mattpocock/skills ranks #1 on GitHub at 28K stars with `/grill-me` and `/tdd` packs

• mattpocockuk's trending screenshot showed mattpocock/skills at the top of GitHub Trending with 28,634 stars on the day, while mattpocockuk's follow-up said the repo had already crossed 28K stars.
• The repo is being treated less like a notes dump and more like a reusable behavior layer for coding agents, with ctatedev's Portless example showing the agent-facing install pattern as npx skills add vercel-labs/portless and the GitHub repo(https://github.com/mattpocock/skills) serving as the distribution point.
• mattpocockuk's /grill-me post singled out /grill-me as the breakout pack, and the story summary around the repo centers on task-shaped prompts like grilling specs, writing PRDs, and enforcing TDD.
• Third-party projects were already shipping against the same format on day one, because ctatedev's thread paired a human install command for Portless with a separate skills install path for agents.
• Packaging was moving underneath the hype too, with MelkeyDev's retweet of Andrew Qu claiming npx skills@1.5.2 cut post-install time from roughly N times 500 ms to a flat 500 ms.

You can browse the repo, see a live third-party integration in Vercel Labs' Portless repo, and the install path in ctatedev's post already reads like a tiny package manager for agent behavior.

The headline fact is simple: a repo of markdown-defined skills briefly outran everything else on GitHub Trending.

The screenshot in mattpocockuk's post listed the project as "Skills for Real Engineers. Straight from my .claude directory," which is a useful clue about distribution. The repo was not framed as a framework or SDK. It was framed as a portable slice of an agent setup, published directly from a working .claude directory into the public repo.

The interesting unit here is not the repository. It is the skill pack.

According to mattpocockuk's /grill-me post, one of the packs is /grill-me, which he called "the most impactful four sentences I've ever written." The story metadata around the repo describes the broader pattern as packs for grilling specs, writing PRDs, and enforcing TDD, which makes the format look closer to command-shaped behavior modules than to generic prompt snippets.

That matters for readability inside agent workflows, because the interface is the slash command itself. A repository full of packs is easy to star. A short verb like /grill-me or /tdd is easy to invoke mid-run.

The cleanest evidence that this format was escaping one repo came from Portless.

[Src:3|ctatedev's Portless skills post] split installation into two paths:

• For humans: npm install -g portless
• For agents: npx skills add vercel-labs/portless

The companion thread in ctatedev's Portless skills post also described what Portless itself does:

• stable local names like myapp.localhost
• parallel worktrees without clobbering each other
• zero-config startup via portless

That is the bigger signal in this tiny story. The skills format was already being used as a second distribution channel beside ordinary package install, with Vercel Labs' Portless repo riding the same pattern.

One more concrete change showed up in the tooling layer.

According to MelkeyDev's retweet of Andrew Qu, npx skills@1.5.2 sped up post-install from roughly N times 500 ms, where N equals the number of skills, to a flat 500 ms. If that number holds, the repo's sudden popularity was already forcing work on the package manager behavior, not just on the markdown packs themselves.