Short answer
Choose one repeated job, create a SKILL.md file that explains when and how to do it, add a small example, test it on real tasks, and publish it with a clear name, version, source, and license.
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Package: a named group of files that people can install and update together.
- Git: a tool that records file changes so people can review or undo them.
What this means
Give the skill one job
A focused skill is easier to discover, test, and trust. Use a clear job such as reviewing a pull request, writing release notes, or preparing a support handoff.
Write instructions that can be checked
Explain when to use the skill, the information it needs, the steps it follows, the output it should create, and the actions it must not take. Add one short example of useful input and output.
Package and improve it
Put the skill in Git, review changes, test it on several real tasks, and give shared releases version numbers. AIPM can create the package folder, validate public files, and publish the package page.
Simple steps to create and AI agent
- Choose one repeated task with a clear result.
- Run aipm publish init --name @your-org/skill-name.
- Edit SKILL.md with purpose, steps, limits, and examples.
- Add description, targets, license, source URL, and tags to the manifest.
- Run aipm publish add . and aipm publish validate.
- Test the skill before publishing version 1.0.0.
Where to go next
If you want to try this in a real project, start with the install guide, then read how to use AIPM. If you want to share your own workflow, read the publishing guide.
FAQ
How long should SKILL.md be?
Use the shortest file that explains the job clearly. Move long reference material into separate files and include it only when the task needs it.
What should never be included in a public skill?
Do not include passwords, API keys, customer data, private prompts, confidential documents, or instructions that hide risky behavior.