writing-great-skills

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill writing-great-skills-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/productivity/writing-great-skills
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill writing-great-skills-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective agent skills is hard: descriptions that fail to trigger, bloated SKILL.md files, duplicated content, and agents that rush steps or ignore instructions. This Skill provides a shared vocabulary and a set of principles for diagnosing and fixing these problems so skills behave predictably on every run. ## Core Features & Use Cases - Invocation design: Decide between model-invoked and user-invoked skills by trading context load against cognitive load, and write trigger-rich descriptions. - Information hierarchy: Arrange steps and reference material across in-file content and progressively disclosed files like GLOSSARY.md. - Failure-mode diagnosis: Identify and fix premature completion, duplication, sediment, sprawl, and no-op instructions using concrete remedies. - Use Case: When an agent keeps firing the wrong skill or rushing through steps, consult this reference to sharpen the description's trigger words or split the step sequence. ## Quick Start Ask the agent to review your SKILL.md using the writing-great-skills principles and 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 agent invocation?

Front-load the skill's leading word and list one trigger per branch, since every word adds context load. Collapse synonym triggers that rename a single branch, and cut identity statements already covered in the body.

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

Choose model-invocation only when the agent or another skill must reach it autonomously, since the always-loaded description costs context load. If it only ever fires by hand, set disable-model-invocation: true and pay no context load.

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

Sharpen the step's completion criterion first so done is clearly checkable, which is cheap and local. Only if the criterion is irreducibly fuzzy and you observe the rush, split the sequence to hide post-completion steps.

What is progressive disclosure in a SKILL.md file?

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

What are the common failure modes when writing agent skills?

The five failure modes are premature completion, duplication, sediment, sprawl, and no-op instructions. Each has a paired remedy: sharpen criteria, keep a single source of truth, prune stale lines, disclose reference, and delete lines the model already obeys by default.