skills.rest
tuantiensiu
tuantiensiuCOMMUNITY
Explore all skills by this author →
GitHub

writing-skills

Draft and validate SKILL.md documentation using TDD baseline tests.

1|Updated Jan 10, 2026
Search Tags:#subagents#quality-assurance#process-documentation#test-driven-development#skill-authoring#writing-skills
One-click install
npx skills add https://github.com/tuantiensiu/todo-app --skill writing-skills-tuantiensiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/tuantiensiu/todo-app/tree/main/.opencode/skill/writing-skills
Command: npx skills add https://github.com/tuantiensiu/todo-app --skill writing-skills-tuantiensiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, reusable Skill documentation is challenging under pressure. This guide demonstrates a test-driven approach to crafting bulletproof Skills with concise frontmatter and structured content.

Core Features & Use Cases

  • Structured frontmatter: YAML frontmatter with name and description to enable discovery and quick onboarding.
  • Progressive disclosure: Inline guidance with references for deep dives, reducing token load in Claude prompts.
  • Quality assurance: RED-GREEN-REFACTOR loop to validate skills before deployment and prevent rationalizations.
  • Use Case: Create a new Skill for a repeatable pattern, iterate through baseline failures, and publish a robust reference.

Quick Start

Draft a minimal SKILL.md for a new capability, then test baseline scenarios and iterate until the skill is bulletproof.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write Skill documentation using test-driven development?▼

To write Skill documentation using test-driven development, draft a minimal SKILL.md and validate it through a RED-GREEN-REFACTOR loop. This ensures the skill is testable, concise, and bulletproof before deployment.

What is progressive disclosure in skill authoring?▼

Progressive disclosure in skill authoring provides inline guidance with references for deep dives. This reduces token load in Claude prompts by structuring content so only necessary details surface initially.

How do I validate skill documentation before deployment?▼

You validate skill documentation by testing baseline scenarios and iterating until the skill is bulletproof. This quality assurance process prevents rationalizations and ensures accuracy before the skill is published.

What format should SKILL.md frontmatter follow?▼

SKILL.md frontmatter should follow YAML format with name and description fields. This structured frontmatter enables discovery and quick onboarding for the skill.

Does skill authoring require CSO optimization?▼

Skill authoring includes guidelines for CSO optimization. This ensures the skill content is structured effectively for discovery while maintaining a clear, compact body.

What are the limitations of using TDD for skill writing?▼

Using TDD for skill writing requires iterating through baseline failures to prevent rationalizations. If the initial minimal SKILL.md is not drafted carefully, the RED-GREEN-REFACTOR loop may require extensive iterations to achieve a robust reference.

Related Skills

Explore More Content & Communication Skills→
can1357can1357
23.2k

valid-skill

Validate Skill Unit discovery with a minimal SKILL.md frontmatter entry.

Community
Basic
venikmanvenikman

fpf-generate-pattern

Convert E.8 FPF patterns into validated Agent Skill packages.

Community
Intermediate
cookeyholdercookeyholder

writing-skills

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

Community
Advanced
SergeiGolosSergeiGolos
1

doc-architect

Scaffold software architecture documentation using arc42 and C4 model templates.

Community
Intermediate