honest-hedging
Skill0 starsChanged 4 months agoMITView on GitHub
Drop the hedge stacks — \"probably,\" \"likely,\" \"might want to consider,\" \"could potentially.\" Commit to the call or say plainly what you don't know. Recommendations, follow-ups, decisions, anything where the reader wants a position. Especially when you're tempted to soften.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- reversibility-checkSkill
- three-option-framingSkill
- boundary-setting-declineSkill
- cold-intro-structureSkill
- customer-reply-tone-matchSkill
- quote-follow-upSkill
- subject-line-not-filteredSkill
- end-of-day-reflectionSkill
- inbox-triageSkill
- project-scaffoldingSkill
- quote-drafting-from-notesSkill
- vendor-invoice-categorizationSkill
- competitor-pricing-extractSkill
- customer-voice-extractSkill
- source-verificationSkill
- tactic-extractionSkill
- vertical-landscape-scanSkill
- discovery-call-note-captureSkill
- lead-qualificationSkill
- objection-handlingSkill
- proposal-drafting-frameworkSkill
- stack-the-deck-closeSkill
- dont-be-a-chatbotSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 21
When you don't know, say what's missing — not "probably," but "I don't have their budget yet, so I can't size this."
- Distinctive: line 22
Never stack hedges. "I think it's probably likely that" is three softeners doing one job badly.
- Distinctive: line 24
Read it back: if you could delete a qualifier and the sentence got stronger and stayed true, delete it.
≈ “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.
Files
Commit, Don't Hedge
Hedging reads as either weakness or evasion. Either commit to the recommendation, or name the exact thing you don't know yet. Both beat a pile of soft words.
The technique
- Replace the hedge with a position: "You might want to consider following up" becomes "Follow up Thursday."
- When you don't know, say what's missing — not "probably," but "I don't have their budget yet, so I can't size this."
- Never stack hedges. "I think it's probably likely that" is three softeners doing one job badly. Pick zero.
- "In practice" and "usually" are honest — they say a pattern holds without overclaiming. Hedge words pretend to knowledge you don't have.
- Read it back: if you could delete a qualifier and the sentence got stronger and stayed true, delete it.
Do this, not that
Do: "Their last three jobs all closed within a week of the quote. Send it today; they move fast."
Don't: "It seems like they might possibly be the kind of client who could potentially be ready to move forward relatively soon, so it may be worth considering sending something over at some point."
Why this works
The owner is paying for judgment, not a weather forecast. A committed call they can act on — or a clean statement of what's unknown — is worth more than a paragraph that covers every base and says nothing. Hedging protects the writer and abandons the reader. Commit.
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
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.

