writing-skills

Validate Skill documentation with frontmatter schema and RED-GREEN-REFACTOR testing.

22|4|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/ivfarias/ceo --skill writing-skills-ivfarias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ivfarias/ceo/tree/main/.gemini/skills/writing-skills
Command: npx skills add https://github.com/ivfarias/ceo --skill writing-skills-ivfarias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill introduces a test-driven development approach to authoring skills and process documentation, helping teams catch gaps before deployment by enforcing failing tests, documenting rationalizations, and closing loopholes.

Core Features & Use Cases

  • RED-GREEN-REFACTOR workflow for Skills: baseline testing without the Skill to capture failures, then implement, then refactor.
  • Rationalization tables, red flags, and meta-testing patterns to harden documentation under pressure.
  • Cross-skill referencing and progressive disclosure to keep discovery fast and context slim.
  • Structured frontmatter and concise body to optimize Claude discovery and safe deployment.

Quick Start

Create SKILL.md with frontmatter name and description, then write the body using the sections above and provide a minimal example to validate deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply TDD methodology to documentation and skill authoring?

Apply TDD to documentation by using a RED-GREEN-REFACTOR workflow: baseline test failures without the Skill, implement the documentation, then refactor to harden standards and close loopholes.

What is a rationalization table in skill documentation?

A rationalization table in skill documentation captures the reasoning behind decisions, identifies red flags, and applies meta-testing patterns to harden the documentation against edge cases under pressure.

How do I structure frontmatter to optimize Skill discovery and safe deployment?

Structure frontmatter using a strict schema with concise name and description fields to optimize discovery, ensure safe deployment, and maintain a minimal token footprint for Claude.

Does progressive disclosure help reduce token footprint in cross-skill references?

Progressive disclosure reduces token footprint by structuring documentation to reveal context incrementally, keeping discovery fast and context slim while enabling cross-skill references for safe deployment.

When should I not use RED-GREEN-REFACTOR testing for documentation?

Avoid RED-GREEN-REFACTOR testing for simple, static documentation where edge cases are minimal, as the overhead of baseline testing and rationalization tables targets complex, high-pressure skill deployment scenarios.

How do I validate skill documentation before deployment?

Validate skill documentation by creating a SKILL.md file with structured frontmatter, writing the body with required sections, and providing a minimal example to test and confirm safe deployment readiness.