creating-skills

Guides creation and testing of agent skills using TDD methodology and trigger optimization.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill creating-skills-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-skills
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/creating-skills
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill creating-skills-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often fail at tasks without proper guidance, and poorly written skills either never trigger or get ignored. This Skill provides a rigorous methodology for authoring, testing, and deploying skills so they reliably change agent behavior. ## Core Features & Use Cases - Skill Anatomy Standards: Defines the required SKILL.md frontmatter (name, description, keywords, paths) and the progressive disclosure structure with optional scripts, references, and assets directories. - TDD-Based Creation Process: Enforces a RED-GREEN-REFACTOR cycle where you must observe an agent failing without the skill before writing it, then close rationalization loopholes. - Claude Search Optimization: Rules for writing trigger-focused descriptions ("Use when...") that avoid workflow summaries, plus keyword coverage and naming conventions. - Use Case: When you notice an agent repeatedly mishandling a task, use this Skill to baseline the failure, author a minimal skill addressing it, pressure-test it, and deploy it via compile-harness.sh. ## Quick Start Ask the agent to create a new skill for a recurring failure pattern, following the TDD baseline-first process defined in this skill.

Frequently Asked Questions about creating-skills

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

FAQPage Schema
How do I create a new agent skill?

Follow the TDD process: first run pressure scenarios without the skill to observe baseline failures, then write a minimal SKILL.md addressing only those failures, and finally refactor by closing rationalization loopholes discovered during retesting.

What should a skill description contain to trigger correctly?

Start with "Use when..." and list triggering conditions, symptoms, and situations rather than summarizing the workflow. Keep it under 500 characters, write in third person, and include searchable keywords like error messages and tool names.

When should I not create a skill?

Skip skills for one-off solutions, standard practices already well-documented, project-specific conventions (use CLAUDE.md instead), and mechanical constraints that can be enforced with automated validation.

How do I test a discipline skill like TDD enforcement?

Use pressure scenarios combining time pressure, sunk cost, and exhaustion, then verify the agent follows the rule under maximum pressure. Build a rationalization table of every excuse observed and add explicit counters for each.

How are skills deployed to different agents?

Author the skill in the vault at 00_meta/skills/<skill-name>/SKILL.md, then run compile-harness.sh --deploy to render it into harness/skills/ and deploy to each agent's directory. Add a targets field in frontmatter to limit which agents receive it.