writing-skills

Organize and validate skill documentation into test-driven Skill units.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a formal, test-driven approach to documenting and authoring other Skills, reducing miscommunication and deployment risk.

Core Features & Use Cases

  • TDD-inspired skill documentation workflow: write, test, and refactor Skill units before deployment.
  • Pressure-testing format: capture baseline failures and rationalizations to close loopholes.
  • Deployment readiness: ensures SKILL.md frontmatter and structure support discovery and reuse.

Quick Start

Run the RED-GREEN-REFACTOR cycle on a brand-new Skill to verify it meets quality and testability before publishing.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write test-driven documentation for new skills?

To write test-driven documentation, run the RED-GREEN-REFACTOR cycle to capture baseline failures and rationalizations. This pressure-testing format validates self-contained skill units before deployment, closing loopholes in your skill authoring workflow.

What is a RED-GREEN-REFACTOR loop for skill authoring?

A RED-GREEN-REFACTOR loop for skill authoring is a testing cycle that captures baseline failures, verifies fixes, and refactors skill units. It enforces testability and structure to ensure deployment readiness across the skill library.

How do I verify deployment readiness for skill documentation?

Verify deployment readiness by checking that SKILL.md frontmatter contains required name and description fields. The skill validation process also derives dependencies and component presence directly from the skill's filesystem structure.

What is the best way to structure SKILL.md frontmatter for discovery?

The best way to structure SKILL.md frontmatter is ensuring it contains explicit name and description attributes. Proper frontmatter formatting supports skill discovery and reuse across the library while meeting testability requirements.

Why does my skill documentation fail deployment validation?

Skill documentation fails deployment validation when SKILL.md frontmatter lacks a name or description, or when filesystem dependencies and component presence do not align with the documented skill structure and rationalizations.