writing-skills

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

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/thienty1207/Hotel_Staff --skill writing-skills-thienty1207
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/thienty1207/Hotel_Staff/tree/main/.baron/core/skills/superpowers/writing-skills
Command: npx skills add https://github.com/thienty1207/Hotel_Staff --skill writing-skills-thienty1207

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing effective agent skills is hard because untested documentation often fails under real-world pressure, and authors cannot know if a skill actually changes agent behavior without watching agents fail without it first. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to documentation by running baseline pressure scenarios with subagents before writing any skill content. - Skill Discovery Optimization: Provides rules for writing descriptions, names, and keywords so future agents can find the skill when they need it. - Rationalization Bulletproofing: Supplies rationalization tables, red flag lists, and persuasion principles to close loopholes agents exploit under time, sunk-cost, or authority pressure. - Use Case: When creating a new discipline-enforcing skill like a testing requirement, run pressure scenarios with subagents first, document their exact excuses, then write the minimal skill that counters those specific rationalizations. ## Quick Start Use the writing-skills skill to create a new agent skill following the test-driven development process with baseline pressure scenario testing.

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 agent skill with SKILL.md?

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, followed by markdown instructions. Run baseline pressure scenarios with subagents first to document failures, then write the minimal skill addressing those specific rationalizations.

How do I test that a skill actually works before deploying it?

Run pressure scenarios combining three or more pressures like time, sunk cost, and authority with subagents, both without the skill to capture baseline failures and with the skill to verify compliance. Iterate by closing loopholes until agents comply under maximum pressure.

What should go in a skill description field?

Write the description in third person starting with "Use when..." followed by specific triggering conditions, symptoms, and situations. Never summarize the skill's workflow in the description, because agents may follow the description shortcut instead of reading the full skill body.

When should I not create a new skill?

Skip skill creation for one-off solutions, standard practices already well-documented elsewhere, project-specific conventions that belong in an instructions file, and mechanical constraints that can be enforced with validation or automation instead of documentation.

Why do agents ignore skills under pressure?

Agents rationalize violations using excuses like sunk cost, pragmatism, or spirit-versus-letter arguments. Counter this with explicit negations of each loophole, rationalization tables, red flag lists, and foundational principles stating that violating the letter violates the spirit.