write-agent-skills

Authors and trims Claude Code skills using a test-first workflow with token budgets.

Updated May 19, 2026
One-click install
npx skills add https://github.com/kmosher/claude-plugins --skill write-agent-skills-kmosher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-agent-skills
Source: https://github.com/kmosher/claude-plugins/tree/main/plugins/kmosher-review/skills/write-agent-skills
Command: npx skills add https://github.com/kmosher/claude-plugins --skill write-agent-skills-kmosher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code skills often grow bloated or fail to trigger correctly, degrading instruction quality across all rules. This Skill provides a disciplined, test-first methodology for writing new skills and cutting existing ones down to a size where they still perform. ## Core Features & Use Cases - Test-first authoring: Baseline the failure without the skill (FORGE), then write only the minimal instructions that close the gap (PAVE), so every rule maps to a real pitfall. - Ruthless economy pass: A teammate subagent (CRITIC) cuts filler against a cut-list, flagging anything it is unsure is load-bearing rather than deleting it. - Budget enforcement: Holds bodies to roughly 150 lines and descriptions under 1024 trigger-dense characters, with explicit keep/cut lists and anti-patterns. - Use Case: You notice a skill's description is verbose and its body repeats what the model already knows. Invoke this Skill to re-run its scenarios, trim the filler, and verify no regressions before committing. ## Quick Start Ask the agent to tighten this skill that has grown too long and cut the filler while keeping it under the line budget.

Frequently Asked Questions about write-agent-skills

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

FAQPage Schema
How do I write a Claude Code skill that actually triggers?▼

Put trigger phrases, symptoms, tool names, and error strings in the description field, written in third person, since it alone decides whether the skill fires. Keep triggers out of the body, which does not participate in routing.

How long should a SKILL.md file be?▼

Keep the body under roughly 150 lines or 1.5-2K tokens and the description under 1024 characters. Past that point, quality degrades across all rules, not just the newly added ones, because bloat weakens the instructions you care about.

How do I test whether a skill actually works?▼

Run the skill's real job end-to-end without the skill across varied scenarios to find genuine pitfalls, then write only the instructions that close those gaps. Re-run the scenarios after trimming to catch overcuts and regressions.

What should go in scripts versus references versus SKILL.md?▼

SKILL.md holds the overview and links, in-depth material goes in references loaded on demand, and deterministic or fragile steps go in scripts that execute without loading into context. This progressive disclosure keeps only relevant context in the prompt.

Why does my skill stop working after I trim it?▼

Overcutting removes load-bearing lines, which shows up as regressions when you re-run the original scenarios. Restore the cut line that fixes the regression, and have the critic flag uncertain lines rather than delete them outright.