skills.rest
Sjw2005
Sjw2005COMMUNITY
Explore all skills by this author →
GitHub

writing-skills

Create and maintain structured SKILL.md documentation with test-driven workflows.

Updated Aug 27, 2026
Search Tags:#workflow#tdd#documentation#progressive-disclosure#skill-authoring#writing-skills
One-click install
npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill writing-skills-sjw2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill writing-skills-sjw2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams struggle to create consistent, testable Skill documentation that is easy to discover and reuse. This guide provides a structured approach to writing, testing, and evolving Skills to ensure they remain clear, verifiable, and maintainable.

Core Features & Use Cases

  • TDD-inspired Skill creation: apply RED-GREEN-REFACTOR to documentation to prevent drift and loopholes.
  • Progressive disclosure: organize content so Claude loads only what is needed and heavy references are optional.
  • Structured SKILL.md discipline: ensures frontmatter with name and description enables discovery; optional references/assets extend guidance as needed.

Quick Start

Draft a new SKILL.md with a concise frontmatter and minimal body, then run the RED-GREEN-REFACTOR testing workflow to validate it.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write testable Skill documentation that prevents drift?▼

Progressive disclosure organizes Skill documentation so Claude loads only the necessary content, keeping heavy references optional and preventing context bloat during execution.

What is the best way to structure a SKILL.md for discoverability?▼

The best way to structure a SKILL.md for discoverability is using YAML frontmatter with name and description fields, optionally extending guidance with references/, scripts/, and assets/ directories.

Can I use test-driven development for documentation across different Skill types?▼

Yes, you can use test-driven development for documentation across Technique, Pattern, and Reference Skill types, applying iterative testing and red flags to ensure reusability.

How do I validate a new Skill before publishing it?▼

To validate a new Skill, draft a concise SKILL.md with minimal body content, then run the RED-GREEN-REFACTOR testing workflow to identify loopholes and verify structural integrity.

What are the limitations of progressive disclosure in Skill authoring?▼

A limitation of progressive disclosure is that it requires strict content organization; if heavy references are not properly separated into optional directories, Claude may load unnecessary context.

Related Skills

Explore More Content & Communication Skills→
alexsandrocruzalexsandrocruz
6

writing-skills

Validate Claude skill documentation using test-driven development with subagents.

Community
Intermediate
obraobra
41

Creating Skills

Automate skill documentation and validation through test-driven development cycles.

Community
Basic
mmartinsolivmmartinsoliv

write-a-skill

Create reusable agent skills with SKILL.md and optional resource files.

Community
Intermediate
Phife726Phife726

writing-skills

Create and validate Skills using a RED-GREEN-REFACTOR cycle.

Community
Advanced