writing-great-skills

Provides vocabulary and principles for writing predictable AI agent skills.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/QT-7274/dotfiles --skill writing-great-skills-qt-7274
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/QT-7274/dotfiles/tree/main/writing-great-skills
Command: npx skills add https://github.com/QT-7274/dotfiles --skill writing-great-skills-qt-7274

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing skills for AI agents often produces bloated, duplicated, or unreliable instructions that cause inconsistent agent behavior. This Skill supplies a shared vocabulary and decision framework for structuring, invoking, and pruning skills so agents follow the same process on every run. ## Core Features & Use Cases - Invocation Design: Decide between model-invoked and user-invoked skills by weighing context load against cognitive load, with concrete mechanics like disable-model-invocation. - Information Hierarchy: Organize content into steps, in-skill reference, and disclosed reference behind context pointers, using progressive disclosure and branching as the test. - Failure Mode Diagnosis: Identify and fix premature completion, duplication, sediment, sprawl, no-ops, and negation in existing skills. - Use Case: When a skill you wrote fires unreliably or the agent rushes through steps, consult this reference to sharpen completion criteria, split sequences, or rewrite the description with leading words. ## Quick Start Review my skill file and diagnose which failure modes are hurting its predictability, then suggest concrete edits.

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 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.

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

Choose model-invocation only when the agent or another skill must reach it autonomously, accepting the context load of an always-loaded description. If it only ever fires by hand, set disable-model-invocation and pay zero context load.

How do I stop an AI agent from rushing through skill steps?▼

Sharpen the step's completion criterion first so done is clearly distinguishable from not-done. Only if the criterion is irreducibly fuzzy and you observe the rush, hide post-completion steps by splitting the sequence across a real context boundary.

What is progressive disclosure in skill writing?▼

Progressive disclosure moves reference material out of SKILL.md into linked files reached by context pointers, keeping the top of the file legible. Inline what every branch needs and disclose what only some branches reach.

Why should I avoid negative instructions in prompts?▼

Prohibitions drag the forbidden behavior into context and make it more available, not less, since the negation is a weak modifier the named concept overruns. State the positive target behavior instead, reserving prohibitions for hard guardrails.