writing-skills

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

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill writing-skills-grupo-6-ads-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Grupo-6-ADS-B/FittNutri/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/Grupo-6-ADS-B/FittNutri --skill writing-skills-grupo-6-ads-b

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing effective agent skills without testing leads to documentation that agents ignore, misinterpret, or rationalize away under pressure. This Skill applies test-driven development to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - TDD-Based Skill Authoring: Follows the RED-GREEN-REFACTOR cycle, running baseline pressure scenarios with subagents before writing any skill content. - Rationalization Bulletproofing: Provides techniques to close loopholes, build rationalization tables, and create red-flag lists that keep agents compliant under time, sunk-cost, and authority pressure. - Discovery Optimization (CSO): Defines rules for names, descriptions, keywords, and token efficiency so future agents can find and correctly trigger the skill. - Use Case: When creating a new discipline-enforcing skill like TDD or verification-before-completion, run baseline scenarios without the skill, document the agent's exact excuses, then write minimal content that counters those specific rationalizations and re-test until bulletproof. ## Quick Start Ask the agent to create a new skill for a recurring technique, requiring baseline pressure-scenario testing with subagents 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 agent skill with SKILL.md?

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, followed by markdown instructions. Test it first by running pressure scenarios with subagents without the skill, then write content addressing the failures you observed.

How to test a skill before deploying it?

Run realistic pressure scenarios combining time, sunk cost, and authority pressures with a subagent that lacks the skill, and document its exact rationalizations. Then verify the agent complies when the skill is present, and refactor to close any new loopholes.

What should a SKILL.md description field contain?

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

When should I not create a skill?

Skip skill creation for one-off solutions, project-specific conventions that belong in CLAUDE.md, well-documented standard practices, 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, time pressure, or spirit-versus-letter arguments. Bulletproof skills counter this with explicit negations, rationalization tables, red-flag lists, and foundational principles stated early.