writing-great-skills

Guides writing and editing agent skills for predictable behavior using defined vocabulary and principles.

2|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/NAMEWTA/learning-open-code --skill writing-great-skills-namewta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/NAMEWTA/learning-open-code/tree/main/speculo/skills/writing-great-skills
Command: npx skills add https://github.com/NAMEWTA/learning-open-code --skill writing-great-skills-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent skills often behave unpredictably across runs because their instructions, descriptions, and structure are poorly designed. This Skill provides a shared vocabulary and concrete principles for writing and editing skills so agents follow the same process every time. ## Core Features & Use Cases - Invocation Design: Decide between model-invoked and user-invoked skills by weighing context load against cognitive load, and configure disable-model-invocation accordingly. - Information Hierarchy: Organize content into steps, in-file references, and disclosed references behind context pointers, using progressive disclosure to keep SKILL.md lean. - Failure-Mode Diagnosis: Identify and fix premature completion, duplication, sediment, sprawl, no-op instructions, and negation using the paired glossary in GLOSSARY.md. - Use Case: When a skill you wrote triggers unreliably or the agent rushes through steps, consult this guide to sharpen completion criteria, rewrite the description with leading words, and split sequences that cause premature completion. ## Quick Start Ask the agent to review your SKILL.md against the writing-great-skills principles and suggest concrete edits to improve predictability.

Frequently Asked Questions about writing-great-skills

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

FAQPage Schema
How do I write a good skill description for an AI agent?▼

Front-load the skill's leading word, include one trigger phrase per distinct branch, and remove identity information already in the body. Every word adds context load, so prune the description more aggressively than the body text.

When should a skill be model-invoked vs user-invoked?▼

Choose model-invoked only when the agent must trigger the skill itself or other skills must reach it, since its description stays loaded every turn. If only humans trigger it, set disable-model-invocation to true to avoid context load.

How do I stop an agent from finishing steps too early?▼

First sharpen the completion criterion so done versus not-done is clearly checkable. Only if the criterion is irreducibly vague and rushing persists, split the step sequence so post-completion steps are hidden from the current context.

What is progressive disclosure in agent skills?▼

Progressive disclosure moves reference material out of SKILL.md into linked files reached through context pointers, keeping the top level clear. Inline material every branch needs and disclose material only some branches require.

Why should I avoid negative instructions in prompts?▼

Negation drags the forbidden behavior into context, making it more available to the model rather than less. State the target behavior positively instead, reserving prohibitions for hard guardrails paired with an alternative action.