writing-skills

Write and validate Claude Skills using test-driven RED-GREEN-REFACTOR cycles.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wolfbela/claude-skill --skill writing-skills-wolfbela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/wolfbela/claude-skill/tree/main/weshake/skills/writing-skills
Command: npx skills add https://github.com/wolfbela/claude-skill --skill writing-skills-wolfbela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Claude Skills is error-prone without a structured, test-driven approach. This guide provides a framework to write, validate, and deploy Skills that are discoverable, auditable, and resistant to rationalization under pressure.

Core Features & Use Cases

  • TDD-based Skill authoring: Apply RED-GREEN-REFACTOR to Skill creation, ensuring baseline failures are eliminated before deployment.
  • Frontmatter discipline: Enforce YAML frontmatter with name and description for consistent discovery and searchability.
  • Progressive disclosure guidance: Organize inline guidance with lightweight references for scalable Skill content and on-demand loading.

Use Case: A team drafts a new skill for code review patterns, writes a minimal SKILL.md, runs baseline tests without the skill, then iterates until the skill passes all stress checks.

Quick Start

Create and validate a new skill by executing a quick RED-GREEN-REFACTOR cycle and deploy only after successful tests.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I validate documentation frontmatter for skill discovery?

Enforce YAML frontmatter validation by requiring name and description fields for skill discovery. You apply automated checks for toxic content, component presence, and dependency mappings during skill creation and editing.

What is test-driven documentation writing and how does it apply to skill creation?

Test-driven documentation writing applies the RED-GREEN-REFACTOR cycle to skill creation. You write a minimal SKILL.md, run baseline tests without the skill, then iterate until the skill passes all stress checks before deployment.

How do I organize skill content to support progressive disclosure and on-demand loading?

Organize skill content by structuring inline guidance with lightweight references, optional assets, and scripts. This progressive disclosure approach ensures scalable content generation and token-efficient on-demand loading.

Do I need any dependencies to run automated checks on my skill documentation?

No dependencies are required to run automated checks on your skill documentation. The validation framework operates standalone to test for toxic content, component presence, and dependency mappings without external libraries.

What are the limitations of using a TDD approach for writing skill docs?

The TDD approach for writing skill docs requires you to run baseline tests without the skill before iterating, which may add overhead to the initial drafting phase if your team is only making minor content edits.