"Three structural wounds that prose skills cannot fix. 12 lifecycle skills that do. Install in 30 seconds."

I've been using SKILLs every day, with almost zero failure. That's not because I got lucky. It's because I stopped writing them as prose — and I built 12 lifecycle skills that orchestrate all the others, the way Unix commands orchestrate any pipeline.

The problem is not SKILL itself — it is the failure of linguistic precision, and the failure to select the correct skill for a specific situation.

Your skills break and you never know.

Three independent studies found the same thing: 56% non-invocation (Vercel), 50% success rate (Villega), 77% activation (Seleznov, n=650). No error. No warning. No log. Claude proceeds without the skill and the output looks plausible.

That is only one of three wounds.

The three wounds

1. Silent Scope Decay — your prose constraints dilute under context compaction. Your architecture boundaries drift between sessions. Neither failure is detectable.

2.…