writing-skills

Create and validate Claude Skills with YAML frontmatter and test-driven documentation.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/jmmL/dr3-old --skill writing-skills-jmml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jmmL/dr3-old/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/jmmL/dr3-old --skill writing-skills-jmml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a disciplined, test-driven approach to documenting Claude Skills, ensuring they are discoverable, reusable, and verifiable.

Core Features & Use Cases

  • Structured Skill templates: YAML frontmatter plus concise, actionable content that guides skill authors.
  • TDD-aligned workflow: RED-GREEN-REFACTOR cycles for creating and updating Skills with explicit validation.
  • Progressive disclosure: supports inline content with optional references to heavy material to minimize context load.

Quick Start

  • Create an initial SKILL.md with frontmatter and a brief overview, then expand sections as needed.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write Claude Skills that are discoverable and maintainable?

Writing Claude Skills requires structured SKILL.md files with YAML frontmatter and progressive disclosure to ensure documentation is discoverable, reusable, and verifiable across projects.

What is the test-driven documentation workflow for creating new skills?

Test-driven documentation applies RED-GREEN-REFACTOR cycles to skill creation, ensuring explicit validation that skill content meets deployment standards before activation by Claude.

How do I validate that my SKILL.md meets YAML frontmatter requirements?

Validating SKILL.md frontmatter requires checking that mandatory name and description fields are present, alongside concise, actionable guidance loadable by Claude during skill activation.

Does progressive disclosure reduce context load when drafting skill templates?

Progressive disclosure minimizes context load by supporting inline content for immediate guidance while referencing heavy material optionally, keeping the core SKILL.md concise and actionable.

What is the best way to start documenting a new Claude Skill?

Start by creating an initial SKILL.md with required YAML frontmatter and a brief overview, then expand sections progressively as needed to support progressive disclosure structure.

When should I not use test-driven documentation for editing existing skills?

Test-driven documentation is specifically designed for drafting new skills, editing existing ones, or validating deployment standards, making it suitable for all skill maintenance scenarios without explicit limitations.