Author a Skill for your project
Draft a Skill from your repository's commands, conventions, and workflows. Review it, then keep it in the repository so any agent can run it.
Authoring guide
1. Draft your Skill
Project Skill
Change setupOpen your agent at the repository root. Give it these instructions to draft your Skill.
Read https://raw.githubusercontent.com/skilld-dev/skilld/main/skills/generate-project-skill/SKILL.md. Draft a Skill for this project using this repository. Read the project instructions, the manifests, and the test, lint, build, and release commands. Show the draft for review before replacing existing Skills.
Point your agent at the repository root.
Ask it to save the draft in skills/your-skill/SKILL.md.
Describe the work the Skill covers: the commands to run, the files to read first, and the rules agents break most often. Point to source files instead of copying them. Name the directories an agent must not edit.
2. Review the draft
Run each command the Skill lists and check the outcome it records. Use the cross-Agent checks to test selection, missing inputs and task completion. Use the authoring Skill's quality checks before committing.
3. Keep the Skill in the repository
Commit the reviewed Skill. GitHub is the source of truth, and skilld.dev reads the Skill from one exact commit. Any dev with access to the repository can run it:
npx skilld run owner/repo/your-skillReplace owner/repo with your repository and your-skill with the Skill directory name.
Put the command in your README so contributors can find it.
For a private repository, see Use Skills from private Repositories.
4. Keep it current
When a command or convention changes, review the Skill alongside the change. Run the authoring Skill again when the project structure moves.