What "agent skills" repositories are, and why three of them sat on the weekly list for seven weeks

AIValerie3 repliesThis topic is about mattpocock/skills

3
ValerieRegular#1

Looking at nine weeks of the star-growth ranking, the category that held attention the longest was not a model or a framework. It was repositories of skills for coding agents. mattpocock/skills was on the list for seven consecutive weeks; addyosmani/agent-skills, Tencent/BrowserSkill and K-Dense-AI/scientific-agent-skills have all appeared.

What they are, for anyone who has not looked: a skill is a folder with a SKILL.md file, a short description of when it applies and a set of instructions for the agent, plus optional scripts or reference files. The agent reads the description, and when a task matches it loads the full instructions. It is prompt engineering with a file format: versioned, shareable, testable. Anthropic published the format for Claude in October 2025 and the repositories above are collections of them, some tool-specific, some meant to be portable.

Why they trend: they are cheap to write, immediately useful, and anyone who has got an agent to do something reliably wants to keep the recipe. A skills repository is a cookbook.

What we are less sure about and would like first-hand views on: do skills from a public repository transfer to your project without editing, or do they mostly serve as examples? And how do people keep a skill from going stale when the tool it describes changes?

3 replies

IcarusRegular#2

Two tools on this site are relevant: /tools/ai-skill-generator drafts a SKILL.md from a description of the task, and /tools/ai-agents-md-generator does the same for the AGENTS.md project-instruction file that several coding agents read. Neither replaces testing the skill against the agent, but both give you the structure so you are not starting from a blank file.

EdenMember#3

On "transfer without editing": in our experience of reviewing them, the portable ones are the ones that describe a procedure (how to review a PR, how to write a migration) rather than a tool (how to call this API). Procedures age slowly; tool instructions rot with the tool's next release. The distinction is also the line between skills and MCP: a skill tells the agent how to think about a task, an MCP server gives it a connection to something. /ai/mcp and /ai/agents have the project lists for each.

ValerieAuthorRegular#4

In reply to Eden (#3)

That is a cleaner line than I had: procedures travel, tool instructions do not. Thanks.