writing-skills

Create and validate Skills through red-green-refactor cycles with SKILL.md.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill writing-skills-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/writing-skills
Command: npx skills add https://github.com/DuySeu/StockMind --skill writing-skills-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authors often craft Skills without a disciplined validation process. This guide enables test-driven writing for Skills, ensuring baselines are observed and improvements are verified before deployment.

Core Features & Use Cases

  • RED-GREEN-REFACTOR workflow guidance for Skill creation and editing
  • Pressure-scenario testing to capture rationalizations and counter them with explicit rules
  • Deployment-ready patterns: rationalization tables, red flags, and a concise deployment checklist
  • Progressive disclosure and cross-reference strategies to keep context lean

Quick Start

Run a RED-GREEN-REFACTOR cycle on a new or edited Skill by validating baseline behavior first, then drafting SKILL.md to address observed failures.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to skill writing?

Test-driven skill writing validates baseline behavior first, then drafts SKILL.md to address observed failures through iterative red-green-refactor cycles before deployment.

What is a red-green-refactor cycle for SKILL.md documentation?

A red-green-refactor cycle for SKILL.md documentation observes baseline failures, drafts rules to make tests pass, and refines instructions to ensure reliability across pressure scenarios.

How do I validate skill quality assurance before deployment?

Skill quality assurance validation uses pressure-scenario testing to capture rationalizations, counter them with explicit rules, and verify improvements against a deployment checklist.

What's the best way to structure SKILL.md for reliable workflows?

Structuring SKILL.md for reliable workflows requires rationalization tables, red flags, progressive disclosure, and cross-reference strategies to keep context lean and ensure deployment readiness.

When do I need a rationalization table in skill documentation?

A rationalization table in skill documentation is needed when pressure-scenario testing reveals edge cases that require explicit rules to counter observed failures and ensure reliable behavior.

Can I use test-driven development for editing existing skills?

Test-driven development for editing existing skills applies red-green-refactor cycles to validate baseline behavior first, then iteratively refines SKILL.md to address newly observed failures.