Fetching from the wire…
Top 5 · 2026-05-22 · source-backed
No compiled code. No runtime. No dependencies. Just 18 markdown files in a .claude directory. Matt Pocock's skills repo hit 75,700 stars this week, gaining 6,400 in seven days. It's the #1 trending AI repo on GitHub.
The repo solves four problems that every Claude Code user hits: misalignment (the agent doesn't understand your intent), verbosity (it generates too much), broken feedback loops (it doesn't verify its work), and design degradation (output quality drifts over time). Each skill is a structured markdown prompt that teaches the agent a specific workflow. TDD. Code review. Planning. Context management.
What's wild is how fast this pattern spread. At least five of the top 20 fastest-growing repos on GitHub right now contain "skills" in their names. This isn't one repo anymore. It's a movement. The community figured out that the leverage point for AI coding agents isn't the model, it's the instructions you give it.
I use a version of this pattern in my own setup. My .claude/skills/ directory has custom skills for my specific workflows, and the difference between Claude Code with good skills and Claude Code without them is the difference between a junior developer and a senior one. Same model, completely different output. The skill layer is where human taste gets encoded.
This connects directly to the Copilot fragmentation story. As the market splinters, the developers who invested in portable skill frameworks are the ones who can switch between agents without losing their workflow. Your skills aren't locked to a vendor. They're yours.
If you haven't looked at Pocock's repo yet, start with the incremental-implementation and test-driven-development skills. They'll change how you use Claude Code within a day. The repo is MIT-licensed. Fork it, customize it, build your own layer on top.
Each link below shares sources, entities, or timing with this story.
Stripe uses Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Stripe uses Claude Code); both cover Claude Code, Each, GitHub, Markdown Files; reported by the same outlet (github.com).
Garry Tan uses Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Garry Tan uses Claude Code); both cover Claude Code, GitHub, MIT, Stars; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude Code uses MCP); both cover Claude Code, GitHub, Stars; reported by the same outlet (github.com).
Codex competes with Claude Code / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, GitHub, Matt Pocock; cite the same source (Matt Pocock's skills repo).
Codex competes with Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Copilot, GitHub, Same; reported by the same outlet (github.com).
Agent Skills supports Claude Code / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Agent Skills supports Claude Code); both cover Claude Code, GitHub, Stars, TDD; reported by the same outlet (github.com).
Cline benchmarked against Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Cline benchmarked against Claude Code); both cover Claude Code, GitHub, Same; reported by the same outlet (github.com).
Anthropic released Claude Code / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Anthropic released Claude Code); both cover Claude Code, Copilot, Same; reported by the same outlet (github.com).