What problem does it solve? Writing effective agent skills is hard because untested documentation often fails under real-world pressure, and authors cannot know if a skill actually changes agent behavior without observing baseline failures first. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to documentation by running baseline pressure scenarios with subagents before writing any skill content. - Rationalization Bulletproofing: Provides rationalization tables, red flag lists, and explicit loophole counters to make discipline-enforcing skills resistant to agent excuses. - Discovery Optimization (CSO): Defines rules for names, descriptions, keywords, and token efficiency so future agents can find and correctly trigger the skill. - Use Case: When creating a new skill like a code-review checklist, run pressure scenarios without it, document how agents rationalize skipping steps, then write the skill targeting those exact failures and re-test until compliant. ## Quick Start Ask the agent to create a new skill for a recurring technique, starting with baseline pressure-test scenarios before writing the SKILL.md file.
