writing-skills

Create and test agent skills using test-driven development with subagent pressure scenarios.

1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/JaimeHoracio/Ostacky --skill writing-skills-jaimehoracio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/JaimeHoracio/Ostacky/tree/main/assets/skills/writing-skills
Command: npx skills add https://github.com/JaimeHoracio/Ostacky --skill writing-skills-jaimehoracio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing documentation-style skills for AI agents often produces untested instructions that agents ignore or misinterpret under pressure, leading to unreliable behavior in production. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to skill creation, requiring baseline failure tests with subagents before writing any skill content. - Discovery Optimization (CSO): Provides rules for writing descriptions, keywords, and names so future agents can find the skill when it matters. - Rationalization Bulletproofing: Includes patterns for closing loopholes, building rationalization tables, and red-flag lists so discipline-enforcing skills hold up under pressure. - Use Case: When creating a new skill like a code-review checklist, run pressure scenarios with subagents first, document their failures verbatim, then write the minimal skill that makes them comply. ## Quick Start Ask the agent to create a new skill for a recurring technique, starting with baseline pressure-scenario tests before writing the SKILL.md file.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a new skill for an AI agent?▼

Follow the TDD cycle: first run pressure scenarios with subagents without the skill to document baseline failures, then write a minimal SKILL.md addressing those failures, and finally refactor to close loopholes agents discover during retesting.

What should a SKILL.md description field contain?▼

The description should start with "Use when..." and list only triggering conditions, symptoms, and situations in third person. Never summarize the skill's workflow, because agents may follow the description instead of reading the full skill body.

How do I test that a skill actually works?▼

Run pressure scenarios with subagents combining stresses like time pressure, sunk cost, and exhaustion. Discipline skills need compliance testing, technique skills need application scenarios, and reference skills need retrieval tests.

When should I not create a skill?▼

Skip skill creation for one-off solutions, well-documented standard practices, project-specific conventions that belong in AGENTS.md, and mechanical constraints that can be enforced with regex or validation scripts instead of documentation.

Why do agents ignore or bypass skill rules?▼

Agents rationalize under pressure, finding loopholes like claiming to follow the spirit of the rules. Counter this with explicit forbidden workarounds, rationalization tables, red-flag lists, and a statement that violating the letter violates the spirit.