writing-skills

Apply test-driven development cycles to author and validate SKILL.md files.

483|58|Updated Aug 14, 2019
One-click install
npx skills add https://github.com/Trevoke/org-gtd.el --skill writing-skills-trevoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Trevoke/org-gtd.el/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/Trevoke/org-gtd.el --skill writing-skills-trevoke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a disciplined approach to creating and validating CLAUDE skills by applying test-driven development to process documentation, ensuring skills are well-structured before deployment.

Core Features & Use Cases

  • TDD-driven skill authoring: write skills only after defining failing tests, then verify with RED-GREEN-REFACTOR cycles.
  • Structured frontmatter requirements: enforce YAML frontmatter with name and description; keep prompts concise.
  • General workflows include editing, versioning, and pilot verification across agents.

Quick Start

Use the writing-skills skill to draft a new skill document, ensure SKILL.md frontmatter contains name and description starting with Use when..., and outline RED-GREEN-REFACTOR steps.

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 skill documentation?

Test-driven documentation requires defining failing tests for your skill's requirements before writing the actual content, then verifying the behavior through RED-GREEN-REFACTOR cycles until the tests pass.

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

A valid SKILL.md file requires YAML frontmatter containing name and description fields, with the description starting with 'Use when...', supported by a minimal structure for optional scripts, references, and assets.

How do I validate deployed skills across different Claude workflows?

Validating deployed skills involves running the RED-GREEN-REFACTOR testing cycles against the skill documentation across target Claude deployments, teams, and workflows to ensure structural compliance and functional accuracy.

Can I edit existing skill documents without breaking their verification tests?

Editing existing skills requires maintaining the YAML frontmatter requirements and running the RED-GREEN-REFACTOR cycle to ensure changes do not break the defined test cases for the deployed skill.

What is the best way to structure frontmatter for new skill creation?

The best way to structure frontmatter for new skill creation is using YAML syntax with concise name and description fields, ensuring the description follows the 'Use when...' format for clear prompt definition.

Why does my skill documentation fail pilot verification across agents?

Skill documentation fails pilot verification when it lacks the required YAML frontmatter structure, missing the 'Use when...' description format, or when the content does not pass the defined RED-GREEN-REFACTOR test cycles.