addyosmani/agent-skills hit 49K stars. Senior engineers are codifying how to hand work to agents.

The skills ecosystem stopped being anonymous markdown dumps this week and started looking like a real discipline, because the people writing the skills are people you've heard of.

Addy Osmani's agent-skills reached about 49,000 stars in 113 days, roughly 435 a day. The pull is provenance. Osmani is a well-known Chrome and web-performance engineer, and the repo is him codifying how senior engineers should actually hand work to coding agents. "Production-grade engineering skills," not vibes. That matters because the gap between a junior prompt and a senior prompt is mostly tacit knowledge, the stuff you learned by shipping and breaking things, and a good skill library makes that knowledge transferable to the agent.

He's not alone. kepano, Obsidian's lead, shipped obsidian-skills (~34.9K) teaching agents to drive the Obsidian CLI and work with Markdown, Bases, and JSON Canvas. VoltAgent's collection curates 5,400-plus skills from the official registry (~50K stars). sickn33/antigravity-awesome-skills aggregates 1,500-plus installable skills across Claude Code, Cursor, Codex CLI, Gemini CLI, and Antigravity (~40K). Tool makers meeting agents halfway instead of forcing the agents to scrape.

This is the thematic close to the other four stories. Open weights gave us cheap capable models. Devin Desktop and ACP gave us a surface to orchestrate them. Anthropic's 8x is what the feedback loop produces. Agent-operable APIs are how tools survive it. And skills are the layer where human taste gets encoded into the loop, the place your judgment actually lives once you've stopped typing the code yourself.

The thing to do is concrete and cheap. Go read Osmani's repo, not to install all of it, but to see what a senior engineer thinks is worth telling an agent explicitly. Then write your own. The highest-leverage skill file is the one that captures the three things you keep correcting your agent about. I have a handful of these for my own projects and they're worth more than any prompt-engineering trick, because they encode the specific ways my code is supposed to be wrong-proof. Curated skill libraries from people who've shipped are now part of the standard toolkit. Anonymous skill dumps are not.