Write a skill
Personal AI agent skills for better coding. Fixes common agent failure modes: misaligned requirements, blind coding, debugging loops, and lost context between sessions.
npx -y skills add tyecode/skills --skill write-a-skillAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Creates new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
SKILL.md
1.8 KB, as published. Nobody here has run it
Skill: write-a-skill
When to Use This Skill
Use this skill when:
- User wants to create a new reusable skill
- User says "write a skill", "build a skill", or "create a skill"
Process
-
Gather requirements - ask user about:
- What task/domain does the skill cover?
- What specific use cases should it handle?
- Does it need executable scripts or just instructions?
- Any reference materials to include?
-
Draft the skill - create:
SKILL.mdwith concise instructions (under 100 lines)- Additional reference files if content is large or has distinct domains
- Utility scripts if deterministic operations are needed
-
Review with user - present draft and ask:
- Does this cover your use cases?
- Anything missing or unclear?
- Should any section be more/less detailed?
Skill Structure
skill-name/
├── SKILL.md # Main instructions (required)
├── TEMPLATE.md # Reusable templates (if needed)
├── REFERENCE.md # Detailed docs (if needed)
└── scripts/ # Utility scripts (if needed)
└── helper.js
See TEMPLATE.md for the standard SKILL.md template, description rules, and review checklist.
When to Add Scripts
Add utility scripts when:
- Operation is deterministic (validation, formatting)
- Same code would be generated repeatedly
- Errors need explicit handling
Scripts save tokens and improve reliability vs generated code.
When to Split Files
Split into separate files when:
SKILL.mdexceeds 100 lines- Content has distinct domains (e.g., finance vs. sales schemas)
- Advanced features are rarely needed