How an agent learns to do things.
A skill is a file that teaches an agent one job, done well. It is the difference between an agent that can only talk and one that can actually get work done. Stack skills together and a simple assistant grows into something genuinely capable. This is the piece our whole network is named for.
A skill is a self-contained file that teaches an agent a single capability: what the job is, when to use it, and how to do it well. It is not code you run. It is instructions the agent reads at the moment it needs them, written in plain language.
Think of your agent as a sharp new hire and each skill as a one-page playbook for a specific task. Hand it the "write a press release" playbook and it can write releases. Hand it ten playbooks and it can do ten jobs. You are not making the agent smarter, you are handing it a growing stack of things it now knows how to do.
People mix these up constantly. Keep them straight and everything else about agents gets easier.
Every skill has three parts: a name, a description that tells the agent when to reach for it, and the instructions themselves. Here is a real one:
name: write-press-release description: Use when the user needs a newsworthy press release for an announcement. --- 1. Ask for the announcement, the company, and the type of outlet it is aimed at. 2. Lead the headline with the news, not the brand. 3. Write inverted-pyramid: most important first. 4. Add a boilerplate paragraph and a media contact. 5. Stay factual. Flag any claim you cannot verify.
The description is the clever part. The agent reads just that one line to decide whether this is the right skill for the moment, without loading the whole thing. That keeps it fast even with a big library.
An agent does not hold every skill in its head at once. It keeps a short list of each skill's name and description, and only pulls the full instructions in when the moment calls for it. Ask it to write a release and it loads the press-release skill; ask it to book a call and it loads the booking one.
This is why you can give one agent dozens of skills without slowing it down or confusing it. It reaches for the right playbook, uses it, and sets it back down.
Stack skill on skill. Each one you add makes the agent capable of one more thing, with no rewrite.
Write a skill once and drop it into any agent that needs that job. Build a library, not a one-off.
The agent only pulls in the skill it needs, when it needs it, so it stays fast and focused.
A skill is just a file. It can be handed to a teammate, sold, or dropped into a new build in seconds.
Choose a single, well-defined task. One skill, one job. Resist the urge to make it do everything.
Write a one-line description so the agent knows exactly when to reach for this skill and not another.
Spell out how to do the job in plain language, the way you would brief a sharp new hire. Add any rules or limits.
Run the agent through the job, tighten the wording where it slips, and drop the finished skill into any agent that needs it.
That is the whole craft. A good skill reads like a clear briefing, not a program. Once you have written a few, you will start seeing every repetitive job as a skill waiting to be captured.