writing-skills

Automate skill creation and validation using RED-GREEN-REFACTOR test-driven development.

4|Updated Mar 15, 2024
One-click install
npx skills add https://github.com/izyanrajwani/agent-skills-library --skill writing-skills-izyanrajwani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/izyanrajwani/agent-skills-library/tree/main/skills/writing-skills
Command: npx skills add https://github.com/izyanrajwani/agent-skills-library --skill writing-skills-izyanrajwani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills document the test-driven process for creating, editing, and validating skills, ensuring documentation reflects actual agent behavior and deployment readiness.

Core Features & Use Cases

  • Red-Green-Refactor workflow: captures baseline failures, minimal skill, and gap closing.
  • Rationalization tracking: documents explicit rationalizations and red flags to prevent common shortcuts.
  • Deployment-ready documentation: provides frontmatter, structure, and progressive disclosure guidelines to streamline loading for Claude.
  • Use Cases: creating new skills, editing existing skills, testing skills before deployment.

Quick Start

Run a baseline RED test to observe agent failures, then iteratively write and test the SKILL.md until all scenarios pass

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use test-driven development to write and validate skills?

Test-driven development for skills involves running a baseline RED test to capture initial failures, writing a minimal skill to pass tests, and iteratively refining the SKILL.md file until all deployment scenarios pass.

What is the Red-Green-Refactor workflow for skill documentation?

The Red-Green-Refactor workflow for skill documentation captures baseline failures, creates a minimal skill version, and closes gaps iteratively to ensure the documentation accurately reflects actual agent behavior and deployment readiness.

How do I document rationalization tracking when testing skills?

Rationalization tracking documents explicit rationalizations and red flags during skill testing to prevent common shortcuts, ensuring the iterative refinement process maintains integrity from baseline testing through deployment verification.

Does writing skills require baseline testing without the skill before deployment?

Yes, baseline testing without the skill is required before deployment to observe agent failures, document gaps, and establish a foundation for iteratively refining SKILL.md, including YAML frontmatter and description checks.

What's the best way to structure SKILL.md for deployment readiness?

Structuring SKILL.md for deployment readiness requires proper YAML frontmatter, clear description fields, and progressive disclosure guidelines that streamline loading for Claude during deployment verification checks.

Can I edit existing skills using the same test-driven workflow?

Yes, the test-driven workflow applies across skill creation, editing, and deployment verification, allowing you to run baseline tests, document failures, and iteratively refine existing SKILL.md files until scenarios pass.