writing-skills

Create and test AI agent skills using test-driven development methodology.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill writing-skills-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/write-skills
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill writing-skills-salomepoulain

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. This Skill applies test-driven development (RED-GREEN-REFACTOR) to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - TDD-based skill authoring: Run baseline pressure scenarios with subagents, document failures, write the skill, then verify compliance and close loopholes. - Skill Discovery Optimization (SDO): Guidelines for writing trigger-focused descriptions, keyword coverage, naming conventions, and token-efficient content so agents actually find and load the skill. - Failure-matched guidance forms: Choose prohibitions, recipes, structural templates, or conditionals based on the type of baseline failure observed. - Use Case: You want to create a new skill enforcing code review discipline. You first run pressure scenarios without the skill to capture agent rationalizations, then write the skill targeting those exact excuses, and re-test until agents comply under time, sunk-cost, and exhaustion pressure. ## Quick Start Ask the agent to help you create a new skill by first running a baseline pressure scenario with a subagent, then drafting the SKILL.md and verifying compliance.

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?

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by the instructional body. Test it first by running pressure scenarios with subagents without the skill, then verify agents comply once the skill is present.

How to write a good skill description for discovery?

Start the description 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 shortcut instead of reading the full skill body.

What is the TDD approach to writing skills?

It maps RED-GREEN-REFACTOR onto documentation: run a baseline scenario and watch the agent fail (RED), write a minimal skill addressing observed rationalizations (GREEN), then close newly discovered loopholes and re-test (REFACTOR).

When should I not create a skill?

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

Why do agents ignore or bypass skill rules under pressure?

Agents rationalize violations under time, sunk-cost, or exhaustion pressure. Counter this with explicit loophole closures, rationalization tables, red-flag lists, and by matching the guidance form to the observed failure type.