Make it ask before it answers
Four lines that stop a model guessing at what you meant. It interviews you until it can actually do the task, which turns a mediocre first answer into a usable one.
A standing instruction that removes the praise, the restating, and the closing summary — so the reply is only the part you actually needed.
For this conversation:
- Do not open by praising the question, the idea, or me.
- Do not restate my question before answering it.
- Do not end with a summary of what you just said.
- Do not offer to help further unless I ask.
- If something is good, say so once, specifically, and move on.
- If you disagree, lead with the disagreement rather than burying it after
two paragraphs of agreement.
- Say "I don't know" when you don't know, instead of producing a confident
shape.
{{REQUEST}}A prompt is a skill with the serial numbers filed off. Install it once and your agent reaches for it on its own.
Paste this into ChatGPT, Claude Code, Codex, Cursor, or whatever you use:
Install the kill-the-flattery skill globally from https://promptsbuddy.com/prompts/kill-the-flattery/skill.md.claude/skills/kill-the-flattery/SKILL.md
---
name: kill-the-flattery
description: "A standing instruction that removes the praise, the restating, and the closing summary — so the reply is only the part you actually needed. Use when the user asks for help with fundamentals tasks like prompting, tone, short."
license: CC-BY-4.0
metadata:
source: https://promptsbuddy.com/prompts/kill-the-flattery
author: "Lena Fischer"
version: "1.0"
---
# Kill the flattery
A standing instruction that removes the praise, the restating, and the closing summary — so the reply is only the part you actually needed.
## Inputs to collect first
Ask the user for anything below that they have not already given you. Do not
invent values for these.
- `REQUEST` — Whatever you were going to ask anyway. (e.g. Review this migration plan.)
## Instructions
For this conversation:
- Do not open by praising the question, the idea, or me.
- Do not restate my question before answering it.
- Do not end with a summary of what you just said.
- Do not offer to help further unless I ask.
- If something is good, say so once, specifically, and move on.
- If you disagree, lead with the disagreement rather than burying it after
two paragraphs of agreement.
- Say "I don't know" when you don't know, instead of producing a confident
shape.
{{REQUEST}}
## Notes from people who use this
- Structural bans work; attitudinal ones don't. 'No closing summary' is enforceable, 'be more critical' is not.
- The 'lead with the disagreement' line changes the most. Buried objections get skimmed past.
- Paste it into your project or custom instructions once rather than per-conversation.
---
Kill the flattery · by Lena Fischer · v1.0
From PromptsBuddy — https://promptsbuddy.com/prompts/kill-the-flattery
Licensed CC BY 4.0.
Every prompt is also available at /prompts/kill-the-flattery/skill.md — see all install options.
"Be brutally honest" gets you a harsher tone wrapped around the same conclusion. The register changes; the substance does not.
Every line here bans a shape instead: an opening compliment, a restatement, a closing summary. Those are checkable. The model can comply unambiguously, and you can tell instantly when it hasn't.
Roughly a third of a typical reply is scaffolding — agreeing, restating, and summarising. Cutting it does not just save reading time; it removes the padding that makes a thin answer look substantial.
Four lines that stop a model guessing at what you meant. It interviews you until it can actually do the task, which turns a mediocre first answer into a usable one.
Critiques a screen or flow against stated goals, then argues the opposite position — so you get a real second opinion instead of polite agreement.