Create AiderDesk Agent Skills by writing SKILL.md files, defining frontmatter metadata, structuring references, and organizing skill directories. Use when building a new skill, creating a SKILL.md, planning skill architecture, or writing skill content.
89
86%
Does it follow best practices?
Impact
89%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Create effective Agent Skills using progressive disclosure.
Create a skill when you notice:
Skills load in 3 levels:
Key: Keep Levels 1 & 2 lean. Move details to Level 3.
.aider-desk/skills/my-skill/SKILL.md with YAML frontmatter (name, description) and body instructionsreferences/ as neededIf skill doesn't load: check YAML syntax is valid, name is lowercase-hyphenated, and description contains the trigger terms users would say
---
name: deploy-helper
description: Deploy AiderDesk builds to staging and production environments. Use when deploying, releasing, or publishing builds.
---# Deploy Helper
Build and deploy AiderDesk to target environments.
## Steps
1. Run `npm run build` to generate production artifacts
2. Verify build output exists in `dist/`
3. Deploy to staging: `./scripts/deploy.sh staging`
4. Verify deployment: check health endpoint returns 200
## Troubleshooting
- Build fails: check `tsconfig.json` paths and run `npm run typecheck`
## References
- [environments.md](references/environments.md) - Environment configsmy-skill/
├── SKILL.md # Core instructions + metadata
├── references/ # Detailed docs (loaded as needed)
├── scripts/ # Executable operations
└── assets/ # Templates, images, files9bcd9bb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.