skills.rest
rapyuta-robotics
rapyuta-roboticsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

writing-skills

Enforce test-driven documentation with RED-GREEN-REFACTOR for Skill files.

Updated Aug 23, 2026
Search Tags:#workflow#documentation#TDD#discovery#quality#frontmatter#skill-writing
One-click install
npx skills add https://github.com/rapyuta-robotics/agent-ai --skill writing-skills-rapyuta-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/rapyuta-robotics/agent-ai/tree/main/skills/writing-skills
Command: npx skills add https://github.com/rapyuta-robotics/agent-ai --skill writing-skills-rapyuta-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and validating Skills requires structure, testing discipline, and a tight frontmatter contract. This Skill applies a test-driven approach to drafting Skill documentation to ensure discoverability, reliability, and safe deployment.

Core Features & Use Cases

  • Enforces a RED-GREEN-REFACTOR cycle for documenting new Skills and editing existing ones.
  • Ensures YAML frontmatter includes only name and description and remains concise.
  • Provides guidance on creating triggering descriptions and lightweight reference patterns for Skills.
  • Useful when creating new Skills or refining existing ones for production readiness.

Quick Start

Draft a SKILL.md that includes a minimal frontmatter and body, then simulate a RED-GREEN-REFACTOR cycle to validate its effectiveness.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write documentation for new Skills?▼

To write Skill documentation, draft a SKILL.md with minimal YAML frontmatter containing only name and description, then apply a test-driven RED-GREEN-REFACTOR workflow to validate triggering effectiveness and deployment readiness.

What is test-driven documentation and how does it work for Skills?▼

Test-driven documentation applies a RED-GREEN-REFACTOR cycle to validate Skill reliability and discoverability. You write triggering descriptions, test them, and refactor the SKILL.md content until it meets verifiable quality standards.

Can I use YAML frontmatter fields beyond name and description when creating Skills?▼

No, creating Skills requires explicit frontmatter constraints where YAML includes only name and description. Keeping frontmatter concise ensures proper validation and reliable discovery under the test-driven documentation workflow.

What's the best way to validate a Skill for production readiness?▼

The best way to validate production readiness is simulating a RED-GREEN-REFACTOR cycle on your SKILL.md. This test-driven approach verifies that descriptions start with Use when and the documentation meets strict frontmatter constraints.

Why does my Skill documentation fail discovery checks?▼

Skill documentation fails discovery checks when frontmatter constraints are violated or descriptions lack the Use when triggering pattern. Applying the RED-GREEN-REFACTOR workflow identifies and resolves these structural documentation issues.

Related Skills

Explore More Content & Communication Skills→
srprasannasrprasanna
11

minimal-example

Create a minimal Claude Skill skeleton with required frontmatter fields.

Community
Basic
hyxkleehyxklee

red-green-refactor

Guide Kotlin/JVM developers through TDD Red-Green-Refactor cycles with Kotest DescribeSpec.

Community
Intermediate
ribeirogabribeirogab
3

broken-layout

Detect misplaced README.md and nested reference files in skill folders.

Community
Basic
HolobiomicsLabHolobiomicsLab
4

clinical-reports

Generate CARE-compliant clinical reports with automated privacy validators.

Official
Advanced