writing-skills

Create and test agent skills using test-driven development with subagent pressure scenarios.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill writing-skills-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/cache/claude-plugins-official/superpowers/6.1.1/skills/writing-skills
Command: npx skills add https://github.com/ksolomon/dotfiles --skill writing-skills-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation for AI agents often fails because authors guess what guidance agents need instead of observing actual failures, resulting in skills that agents ignore or rationalize away under pressure. ## 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. - Skill Discovery Optimization: Provides rules for writing effective name and description frontmatter, keyword coverage, and token-efficient structure so agents can find skills. - Rationalization Bulletproofing: Includes techniques like rationalization tables, red flags lists, and persuasion principles to close loopholes agents exploit under time or sunk-cost pressure. - Use Case: When creating a new skill that enforces a discipline like TDD, run pressure scenarios with subagents first, document their verbatim excuses, then write the skill to counter those specific rationalizations. ## Quick Start Ask the agent to create a new skill following the test-driven development process, starting with baseline pressure scenarios before writing any documentation.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write a skill that agents actually follow?▼

Run pressure scenarios with subagents before writing the skill to observe baseline failures, then write content addressing those specific rationalizations. Re-test with the skill present and iterate until agents comply under maximum pressure.

What should go in a SKILL.md description field?▼

The description should start with "Use when..." and describe only triggering conditions, symptoms, and contexts in third person. Never summarize the skill's workflow, because agents may follow the description instead of reading the full skill body.

How do I test a skill before deploying it?▼

Create pressure scenarios combining three or more pressures like time, sunk cost, and authority, then run them with subagents with and without the skill. Document verbatim rationalizations and add explicit counters until no new loopholes appear.

When should I not create a new skill?▼

Skip skill creation for one-off solutions, standard practices documented elsewhere, project-specific conventions, and mechanical constraints that can be enforced with regex or validation automation.

Why do agents ignore skills under pressure?▼

Agents rationalize rule violations when facing time pressure, sunk costs, or authority conflicts. Skills need explicit loophole closures, rationalization tables, and red flags lists built from observed baseline failures to resist this.