writing-skills

Document and validate skills using RED-GREEN-REFACTOR workflows with SKILL.md and failing tests first.

Updated Jan 16, 2026

Search Tags:#documentation #flowcharts #skill-discovery #test-driven-development #skill-writing #rationalizations #deployment-checklist

Ready to run

npx skills add https://github.com/Xinm123/MyRecall --skill writing-skills-xinm123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Xinm123/MyRecall/tree/main/openrecall/.trae/skills/writing-skills
Command: npx skills add https://github.com/Xinm123/MyRecall --skill writing-skills-xinm123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill formalizes and enforces a test-driven approach to creating, editing, and validating skills, reducing drift and deployment risk.

Core Features & Use Cases

Frontmatter-driven skill discovery with a strict name/description contract.
RED-GREEN-REFACTOR workflow applied to skill documentation and tests.
Structured deployment checklists and cross-skill references to ensure reuse and consistency.

Quick Start

Upload a SKILL.md at the root of your skill directory, ensure the frontmatter defines name and description, run the validation and testing workflow, and apply the deployment checklist 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 document skills using a test-driven approach?▼

Documenting skills using a test-driven approach requires writing a failing test first, then creating or editing a SKILL.md with YAML frontmatter defining name and description, and finally running deployment checks before publishing.

What is the NO SKILL WITHOUT A FAILING TEST FIRST principle?▼

The NO SKILL WITHOUT A FAILING TEST FIRST principle enforces writing a failing test for skill documentation before creating the actual skill content, ensuring validation and reducing deployment drift within a disciplined RED-GREEN-REFACTOR workflow.

How do I structure a SKILL.md file for skill discovery?▼

Structure a SKILL.md file for skill discovery by including YAML frontmatter with a strict name and description contract, followed by a well-structured Markdown body, and optionally adding scripts, references, and assets directories in the skill root folder.

What deployment checklist is needed before publishing a skill?▼

Before publishing a skill, apply a structured deployment checklist that validates the YAML frontmatter contract, verifies cross-skill references for consistency, and confirms all RED-GREEN-REFACTOR workflow tests pass to ensure deployment readiness.

Can I edit existing skills without breaking cross-skill references?▼

Editing existing skills without breaking cross-skill references requires applying a test-driven validation workflow that checks the structured deployment checklist and verifies frontmatter contracts to ensure reuse and consistency across related skills.

Why does skill documentation require a RED-GREEN-REFACTOR workflow?▼

Skill documentation requires a RED-GREEN-REFACTOR workflow to formalize validation, reduce drift, and enforce deployment-ready checks, ensuring that every skill modification is tested before the final Markdown body and references are published.