do-writing-great-skills

Provides vocabulary and principles for writing predictable AI agent skills.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-writing-great-skills-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-writing-great-skills
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/harness/do-writing-great-skills
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-writing-great-skills-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing skills for AI agents often produces bloated, unreliable instructions that fire inconsistently or steer the agent unpredictably. This Skill supplies a shared vocabulary and set of principles for authoring and editing skills so the agent follows the same process on every run. ## Core Features & Use Cases - Invocation Design: Guidance on choosing between model-invoked skills (with a description, agent-discoverable) and user-invoked skills (typed by hand, zero context load), including router skills for managing many user-invoked ones. - Information Hierarchy: A ladder model for arranging steps, in-file reference, and disclosed reference behind context pointers, with progressive disclosure and co-location rules. - Failure Mode Diagnosis: Named failure modes — premature completion, duplication, sediment, sprawl, no-op, and negation — each paired with its cure, plus a full glossary in GLOSSARY.md. - Use Case: When editing an existing skill that the agent triggers inconsistently, consult this reference to sharpen the description's trigger wording, prune no-op lines, and split sequences that cause premature completion. ## Quick Start Review my skill file and apply the writing-great-skills principles to make it more predictable.

Frequently Asked Questions about do-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 and write one trigger per branch, since synonyms that rename a single branch are duplication. Keep the description to triggers plus any reach clause for other skills, because every word adds permanent context load.

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: true, 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 post-completion steps tempt the agent to rush the current step, causing premature completion.

Why does my AI agent skip steps or finish tasks early?▼

This is premature completion, caused by a vague completion criterion combined with visible upcoming steps. Sharpen the completion criterion first to make it checkable; only hide later steps by splitting if the criterion is irreducibly fuzzy and the rush is observed.

Should I use negative instructions like 'do not' in prompts?▼

Avoid negation because naming the forbidden behavior makes it more available to the model, not less. Prompt the positive target behavior instead, reserving prohibitions for hard guardrails you cannot phrase positively, paired with what to do instead.