Write a skill once, use it forever
Every team has a procedure that lives in one person’s head. A skill file turns it into something an agent can pick up on Monday.
Nimind Team
Academy
There is a person on your team who has explained the same process eleven times: the deck structure, the invoice format, the three checks before a launch email goes out. That repetition is a missing file.
What a skill is
A skill is a folder with a short procedure in markdown, the tools it needs, and notes about what good looks like. The agent reads it at the start of a task instead of guessing the shape of the job from a one-line prompt.
The bar for writing one: could a smart contractor follow this on their first day without calling you?
The shape that works
- One outcome per skill. “Publish the weekly changelog”, not “help with content”.
- Inputs, and where they come from: a link, a folder, a table.
- The steps in the order you would actually do them, including the annoying one.
- The two or three checks that catch mistakes you have made before.
- What to do when an input is missing, because it will be.
Skills compound
The first skill saves one explanation. The tenth changes the shape of the team: a new hire inherits the same procedures as the agents, and the procedures stop being folklore. When a project goes wrong, the fix goes into the skill, not into a message that gets buried by Thursday.
The method is small. The next time you answer a question you have answered before, write the answer down as a skill instead. That is it.
Published October 8, 2026 · Nimind Team
Back to all posts
