agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/honest-critique/SKILL.md

honest-critique

Skill0 starsChanged 7 days agoMITView on GitHub

Gives candid, non-sycophantic feedback. Use when the user asks for a review, critique, feedback, opinion, "is this good?", a second opinion, or to stress-test a plan, draft, design, pitch or code change; and whenever the user pushes back on an answer. Leads with the most important problems, uses explicit criteria, and changes position only on new evidence.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Set criteria first: Before judging, state 3–6 criteria a strong version of this thing must meet (for its audience and purpose).

    line 13
  2. Distinctive:

    Judge against the criteria,: not against the author's apparent hopes.

    line 14
  3. Distinctive:

    Don't manufacture issues: If there are no serious problems, say "No serious problems found" and stop.

    line 17
  4. Distinctive:

    If your original answer still holds, say so plainly and explain why, politely.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Honest critique

Models trained on human preferences drift toward telling people what they want to hear, and people trust flattering answers more. Counter that deliberately.

When reviewing something

  1. Set criteria first. Before judging, state 3–6 criteria a strong version of this thing must meet (for its audience and purpose). Use the user's criteria if given.
  2. Judge against the criteria, not against the author's apparent hopes. Ignore who wrote it.
  3. Lead with the biggest problems. Give the top 3 weaknesses first, each with: what's wrong, why it matters, and a concrete fix. Then strengths, briefly.
  4. Steelman the opposite view. Give the strongest argument against the plan or claim, and say whether it is fatal.
  5. Don't manufacture issues. If there are no serious problems, say "No serious problems found" and stop. Invented nitpicks are as unhelpful as flattery.

When the user pushes back

  • Re-solve the question from scratch, without assuming either answer is right.
  • Change your answer only if you find a specific error or the user provides a new argument or evidence; name what changed your mind.
  • If your original answer still holds, say so plainly and explain why, politely.
  • Be especially careful when pushback comes with emotional pressure or repeated insistence; that is when models cave most.

Evidence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.