writing-skills

Create and test agent skills using TDD-style baseline scenarios and loophole closing.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Domush/ai-agent-web-development-skills --skill writing-skills-domush
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Domush/ai-agent-web-development-skills/tree/main/skills/writing-skills
Command: npx skills add https://github.com/Domush/ai-agent-web-development-skills --skill writing-skills-domush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing agent skills without testing them leads to documentation that agents ignore or misinterpret under pressure. This Skill applies Test-Driven Development to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - RED-GREEN-REFACTOR for documentation: Run baseline pressure scenarios with subagents, document failures verbatim, write the minimal skill, then close rationalization loopholes. - Discovery optimization (CSO): Guidelines for writing name and description frontmatter, keyword coverage, and token-efficient structure so agents actually find and load the skill. - Bulletproofing techniques: Rationalization tables, red-flag lists, and persuasion principles to make discipline-enforcing rules resist workarounds. - Use Case: You want to add a new skill to your agent's library. Use this Skill to first run a pressure scenario without the skill, capture how the agent fails, then write and iteratively harden the SKILL.md until the agent complies under maximum pressure. ## Quick Start Use the writing-skills skill to create a new agent skill following the TDD-based authoring and testing workflow.

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.md file for an agent skill?▼

A SKILL.md needs YAML frontmatter with a name and a description starting with "Use when...", followed by a body with an overview, when-to-use triggers, core patterns, and common mistakes. Keep the description focused on triggering conditions, never a workflow summary.

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 failures and re-test. Combine three or more pressures like time, sunk cost, and authority, and keep refactoring until no new rationalizations appear.

What makes a good skill description for discovery?▼

A good description starts with "Use when", is written in third person, and lists concrete triggering symptoms and situations. It must never summarize the skill's workflow, because agents may follow the description shortcut instead of reading the full skill body.

When should I not create a new agent skill?▼

Skip creating skills 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 regex instead of documentation.

Why do agents ignore or bypass skill rules under pressure?▼

Agents rationalize violations using excuses like sunk cost, pragmatism, or spirit-versus-letter arguments. Counter this with explicit negations of each loophole, rationalization tables, red-flag lists, and authority-based imperative language.