skills: Skills for Real Engineers. Straight from my .claude directory

by mattpocock · Agent Tool · ★ 321.9k

Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h

Featured in: Claude Code Skills

Security audit verdict: SAFE · quality 52/100

None of the 44 rules matched — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against 44 published rules built on the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →

The quality score combines nine heuristic checks of the repo and its README: completeness, clarity, specificity, examples, structure, agent readiness, step-by-step content, instruction quality and security notes. It rates how well the project explains itself to an agent, not the code.

🧪 Tested by Agent Skills Hub

One of 36 tools we ran end to end on the same task for our Claude Code Skills page (2026-10-11).

Our pick for everyday engineering: The most-starred collection here and one of the leanest: 38 skills, all 38 meet the format, about 1,500 tokens of names and descriptions in total.

Result: 38 distinct skills · 100% meet the format · installed whole, every skill keeps its description

See the count → · See the whole test →

Skills in this repository (31)

  • ask-matt Ask which skill or flow fits your situation. A router over the skills in this repo.
  • code-review Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's doc…
  • codebase-design Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportuniti…
  • diagnosing-bugs Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throw…
  • domain-modeling Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or edi…
  • git-guardrails-claude-code Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wa…
  • grill-me A relentless interview to sharpen a plan or design.
  • grill-with-docs A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
  • grilling Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' tri…
  • handoff Compact the current conversation into a handoff document for another agent to pick up.
  • implement Implement a piece of work based on a spec or set of tickets.
  • implement-spec Implement the result of /to-spec and /to-tickets in code.
  • improve-codebase-architecture Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
  • migrate-to-shoehorn Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests…
  • prototype Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right…
  • research Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants…
  • retro Conduct a retrospective on a coding session.
  • scaffold-exercises Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold…
  • setup-matt-pocock-skills Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before f…
  • setup-pre-commit Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-com…
  • tdd Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integrat…
  • teach Teach the user a new skill or concept, within this workspace.
  • to-questionnaire Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
  • to-spec Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already…
  • to-tickets Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the co…
  • pr Use when writing a PR body.
  • triage Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
  • wait-what Stop. That last message did not land: re-pitch it.
  • wayfinder Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve the…
  • wizard Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting u…
  • writing-for-agents Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Quick Facts

Stars321,860
Forks26,982
LanguageShell
CategoryAgent Tool
LicenseMIT
Quality Score52/100
Open Issues236
Last Updated2026-11-11
Created2026-02-03
Platformsclaude-code, cli
Est. Tokens~11k

About skills

Agent Skills A collection of agent skills that extend capabilities across planning, development, and tooling. Planning & Design These skills help you think through problems before writing code. write-a-prd — Create a PRD through an interactive interview, codebase exploration, and module design. Filed as a GitHub issue.

More Agent Tool Tools

Explore other popular agent tool tools:

View all Agent Tool tools →

Popular Shell Agent Tools

How this security grade is produced

Grades come from a rule-based scan built on the SlowMist agent-security taxonomy: 44 published rules, covering credential harvesting, data exfiltration, curl | sh installers and more. It is a first-layer scan, not a manual audit — we say so rather than overstate it.

The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.

Sources & who's responsible:

View on GitHub → Browse Agent Tool tools