writing-skills

Author and validate Skills using a test-driven RED-GREEN-REFACTOR workflow.

1|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/orbtyapp/orbty-eazy --skill writing-skills-orbtyapp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/orbtyapp/orbty-eazy/tree/main/skills/writing-skills
Command: npx skills add https://github.com/orbtyapp/orbty-eazy --skill writing-skills-orbtyapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to writing, validating, and maintaining Skills as living documentation, ensuring they are testable, reusable, and robust under pressure.

Core Features & Use Cases

  • TDD-based workflow: RED-GREEN-REFACTOR cycle applied to skill documentation, including pressure scenarios and rationalization tracking.
  • Guided structure: Encourages YAML frontmatter with name and description, concise description, and optional references or scripts.
  • Quality assurance: Checklists and testing guidance to verify Skills before deployment.
  • Use Case: Authors draft a new Skill, run baseline tests without the Skill, then refine to cover observed rationalizations.

Quick Start

Create a new Skill by adding a SKILL.md with frontmatter including name and description. Write the Skill body following the three-section pattern and the SKILL.md structure. Then perform a RED-GREEN-REFACTOR cycle by first drafting pressure scenarios without the skill, then implementing the Skill to address observed rationalizations, and finally iterating to close loopholes with counters and red flags.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write testable skill documentation for Claude?▼

To write testable skill documentation for Claude, use a test-driven development approach by drafting pressure scenarios first, then implementing the skill body to address observed rationalizations, and iterating to close loopholes.

What is the TDD workflow for creating and validating skills?▼

The TDD workflow for creating and validating skills follows a RED-GREEN-REFACTOR cycle: draft baseline tests without the skill, implement the skill to pass those tests, then refine to close loopholes with counters and red flags.

Do I need YAML frontmatter in SKILL.md files?▼

Yes, you need YAML frontmatter in SKILL.md files. The framework requires including both name and description fields in the frontmatter block to properly define and structure the skill for agent behavior.

How do I ensure skill reliability before deployment?▼

To ensure skill reliability before deployment, use the provided quality assurance checklists and testing guidance to verify the skill, tracking rationalizations observed during pressure scenarios to confirm robustness.

Can I include external scripts and references when authoring skills?▼

Yes, you can include external scripts and references when authoring skills. The guided structure supports optional directories specifically designed to handle heavy references alongside the core SKILL.md file.

Why does my Claude skill fail under pressure scenarios?▼

Your Claude skill fails under pressure scenarios when it contains loopholes in the documentation. Applying the REFACTOR phase of the TDD cycle closes these gaps by adding counters and red flags to guide behavior.