op-add-skilllisted
Install: claude install-skill TimTGelhard/ACHRON-spine
# op-add-skill — write a new bucket skill
Guides the user through adding a personal skill to their bucket. The result is a `bucket/skills/<name>/SKILL.md` (or `<name>.md`) file plus an INDEX row that lets `op-bucket-router` find it later.
## Adjacent files
| File | When |
|---|---|
| `~/.achron-spine/skills/core/op-add-skill/bucket-skill-template.md` | Before writing the new skill file — copy the shape |
## Before writing anything — the gate
Bucket skills are personal-library territory. Chapter 13's anti-pattern is shipping speculative libraries. Refuse to add a skill unless **at least one** of these is true:
- The user has reached for this same pattern **K+ times** already, where **K = `Add-skill minimum fire count`** in `~/.claude/achron-spine-profile.md`'s `## Spine defaults` section, default **3**.
- The user explicitly states: "I do this every project" / "I always X" / "I've corrected Claude on this multiple times."
- There's a concrete repeatable workflow (deploy script, review style, codegen pipeline) the user wants captured.
If none apply, say so plainly: "This sounds like a one-off — not worth a skill yet. Come back when you've reached for it a couple more times." Stop there.
## Steps
1. **Read `~/.achron-spine/bucket/INDEX.md`** — get the existing skill names so you don't collide.
2. **Read `bucket-skill-template.md`** — that's the shape to write.
3. **Gather (one question at a time, free text):**
- `name` — kebab-case slug, unique vs the INDEX (e.g. `de