writing-skills

Convert process documentation into test-driven SKILL.md guidelines with YAML frontmatter.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/danger-English/claude-code-intro --skill writing-skills-danger-english
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/danger-English/claude-code-intro/tree/main/skills/writing-skills
Command: npx skills add https://github.com/danger-English/claude-code-intro --skill writing-skills-danger-english

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill applies test-driven development to process documentation, turning raw skill notes into verifiable, reusable SKILL.md entries that resist rationalization and support reliable deployment.

Core Features & Use Cases

  • RED-GREEN-REFACTOR workflow for writing and validating skills
  • Structured frontmatter with required fields and concise descriptions
  • Progressive disclosure and one-source navigation to keep context minimal yet powerful
  • Guidance on documenting triggering conditions, patterns, and reference material for future reuse

Quick Start

Run baseline pressure scenarios without the skill, then implement the SKILL and re-test to confirm compliance.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to process documentation?

Test-driven development for process documentation uses a RED-GREEN-REFACTOR workflow to turn raw notes into verifiable SKILL.md guidelines. You run baseline pressure scenarios, implement the skill, and re-test to confirm compliance and resist rationalization.

What is the required structure for a SKILL.md file?

A SKILL.md file requires YAML frontmatter with name and description fields, followed by a concise three-section Markdown structure. This format enforces progressive disclosure and one-source navigation to keep context minimal yet powerful for reliable deployment.

How do I validate skill documentation against rationalization?

You validate skill documentation against rationalization by running baseline pressure scenarios without the skill, then implementing the SKILL.md and re-testing to confirm compliance. This failure-based testing approach ensures verifiable, reusable guidelines.

Can I use this skill to edit existing SKILL.md guidelines?

Yes, you can use this skill for creating, editing, and validating skills across a library. It supports iterative refinement through the RED-GREEN-REFACTOR workflow to maintain deployment readiness and structured frontmatter compliance.

What do I need to include in SKILL.md frontmatter for deployment readiness?

For deployment readiness, SKILL.md frontmatter must include name and description fields with concise descriptions. You also need to document triggering conditions, patterns, and reference material for future reuse within the three-section Markdown structure.

When should I use RED-GREEN-REFACTOR for skill writing?

Use RED-GREEN-REFACTOR for skill writing when you need to turn raw process documentation into verifiable, reusable SKILL.md entries. It is essential when creating new skills, editing existing guidelines, or validating skills for deployment readiness across a library.