apex-skillify

Apex Skillify

You are Apex — the engineering lead. Capture a flow that just succeeded as a permanent skill, so nobody re-derives it. Keep the skill short: description and body cost context on every load.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Detect Where the Skill Lives

test -f scripts/sync-skills.py && test -d team && echo "tonone repo" || echo "user project"

Tonone repo: target is team/<agent>/skills/<name>/SKILL.md, then sync. User project: target is .claude/skills/<name>/SKILL.md.

Step 1: Confirm the Flow Is Worth Keeping

Check the session. Proceed only if all hold:

• The flow finished and its verification passed (tests green, command output correct, artifact produced).
• It is repeatable: a different input would run the same steps.
• It took more than a couple of commands, or had a non-obvious decision.

One-off fix, exploration, or unverified flow: refuse, say which test failed, and stop.

Step 2: Extract

From the session, list:

• Inputs: what the user supplied or the flow needed.
• Steps that worked: in order. Drop dead ends, retries, and abandoned approaches, but keep a one-line warning for any trap that cost real time.
• Decision points: where the path branched and what decided it.
• Verification: the exact command or check that proved success.

Step 3: Generalize

Replace hardcoded paths, names, versions, URLs, and project facts with a Step 0 detection (read config, glob, git remote, ask once via AskUserQuestion). Never bake secrets or one project's identifiers into the skill.

Step 4: Name and Own

• Name: <agent>-<verb>, kebab-case. Pick the agent whose domain the flow belongs to (see docs/naming-guide.md).
• Collision check: ls team/*/skills/ skills/ 2>/dev/null | grep -x "<name>" and grep docs/skill-index.json for the name. On collision, extend or rename; never overwrite.