Agent skills are becoming composable the way npm packages did

Skills are just markdown files that make agents useful

An agent skill is a markdown file. You write instructions in natural language, save as .md, and your agent knows how to do something new. No API. No SDK. No build step. Prose that teaches a machine a specific task.

The distribution is what makes this interesting. npx skills add mblode/agent-skills. One command and the skill is in your project. Sound familiar? This is npm install for agent capabilities. Browse a registry, install, your agent gets smarter.

I have been building skills for Claude Code since late 2025. Every time I repeat the same instructions across projects, I extract them. Deployment patterns, code review checklists, animation guidelines, component decisions. Things that lived in my head now live in shareable files.

The meta moment

I built agent-skills-creator. A skill that creates skills. You describe what you want, and the agent generates a structured skill file. A skill that makes skills. Not a gimmick. It is the natural consequence of treating agent capabilities as composable units.

Then I built allmd. It converts any URL, PDF, video, or audio into clean markdown. The tagline is "turn the whole universe into a skill," and I meant it literally. Any knowledge source becomes agent context in one command.

Then I built Shareful.ai. Stack Overflow for AI coding agents. Developers share solutions and patterns that work with AI tools. The problems we solve with agents are different from the ones we Google. They deserve their own knowledge base.

Each project felt standalone. They are the same idea. Build the ecosystem that makes agent capabilities shareable.

The npm analogy is not a metaphor

In 2010, npm was a weird idea. Why share a four-line function as a package? Why install left-pad instead of writing it? Composability at scale changes everything. Small, focused, reusable units compound into capability no single developer could build alone.

Skills are on the same trajectory. Small. Focused. Shareable. Composable. Install one for database migrations, another for accessibility audits, another for performance profiling. Your agent becomes competent across domains without you being an expert in all of them.

The early npm ecosystem was messy and exciting. Skills are messy and exciting now. No dominant registry. Best practices still forming. The people building skills today are the equivalent of the first npm publishers.

MCPs are the other half

MCPs are infrastructure for agents rather than humans. They expose natural language APIs so bots can run commands. Stainless auto-generates SDKs and MCPs from OpenAPI specs. The infrastructure layer is standardising fast.

Skills sit on top. A skill tells an agent when and why to use a specific MCP. The MCP provides the capability. The skill provides the judgment.

The honest tension

Here is what I wrestle with: even skills for CLI tools are mostly overkill because Claude Code can figure it out. Give it a well-documented tool and it will read the docs and use it correctly.

So why do skills matter? They improve output quality and consistency. The gap between "the agent can figure it out" and "the agent does it the way I want" is real. Skills close that gap. They encode preferences and hard-won decisions the agent would not discover alone.

The honest question is whether that gap shrinks to zero. Maybe skills are transitional. Essential now, obsolete later.

The open question

Will skills consolidate the way npm did, with a dominant registry and standard format? Or will agents absorb skills into their own intelligence?

I do not know. But I know which side I am building on. The people who shaped npm's early ecosystem got to define how a generation of developers shared code. The people shaping skills today get to define how a generation share agent capabilities.

That is a bet worth making. Even if the agents eventually eat it all.