$npx -y skills add tkellogg/open-strix --skill skill-creatorCreate or update reusable skills for this agent. Use this skill ONLY when the user asks to create a new skill, edit an existing skill, improve a SKILL.md, or capture a repeated workflow as a reusable skill. Do not use this skill for one-off tasks.
| 1 | # skill-creator |
| 2 | |
| 3 | Create or update local skills in this agent home repo. |
| 4 | |
| 5 | ## Where Skills Go |
| 6 | |
| 7 | User-editable skills belong in: |
| 8 | - `skills/<skill-name>/SKILL.md` |
| 9 | |
| 10 | Example: |
| 11 | - `skills/triage-issues/SKILL.md` |
| 12 | |
| 13 | Built-in skills are exposed at: |
| 14 | - `/.open_strix_builtin_skills/<skill-name>/SKILL.md` |
| 15 | |
| 16 | Treat built-in skills as read-only. |
| 17 | |
| 18 | ## Critical Rule: Trigger Description |
| 19 | |
| 20 | The YAML frontmatter `description` is the trigger signal. It must make it obvious |
| 21 | when the skill should be used. |
| 22 | |
| 23 | Every skill description should include: |
| 24 | - what the skill does |
| 25 | - exact "when to use" triggers |
| 26 | - what it should not be used for |
| 27 | |
| 28 | Bad description: |
| 29 | - `Helps with docs.` |
| 30 | |
| 31 | Good description: |
| 32 | - `Create and update release notes from git history. Use when the user asks for changelogs, release summaries, or version notes. Do not use for code changes.` |
| 33 | |
| 34 | ## Authoring Checklist |
| 35 | |
| 36 | 1. Write frontmatter with `name` and a high-signal `description`. |
| 37 | 2. Add concise execution steps in the SKILL body. |
| 38 | 3. Include concrete paths/commands the agent should run. |
| 39 | 4. Keep scope narrow; split broad domains into multiple skills. |
| 40 | 5. Prefer deterministic instructions over generic advice. |