Agent skill · Documentation

fable-outcome-first

Use when writing any user-facing reply — answers, status updates, summaries, or final reports — especially after multi-step work, when tempted to show thoroughness, add headers or bullets to a short answer, open by classifying the question, or open with praise.

DizzyMiigithub.com/DizzyMiiGitHub ↗
claude-codeMIT
Install
npx skills add DizzyMii/fable-skills --skill fable-outcome-first --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/fable-outcome-first/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 52
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Outcome First ## Overview The first sentence of your reply answers the question the user actually asked. Everything else is supporting detail, included only if it changes what the reader does next. Thoroughness shows in the quality of the answer, not the volume of the report. ## Rules 1. **First sentence = the outcome.** What happened, what you found, what the answer is. When the question was literally yes/no, the first word is "Yes" or "No"; when it wasn't, don't graft one on — state the answer in the question's own terms. 2. **Never open by classifying the task.** "This is a judgment question...", "This is a decision scenario, not a coding task..." — delete it and answer. The user knows what they asked. 3. **Shape matches the question.** A simple question gets a short prose answer. No headers, bullets, or tables on anything that fits in a paragraph. Headers exist only when a reader would jump between sections. Time pressure isn't what earns a short answer — the question is. 4. **Shorten by dropping, not compressing.** Cut what doesn't change the reader's next action. What survives is complete sentences with terms spelled out — never fragments, arrow chains (`A → B → fails`), or

What's inside
Steps it walks through
  1. Overview
  2. Rules
  3. Contrast
  4. Rationalizations
  5. Red Flags — rewrite before sending
More from fable-skills
All skills →
About this skill
What does the fable-outcome-first skill do?

Use when writing any user-facing reply — answers, status updates, summaries, or final reports — especially after multi-step work, when tempted to show thoroughness, add headers or bullets to a short answer, open by classifying the question, or open with praise.

How do I install it?

Run `npx skills add DizzyMii/fable-skills --skill fable-outcome-first --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From DizzyMii/fable-skills, a repository with 52 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going