writing-skills

Create and test agent skills using test-driven development methodology.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill writing-skills-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/writing-skills
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill writing-skills-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing effective agent skills without testing leads to documentation that agents ignore, misinterpret, or rationalize away under pressure. This Skill applies the RED-GREEN-REFACTOR cycle of test-driven development to skill authoring, ensuring skills actually change agent behavior before deployment. ## Core Features & Use Cases - TDD-Based Skill Authoring: Run baseline pressure scenarios with subagents (RED), write minimal skills addressing observed failures (GREEN), then close rationalization loopholes (REFACTOR). - Claude Search Optimization (CSO): Guidelines for writing discovery-optimized descriptions, keyword coverage, naming conventions, and token-efficient content. - Bulletproofing Against Rationalization: Templates for rationalization tables, red flags lists, and explicit loophole counters based on persuasion research. - Use Case: You want to create a new skill enforcing code review discipline. Use this Skill to first run pressure scenarios (time pressure, sunk cost, authority) with subagents, document their exact rationalizations, then write a skill that explicitly counters each excuse and verify compliance. ## Quick Start Use the writing-skills skill to create a new skill for my agent following the test-driven development process.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write an effective skill description for agent discovery?▼

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

How do I test a skill before deploying it?▼

Run pressure scenarios with subagents without the skill first to document baseline failures verbatim, then write the skill addressing those failures, and re-test until agents comply under combined pressures like time, sunk cost, and authority.

What should go in SKILL.md versus separate reference files?▼

Keep principles, short code patterns under 50 lines, and core guidance inline in SKILL.md. Move heavy reference material over 100 lines, API documentation, and reusable scripts into separate files loaded on demand.

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 automated validation instead of documentation.

Why do agents ignore skills under pressure?▼

Agents rationalize violations using excuses like sunk cost, time pressure, or spirit-versus-letter arguments. Counter this with explicit negations of each loophole, rationalization tables, red flags lists, and foundational principles stated early.