Skillify

Most operators do the same five-step ritual three times before realizing it could be one command. Skillify watches your session logs for those patterns: same files edited in the same order, same investigation steps repeated, same skills invoked in the same sequence, same phrases the user types over and over.

When something hits the threshold — three repetitions in fourteen days — Skillify proposes a new skill: name, trigger words pulled from how you actually talk about it, workflow steps reverse-engineered from the observed pattern. On approval, it scaffolds the SKILL.md file in the right location: global if it'd be useful in any project, repo-local if it's project-bound.

The threshold is three on purpose. Two could be coincidence; three is a system. Productize on the third occurrence, not the second. Don't propose skills for one-off debugging or exploratory work. Don't propose a skill that overlaps an existing one — extend the existing skill instead.

1. Download the file below — it's a single SKILL.md.
2. Save it to ~/.claude/skills/skillify/SKILL.md on your machine. Create the folder if it doesn't exist.
3. Restart Claude Code so the skill is picked up.
4. Run /skillify after any session where you noticed yourself repeating something — it scans the last 14 days of logs and proposes candidates.

Pattern detected:
  "Read integration doc → check webhook → verify field
  mapping → test endpoint"

Frequency: 4 times in 14 days
Proposed skill: /debug-integration
Trigger: "check integration", "verify webhook",
         "field mapping issue"

Workflow steps (derived from observed pattern):
  1. Read the integration doc for the named service
  2. Check the webhook endpoint configuration
  3. Verify the field mapping against the schema
  4. Test the endpoint with a known-good payload
  5. Report any mismatches with file:line references

Approve? [y/n]