writing-great-skills

Provides vocabulary and principles for writing and editing predictable AI agent skills.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill writing-great-skills-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/writing-great-skills
Command: npx skills add https://github.com/falentio/cimi --skill writing-great-skills-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective skills for AI agents is hard: descriptions fail to trigger, instructions bloat, and agents behave inconsistently across runs. This Skill supplies a shared vocabulary and a set of principles for designing, structuring, and pruning skills so the agent follows the same process every run. ## Core Features & Use Cases - Invocation Design: Explains the trade-off between model-invoked skills (agent-discoverable, paying context load) and user-invoked skills (human-triggered, paying cognitive load), including router skills for managing many user-invoked skills. - Information Hierarchy: Defines how to rank content into steps, in-file reference, and disclosed reference behind context pointers, using progressive disclosure and co-location to keep SKILL.md legible. - Failure Mode Diagnosis: Catalogs predictable failure modes — premature completion, duplication, sediment, sprawl, no-ops, and negation — each paired with its cure. - Use Case: When editing a skill whose agent keeps skipping steps, consult the failure modes section to diagnose premature completion and apply the fix: sharpen the completion criterion, or split the sequence to hide post-completion steps. ## Quick Start Ask the agent to review your SKILL.md using the writing-great-skills principles and suggest improvements to its description, structure, and pruning.

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, list one trigger per distinct branch, and cut identity statements already covered in the body. Every word in a model-invoked description adds permanent context load, so prune it harder than the body text.

What is the difference between model-invoked and user-invoked skills?

A model-invoked skill keeps its description so the agent and other skills can fire it, paying context load every turn. A user-invoked skill sets disable-model-invocation, making it reachable only by the human typing its name, with zero context load.

When should I split a skill into multiple skills?

Split by invocation when you have a distinct leading word that should trigger a model-invoked skill on its own. Split by sequence when visible upcoming steps tempt the agent into premature completion of the current step.

Why does my agent skip steps when running a skill?

This is premature completion, caused by a vague completion criterion combined with visible post-completion steps pulling attention forward. Sharpen the completion criterion first; only split the sequence if the criterion is irreducibly fuzzy and the rush persists.

Should I use negative instructions like 'do not' in a skill?

Avoid negation because naming the forbidden behavior makes it more available to the model, not less. State the positive target behavior instead, reserving prohibitions for hard guardrails that cannot be phrased positively.