writing-skills

Create and test agent skills using TDD-style pressure scenarios with subagents.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill writing-skills-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ibytechaos/claude/tree/main/plugins/superpowers/skills/writing-skills
Command: npx skills add https://github.com/ibytechaos/claude --skill writing-skills-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation-style skills for AI agents often produces untested instructions that agents ignore or rationalize away under pressure, leading to unreliable behavior in production workflows. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to skill creation by running baseline pressure scenarios with subagents before writing any documentation. - Rationalization Bulletproofing: Provides rationalization tables, red flag lists, and explicit loophole counters so discipline-enforcing skills resist agent workarounds. - Discovery Optimization (CSO): Defines naming, description, and keyword rules so future agents can find the right skill from its frontmatter alone. - Use Case: When creating a new skill like a code-review checklist, run baseline scenarios without the skill, document how agents fail, write the minimal skill addressing those failures, then re-test until agents comply under time, sunk-cost, and authority pressure. ## Quick Start Ask the agent to help you create a new skill by first running baseline pressure scenarios with subagents, then writing and iteratively testing the SKILL.md until agents comply.

Frequently Asked Questions about writing-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a new agent skill before deploying it?

Run pressure scenarios with subagents without the skill first to capture baseline failures verbatim, then write the skill addressing those failures and re-test until agents comply. Combine three or more pressures like time, sunk cost, and authority for realistic tests.

What makes a good SKILL.md description for discovery?

Write the description in third person starting with "Use when..." and list only triggering conditions and symptoms, never a workflow summary. Descriptions that summarize the process cause agents to follow the description instead of reading the full skill.

How do I stop agents from rationalizing away skill rules?

Close every loophole explicitly with negations, build a rationalization table from observed excuses, add a red flags list, and state that violating the letter of the rules violates the spirit. Re-test after each addition until no new rationalizations appear.

When should I not create a new skill?

Skip skill creation for one-off solutions, project-specific conventions that belong in CLAUDE.md, well-documented standard practices, and mechanical constraints that can be enforced with validation or automation instead of documentation.

What is the difference between technique, pattern, and reference skills?

Technique skills give concrete steps to follow, pattern skills provide mental models for problem-solving, and reference skills hold API or syntax documentation. Each type needs a different test approach: application scenarios, recognition scenarios, or retrieval scenarios respectively.