writing-skills

Codify a RED-GREEN-REFACTOR workflow for validating skill documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a repeatable RED-GREEN-REFACTOR workflow to ensure skill documentation is tested and free of common rationalizations before deployment.

Core Features & Use Cases

  • Establishes a disciplined workflow (RED-GREEN-REFACTOR) for writing and validating skills.
  • Enables progressive disclosure and multi-file reference patterns to keep context concise.
  • Supports cross-skill references, deployment readiness, and structured testing practices.

Quick Start

Create a Skill by writing SKILL.md with a frontmatter for name and description, then validate it through the RED-GREEN-REFACTOR cycle with failing baseline tests first.

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 test skill documentation to prevent untested agent behaviors?

Skill documentation uses a RED-GREEN-REFACTOR workflow to prevent untested behaviors. You write a SKILL.md file with frontmatter for name and description, then validate the Markdown body and optional scripts through failing baseline tests before deployment.

What is the RED-GREEN-REFACTOR workflow for skill development?

The RED-GREEN-REFACTOR workflow for skill development is a test-driven cycle: write failing baseline tests for skill documentation (RED), validate the SKILL.md to pass tests (GREEN), and refine the structured Markdown body and references (REFACTOR) before deployment.

How do I structure a SKILL.md file for progressive disclosure and cross-skill references?

Structure a SKILL.md file with frontmatter for name and description, followed by a structured Markdown body. Use multi-file reference patterns and optional scripts to keep context concise and support cross-skill references for deployment readiness.

Does test-driven skill documentation work for cross-team projects guiding agent behavior?

Test-driven skill documentation applies to creating and validating new skills across teams and projects, especially where skills guide agent behavior and require testing before deployment. It establishes a disciplined workflow for consistent results.

What's the best way to validate skill deployment readiness before releasing new skills?

The best way to validate skill deployment readiness is to apply a deployment checklist including testing steps within a RED-GREEN-REFACTOR cycle. This prevents common rationalizations and ensures the SKILL.md and optional assets are fully tested.