writing-skills

Design and validate reusable Skills using a RED-GREEN-REFACTOR workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill writing-skills-spursgo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/SPURSGO/awesome-skills-cn/tree/main/writing-skills
Command: npx skills add https://github.com/SPURSGO/awesome-skills-cn --skill writing-skills-spursgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance for writing, validating, and deploying Skills, ensuring consistent structure, frontmatter, and testing discipline across documentation-driven skills.

Core Features & Use Cases

  • Structured SKILL.md: Enforces YAML frontmatter with required fields and a standardized body.
  • TDD-inspired workflow: Encourages RED-GREEN-REFACTOR cycles for skill creation and refinement.
  • Progressive disclosure patterns: Promotes concise, modular content with references/loading only when needed.

Quick Start

Use this Skill to draft a new writing-skill by outlining name and description, then add minimal body content and a small, self-contained example.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write and validate reusable documentation skills?

Using a TDD-inspired workflow ensures reliable skills by capturing baseline failures first, then refining structured content through rationalization tracking and progressive disclosure patterns during deployment.

What is the best way to structure SKILL.md frontmatter and body content?

A standardized SKILL.md enforces required YAML frontmatter fields and modular body content, applying progressive disclosure patterns to keep documentation concise and load references only when needed.

Does test-driven development work for writing documentation skills?

Yes, applying a RED-GREEN-REFACTOR cycle to documentation skills enforces test-first discipline by capturing baseline failures and tracking rationalization, ensuring reliable and validated content deployment.

How do I start creating a new skill with TDD validation?

Begin by outlining the skill name and description, then add minimal body content and a small, self-contained example to initiate baseline failure capture and rationalization tracking.

When should I use progressive disclosure patterns in skill documentation?

Progressive disclosure patterns should be used when modular content requires concise presentation with references loaded on demand, ensuring structured and reliable documentation without overwhelming the user.

Why does my skill validation fail without baseline failure capture?

Without baseline failure capture, the RED-GREEN-REFACTOR workflow cannot enforce test-first discipline, preventing rationalization tracking and undermining the reliability of structured skill content.