skillify-meta-looplisted

Bug → durable skill in 10 steps. The loop runs same-session, no queueing. ## When to invoke | Signal | Example | |---|---| | Same issue 2+ times | Two clients hit the same install error | | Manual repeat | Wrote the same onboarding email 3× | | Codified rule violated | A typo slipped past a lint rule despite it being codified | | Support question pattern | 3 teams asked "how do we wire X" | | Delivery friction | Bespoke setup hour you shouldn't be spending each time | If the trigger is a one-off accident with no pattern signal, skip skillify. The loop is for repeats. ## The 10 steps ### 1. Scaffold Pick the skill's home: - Private skills repo → `~/dev/<your>-skills/<name>/` - Public substrate → `<repo>/skills/<name>/` (if generic + no personal data) - Team repo → `~/dev/<team>-skills/<name>/` `mkdir <path> && touch <path>/SKILL.md`. Don't symlink yet. ### 2. State the trigger In SKILL.md frontmatter `trigger:` field: every phrase a user might type that should fire this skill. Cover bilingual surfaces if relevant. Cover the explicit invocation (`/skill-name`) AND natural-language patterns. Be over-inclusive; pruning false-positives is cheaper than missing the signal. ### 3. Define the failure mode What does the world look like WITHOUT this skill? One paragraph. Be specific: name the file, the rule, the client, the hour cost. Without this, the skill ages into a "feels useful but no one runs it" file. ### 4. Write the steps in caveman form Terse, IF/THEN, bullets, no pre