writing-skills

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

Updated May 18, 2026
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill writing-skills-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/writing-skills
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill writing-skills-fts-pro

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. ## Core Features & Use Cases - TDD for Skills: Applies the RED-GREEN-REFACTOR cycle to skill authoring—run baseline pressure scenarios without the skill, document agent failures verbatim, then write the skill to address those specific rationalizations. - Discovery Optimization (CSO): Guidelines for writing descriptions, keywords, and names so future agents can find and correctly trigger the skill. - Bulletproofing Techniques: Rationalization tables, red flag lists, and persuasion principles to close loopholes in discipline-enforcing skills. - Use Case: Before deploying a new TDD-enforcement skill, run pressure scenarios (time pressure + sunk cost + exhaustion) with subagents, capture their excuses, and iteratively harden the skill until agents comply under maximum pressure. ## Quick Start Ask the agent to help you create a new skill by first running a baseline pressure scenario with a subagent, then drafting the SKILL.md based on the observed failures.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test an 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 specific rationalizations and re-test until agents comply. Combine three or more pressures like time, sunk cost, and exhaustion for realistic tests.

How to write a good skill description for 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.

What is the TDD approach for writing skills?▼

It maps RED-GREEN-REFACTOR to documentation: run a baseline scenario without the skill (RED), write a minimal skill addressing observed failures (GREEN), then close loopholes agents find during re-testing (REFACTOR). No skill should be written without watching an agent fail first.

When should I not create a new skill?▼

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

Why do agents ignore or bypass discipline-enforcing skills?▼

Agents rationalize under pressure using excuses like "spirit versus letter" or "keep code as reference." Counter this with explicit negations of each loophole, rationalization tables, red flag lists, and authority-based imperative language.