27k Stars and Rising: Matt Pocock's Agent Skills for Real Engineers

The Repo That Called Out Vibe Coding by Name

On April 27, 2026, mattpocock/skills sat at the top of GitHub's daily trending chart with over 5,500 stars earned in a single day, pushing its total past 27,000. That kind of velocity is rare for a shell-based repository with no flashy UI and no viral demo video. What drove the climb was the tagline itself: "Agent Skills for real engineers. Straight from my .claude directory."

That phrase - "real engineers, not vibe coding" - landed like a compressed argument. It arrived at a moment when a large portion of the developer community was growing skeptical of AI coding workflows that look impressive in short clips but collapse under the weight of actual production code. Matt Pocock, best known for his TypeScript education work and Total TypeScript course, is not a person who ships half-baked tools. When he publishes what lives in his own .claude directory, engineers pay attention.

The timing also mattered. Claude Code's skills system was already gaining momentum as a serious alternative to ad-hoc prompting. Pocock's repo gave the ecosystem a reference implementation from a high-credibility source.

What the Skills Pack Contains

mattpocock/skills is a structured collection of reusable agent skills organized into four practical categories.

Planning and design skills handle the early stages of software work. to-prd converts a rough idea into a structured product requirements document. to-issues breaks a PRD or feature description into discrete GitHub issues. grill-me runs an interrogation on your plan - asking the hard questions before you start coding. design-an-interface helps sketch out API shapes and component contracts. request-refactor-plan frames a refactor as a plan before any code changes hands.

Development skills cover the coding phase. tdd steers Claude Code toward a test-first workflow. triage-issue takes an open bug report and produces a diagnosis. improve-codebase-architecture audits your current structure and surfaces concrete improvements. migrate-to-shoehorn handles the specific pattern of shoehorning new behavior into an existing codebase without full rewrites. scaffold-exercises generates practice problems from a codebase or concept.

Tooling and setup includes setup-pre-commit, which installs and configures pre-commit hooks appropriate for your stack, and git-guardrails-claude-code, which adds safety rails to Claude Code's git operations so the agent does not make destructive commits without explicit confirmation.

Writing and knowledge rounds out the collection. write-a-skill helps you author a new skill from scratch. edit-article is for prose editing with a technical voice. ubiquitous-language builds a shared vocabulary document from your codebase - a domain-driven design practice that rarely gets done because it takes time. obsidian-vault connects Claude Code to an Obsidian notes directory.

The repository holds 34 commits and ships under the MIT license.

How to Install and Use These Skills

The recommended installation path uses the skills npm package, which Pocock publishes as part of his broader aihero.dev ecosystem. You can add any individual skill to your Claude Code setup with a single command:

npx skills@latest add mattpocock/skills/tdd

Replace tdd with the name of whichever skill you want. For example, to add the planning trifecta:

npx skills@latest add mattpocock/skills/to-prd
npx skills@latest add mattpocock/skills/to-issues
npx skills@latest add mattpocock/skills/grill-me

Each skill installs into your .claude directory as a reusable slash command. Once installed, you invoke them directly inside a Claude Code session:

/to-prd
/tdd
/git-guardrails-claude-code

You can also browse the repository directly and copy the skill files manually if you prefer to inspect them before running any install script. The skills are plain text files - readable, auditable, and easy to modify for your own project conventions.

Who Should Use This

The primary audience is engineers who are already using Claude Code daily and want to move beyond improvised prompting. If you find yourself typing the same setup instructions at the start of every session - "use TDD", "don't make git commits without asking", "write a plan before touching code" - these skills encode that intent once and replay it reliably.

Senior engineers on teams will find particular value in the planning layer. to-prd, to-issues, and grill-me together create a lightweight gate between "someone had an idea" and "someone started writing code." That gate is where a lot of bad software gets caught early in human workflows, and it is often the first thing that disappears when AI agents enter the loop.

Junior engineers benefit from the guardrails. git-guardrails-claude-code and setup-pre-commit impose discipline that an experienced engineer might apply automatically but a less experienced developer - or an AI agent acting autonomously - might skip.

Teams that run mixed human-agent workflows will find the vocabulary skill interesting. ubiquitous-language is one of the few skills in any public collection that addresses the coordination problem between agents, developers, and domain experts.

How This Fits the DevDigest Ecosystem

Claude Code skills are a core topic at Developers Digest. The skills directory at skills.developersdigest.tech catalogs community-contributed skills and serves as a discovery layer for the growing ecosystem of reusable agent behaviors.

mattpocock/skills slots in as a reference-grade pack - the kind of curated, production-tested collection that is worth studying even if you never install it. The naming conventions, the category structure, and the balance between planning and execution skills are all patterns worth borrowing when you write your own.

The write-a-skill skill inside this pack is particularly relevant here. It is recursive in a useful way: you can use Claude Code to build more Claude Code skills, and Pocock's implementation of that idea is a working template. If you have used the skills editor on this site and want a second reference point, reading how Pocock structures his write-a-skill file is instructive.

The git-guardrails-claude-code skill is also directly related to the Claude Code hooks system covered at hooks.developersdigest.tech. While skills and hooks serve different purposes, guardrails around git operations are something both approaches address, and it is worth understanding how each one works to decide which layer the protection belongs in for your project.

Honest Assessment

The strengths are clear: high-credibility source, practical skill selection, clean category structure, and an easy install path. The grill-me and ubiquitous-language skills are particularly underrepresented in competing collections and fill genuine gaps.

The limitations are also real. Thirty-four commits and 27k stars means there is a gap between attention and depth. Some skills are thin wrappers around common patterns that experienced Claude Code users will have already internalized. The repository does not yet include skills for testing infrastructure, deployment, or observability - areas where agent-driven engineering can go wrong in ways that are hard to recover from.

The install tooling via npx skills@latest adds a dependency that some teams will want to vet before running in their environments. Manually copying skill files from the repository is a reasonable alternative until the toolchain matures.

That said, the overall quality bar is higher than most community skill packs. The signal-to-noise ratio is good. This is worth adding to your .claude directory and iterating from.

References

• mattpocock/skills on GitHub
• GitHub Trending - Daily
• skills.developersdigest.tech
• hooks.developersdigest.tech
• aihero.dev