writing-skills

Apply test-driven development to create and validate skill documentation.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/SlevoDev/s-tag --skill writing-skills-slevodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/SlevoDev/s-tag/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/SlevoDev/s-tag --skill writing-skills-slevodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills provide a formal approach to creating, editing, and validating Skill documentation using test-driven development. They define a repeatable RED-GREEN-REFACTOR workflow, frontmatter constraints, and progressive disclosure to prevent undocumented gaps and rationalizations.

Core Features & Use Cases

  • TDD-based Skill creation and maintenance
  • Structured frontmatter with name and description
  • Rationalization tracking, red flags, and meta-testing guidance
  • Optional references for deeper materials to keep inline context lean

Quick Start

Draft a new SKILL.md with frontmatter including name and description, then run baseline tests and refine until the skill stays green.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use test-driven development for skill documentation?

Test-driven development for skill documentation applies a RED-GREEN-REFACTOR workflow to ensure skills are measurable, repeatable, and resistant to rationalization. You draft a SKILL.md, run baseline tests, and refine until the skill stays green.

What is the best way to structure frontmatter for skill documentation?

The best way to structure frontmatter for skill documentation is using a standardized format that includes the skill name and description. This conformity ensures reliable discovery, prevents undocumented gaps, and supports progressive disclosure of deeper materials.

Can I track rationalization gaps in my documentation workflow?

Yes, you can track rationalization gaps by applying meta-testing guidance, red flags, and checklists within your documentation workflow. This formal approach identifies undocumented gaps and prevents rationalizations during skill creation and editing.

How do I validate skill documentation before deployment?

You validate skill documentation before deployment by running baseline tests using the RED-GREEN-REFACTOR workflow. Draft your SKILL.md with proper frontmatter, execute the tests, and refine the content until all validation checks stay green.

Does progressive disclosure help keep skill documentation context lean?

Progressive disclosure helps keep skill documentation context lean by moving deeper materials into optional references. This approach maintains concise descriptions in the main document while still providing access to extended information when needed.

Why does my skill documentation fail baseline tests?

Skill documentation fails baseline tests when frontmatter lacks required name and description fields or when content contains rationalization gaps. Refine the SKILL.md file using the RED-GREEN-REFACTOR workflow until the validation checks pass and stay green.