write-skill
/write-skill
Create a new agent skill, or improve an existing one, inside this skills repo, following its housekeeping rules. Use when asked to "write a skill", "make this a skill", "save this as a skill", "turn what we just did into a skill", or "improve the X skill".
- Author
- cao-partners-au ↗
- Repository
- olc-agent-skills-starter ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create a new agent skill, or improve an existing one, inside this skills repo, following its housekeeping rules. Use when asked to "write a skill", "make this a skill", "save this as a skill", "turn what we just did into a skill", or "improve the X skill".
Triggers from the description
Original author description
Create a new agent skill, or improve an existing one, inside this skills repo, following its housekeeping rules. Use when asked to "write a skill", "make this a skill", "save this as a skill", "turn what we just did into a skill", or "improve the X skill".
How it works
- Steps
- Improving an existing skill
SKILL.md preview
--- name: write-skill description: Create a new agent skill, or improve an existing one, inside this skills repo, following its housekeeping rules. Use when asked to "write a skill", "make this a skill", "save this as a skill", "turn what we just did into a skill", or "improve the X skill". --- # Write a skill Skills live in the user's skills repo (usually `~/agent-skills`), one folder per skill: `skills/<name>/SKILL.md`. Follow `HOUSEKEEPING.md` in that repo. ## Steps 1. **Find the repo.** Look for `~/agent-skills`, or ask the user where their skills repo is. Never create skills outside it. 2. **Check for an existing skill** that already covers the job (`skills/*/SKILL.md`). Improve that one rather than adding a near-duplicate. 3. **Agree the job in one sentence** with the user: what outcome, and when it should trigger. If it covers two unrelated jobs, make two skills. 4. **Copy `skills/_template/SKILL.md`** to `skills/<name>/SKILL.md`. Name: lowercase words joined by hyphens. 5. **Write the description first.** It decides when the skill loads: say what it does and list the phrases the user would actually use. 6. **Fill in the body**, briefly: - the outcome, and what to check before starting - only the steps and rules that matter, not general knowledge - business facts in one place - gotchas: what went wrong before and the fix. When turning a just-finished task into a skill, capture the mistakes and corrections from that task here. 7. **No secrets.** Refer to keys and logins by environment variable or password-manager item name only. Never paste a value. 8. **Test it** on a real task, or walk the user through a dry run, and fix what's unclear. 9. **Install and save:** run `./install.sh` from the repo, tell the user to restart their AI tool, then commit and push: ```bash git add skills/<name> && git commit -m "Add <name> skill" && git push ``` Add a line to `CHANGELOG.md` for anything notable. ## Improving an existing skill - Read the whole skill first. Change the smallest part that fixes the problem. - Add the new gotcha or rule; don't rewrite what already works. - Commit with a message that says what changed and why.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · cao-partners-au/olc-agent-skills-starter | 100 | MIT |
| hassan-mohiddin/freeflow | 100 | MIT |
| jelvodev/yaap | 100 | MIT |
| wilbeibi/claude-toolkit | 100 | MIT |
| NormandErwan/claude-casebook | 98 | BSD-3-Clause |
| hassan-mohiddin/freeflow | 96 | MIT |
| LandonSchropp/agent-toolkit | 90 | MIT |
| serionist/claude-session-restore | 90 | MIT |
| pwguler/skills | 82 | MIT |
Database snapshot: 13.11.2026 · package version c670b92f96fc (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100skill-writer
Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills. - 100skill-writer
Create and improve agent skills following the Agent Skills specification. Use when asked to create, write, or update skills. - 100skill-creator
Create, improve, and troubleshoot Claude Code agent skills. Use when asked to make a new skill, write a SKILL.md file, improve skill discoverability, debug why a skill isn't activating, answer questions about skills, or review skill best practices. - 100skill-writer
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs… - 100add-skill
Use in the agent-skills repo when the user asks to add a new shared skill, change or split one in skills/, move a section to a reference file, or fix a failing check. Writes the skill to the rules in AGENTS.md, runs the skill and prose checks and the temp home install, and… - 100skill-development
This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent.