Answer First

Shape every answer so the bottom line comes first. Sentence one is the answer, the number, the verdict or the one thing to do. Everything after it is support. Use when the user asks for output that is short, skimmable, action-led or "no waffle", and keep applying it for the whole conversation once invoked, not just one reply. Triggers on "answer first", "bottom line first", "no preamble", "no waffle", "keep it short", "just tell me what to do", "cut the fluff", "ADHD mode", or any request to stop burying the answer in paragraph four. It shapes Claude's replies to you, not writing you publish.

10 stars 1 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add charlie947/skills-for-everyone

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add charlie947/skills-for-everyone --skill answer-first
Manual install
git clone --depth 1 https://github.com/charlie947/skills-for-everyone.git /tmp/skills-for-everyone
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-everyone/skills/answer-first ~/.claude/skills/answer-first

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# answer-first

> Rules 1 to 10 are adapted from the open-source `i-have-adhd` project, MIT licence, Copyright (c) 2026 Ayoub Ghriss. The full licence text is in LICENSE in this folder.

The answer you wanted is usually in paragraph four. These twelve rules move it to the top of the reply. Once invoked, they apply for the rest of the conversation. They do not expire when the topic changes.

## The rules

0. **BOTTOM LINE UP FRONT.** Sentence one carries the bottom line: the answer, the number, the verdict, or the single thing to do. One sentence. Everything after it is support: evidence, caveats, detail. Never build up to a conclusion that arrives later. **The test: if the reader stops after sentence one, do they have the answer?** If no, the sentence is wrong. If the bottom line is uncertain, sentence one says how sure: 'Most likely X.'

   Never open by narrating the work. Not "found the cause", not "three things changed", not "here is where we are". Those are summaries of an answer, not the answer. State the finding itself.

1. **LEAD WITH THE NEXT ACTION.** When the reply is a how-to, the first line is something the reader can do right now. Not context, not a plan, not a restatement of their question. If the answer is a command, a link, a price or a single sentence, that goes first. Explanation after.

2. **NUMBER MULTI-STEP WORK.** More than one step means a numbered list. One action per step. Never two "and then"s in a single step. Use the fewest steps that still work.
Read the full skill on GitHub

Details

Skill name
answer-first
Path
skills/answer-first/SKILL.md
License
MIT
Repo updated
6 October 2026

FAQ

What does the Answer First skill do?

Shape every answer so the bottom line comes first. Sentence one is the answer, the number, the verdict or the one thing to do. Everything after it is support. Use when the user asks for output that is short, skimmable, action-led or "no waffle", and keep applying it for the whole conversation once invoked, not just one reply. Triggers on "answer first", "bottom line first", "no preamble", "no waffle", "keep it short", "just tell me what to do", "cut the fluff", "ADHD mode", or any request to stop burying the answer in paragraph four. It shapes Claude's replies to you, not writing you publish.

How do I install the Answer First skill?

Claude Code plugin: /plugin marketplace add charlie947/skills-for-everyone. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Answer First popular?

It lives in charlie947/skills-for-everyone, which has 10 GitHub stars and 1 forks.

Related skills

Close

10

charlie947/skills-for-everyone

End a good session properly. Banks what the session taught into Claude's memory so the next session starts smarter, finishes every loose end it can, proves the changes actually landed, and hands back only what genuinely needs you. Four phases, in order: LEARN, FIX, PROVE, REPORT. Use when the user says "close", "/close", "close out", "wrap this up", "are we good to close?", "what's still open?", "anything left?", "did we miss anything", "save progress", "bank what we learned", "remember this for next time", "lock in our corrections", or otherwise signals a session is ending. Not for handing wo

Learning & Education

Improve System

10

charlie947/skills-for-everyone

Mine your own Claude Code history for what keeps going wrong, then fix it at the source. Finds corrections you had to give more than once (a rule should have stopped them), jobs you keep typing by hand (a missing skill), context you keep pasting in (a missing fact), and the kinds of work eating the most hours. Use when the user says "improve the system", "improve my setup", "what am I correcting", "what keeps going wrong", "mine my history", "what skills should I build", "why do I keep repeating myself", or once or twice a week as a routine. Also use with a topic to audit one kind of work that

AI, LLMs & Agents

Prompt Lab

10

charlie947/skills-for-everyone

Turn an idea for a prompt into a finished, tested prompt in one turn. You type the idea, and the prompt comes back in a code block, graded out of 100 against Anthropic's current published prompting guidance (fetched live every run) and a plain bar any reader can run. The pass mark is 95, and Claude runs the prompt itself before handing it over whenever it can. Use when the user wants a prompt written, improved or checked. Triggers on "prompt lab", "write me a prompt", "make this prompt better", "grade this prompt", "score this prompt", "is this prompt any good", "make this prompt expert level"

AI, LLMs & Agents

Carly Product Req

9

carlymr/carlys-claude-skills

Co-author a lightweight product requirements document through structured conversation. Guides non-technical teammates through problem statement, users, goals, success signals, and open questions — producing a short doc (~1 page) that's ready to hand off for a tech spec. Use when writing product requirements, a PRD, feature brief, or scoping a new product idea.

Writing & Content

Adobe Express Document Manipulation

9

Sandgrouse/adobe-express-dev-skill

Create and modify document content in Adobe Express add-ons using Document SDK. Use when planning document operations, inserting shapes/text/media, sequencing sandbox commands, or troubleshooting document edits.

Writing & Content

Carly Tech Spec

9

carlymr/carlys-claude-skills

Co-author a technical design specification through structured conversation. Guides you through problem statement, goals, current state, proposed solution, alternatives, risks, and milestones — with a fixed template and coaching at each step. Use when writing a tech spec, design doc, technical proposal, or RFC.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.