- Home
- Skills
- Hotovo
- Aider Desk
- Skill Creator
skill-creator_skill
- TypeScript
1k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill hotovo/aider-desk --skill skill-creator- SKILL.md1.6 KB
Overview
This skill helps you design and create Agent Skills using progressive disclosure principles. It focuses on keeping trigger metadata and core instructions lean while offloading detailed content to external resources. Use it to standardize skill architecture and streamline authoring for developer-focused AI agents.
How this skill works
The skill defines a three-level loading model: compact trigger metadata, concise core instructions, and on-demand detailed resources. Triggers and core patterns remain small to keep token use efficient, while extensive documentation, scripts, and assets are stored separately and fetched only when needed. This keeps runtime prompts focused and ensures maintainability as capabilities grow.
When to use it
- You notice repeated context or tasks across agent conversations
- A domain or team needs consistent, reusable agent behavior
- You’re planning the architecture for multiple related skills
- You need to offload large documentation, templates, or scripts
- You want predictable triggering with minimal prompt overhead
Best practices
- Keep metadata under ~30 tokens to optimize trigger matching
- Limit core instructions to essential patterns and examples (<680 tokens)
- Put step-by-step guides, code, and assets in separate resource folders
- Use clear naming and a consistent folder layout for discoverability
- Design triggers to be specific enough to avoid false positives
Example use cases
- Create a repository-specific dev assistant with project knowledge loaded on demand
- Extract recurring troubleshooting flows into a reusable skill
- Bundle common developer commands and scripts so the agent can run them when authorized
- Provide language- or domain-specific editing guidelines without bloating prompts
- Build onboarding helpers that reveal deeper training materials only when requested
FAQ
Keep it compact—aim for a few tokens that reliably match intent without including detailed instructions.
What goes into the core instructions versus resources?
Core instructions include essential behavior patterns, guardrails, and short examples. Put long tutorials, sample code, templates, and heavy references in resources loaded on demand.