writing-skills

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

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill writing-skills-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill writing-skills-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphviz, and includes scripts (resource) and 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 Test-Driven Development to skill authoring so you can verify agents actually comply before deployment. ## Core Features & Use Cases - TDD-Based Skill Authoring: Follows the RED-GREEN-REFACTOR cycle—run baseline pressure scenarios without the skill, document agent failures verbatim, then write the skill to address those specific rationalizations. - Rationalization Bulletproofing: Provides patterns for closing loopholes, building rationalization tables, red-flag lists, and persuasion principles grounded in research (Cialdini, Meincke et al.). - Discovery Optimization (CSO): Guidelines for writing descriptions, keywords, and naming so future agents can find the skill when needed. - Use Case: You want to create a new discipline-enforcing skill (e.g., requiring verification before completion). Use this Skill to design pressure scenarios with subagents, watch baseline failures, write the minimal skill, and iterate until agents comply under maximum pressure. ## Quick Start Ask the agent to help you create a new skill using the writing-skills TDD workflow, starting with a baseline pressure scenario test.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a new Claude agent skill?▼

Create a directory with a SKILL.md file containing YAML frontmatter with name and description fields, followed by markdown instructions. Follow the TDD cycle: run baseline scenarios without the skill first, then write the skill to address observed failures.

How to test agent skills before deployment?▼

Use pressure scenarios with subagents that combine multiple pressures like time constraints, sunk cost, and authority. Run scenarios without the skill to capture baseline rationalizations, then verify agents comply once the skill is present.

What should a SKILL.md description field contain?▼

The description should start with "Use when..." and describe only triggering conditions and symptoms, never the skill's workflow. Write in third person, keep it under 500 characters, and include searchable keywords like error messages and symptoms.

Why do agents ignore or bypass skill instructions?▼

Agents rationalize around rules under pressure using excuses like "spirit versus letter" or "being pragmatic." Bulletproof skills by adding explicit negations for each loophole, rationalization tables, and red-flag lists based on observed baseline failures.

When should I not create a skill?▼

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