chore: add skills library

This commit is contained in:
Zac Gaetano 2026-05-29 20:11:11 -04:00
parent 7c7fc44f7e
commit 674162e044

View file

@ -0,0 +1,59 @@
---
name: skill-creator
description: Create a new reusable Claude Code skill from scratch. Use when the user wants to encode a repeatable workflow, process, or domain expertise into a skill file.
---
# Skill Creator
Use when: building a new skill to encode a workflow, process, checklist, or domain expertise that should be reusable across sessions.
## What Makes a Good Skill
- **Specific trigger** — clear "use when" condition so Claude knows when to invoke it
- **Process, not just content** — steps to follow, not just reference info
- **Opinionated** — makes decisions so the user doesn't have to repeat themselves
- **Testable** — you can tell if it's being followed correctly
## Skill File Format
```markdown
---
name: skill-name # kebab-case, matches filename
description: One line explaining when and why to use this skill.
---
# Skill Title
Use when: [specific trigger condition]
## [Section 1]
[Content]
## [Section 2]
[Content]
## Rules / Constraints
- Hard rules the skill enforces
```
## Process for Creating a New Skill
1. **Understand the workflow** — ask the user:
- What task does this skill help with?
- When should it be triggered (what user phrase or situation)?
- What are the non-obvious things to remember?
- What mistakes does it prevent?
2. **Draft the skill** — write a SKILL.md with:
- Clear frontmatter (name, description)
- Trigger condition upfront
- Step-by-step process OR checklist
- Rules/constraints section
- Example output if helpful
3. **Save to `~/.claude/skills/<name>.md`**
4. **Test it** — invoke the skill and confirm it produces the right behavior
## Skill Location
Skills go in `~/.claude/skills/` as individual `.md` files.
They're invoked with `/skill-name` or detected automatically from the description.