boundary-setting-decline
Skill0 starsChanged 4 months agoMITView on GitHub
Decline a request — a discount, a deadline, an out-of-scope ask — clearly and warmly, so the relationship survives the no. When the answer has to be no: a price you won't drop, work you don't do, a timeline you can't hit. Anytime softening into a maybe would make it worse.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- reversibility-checkSkill
- three-option-framingSkill
- 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
- honest-hedgingSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 23
Don't apologize five times.
- Distinctive: line 24
Keep your voice warm. A firm no said warmly keeps the relationship.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Say No Without Burning the Bridge
A clean no is kinder than a fake maybe. Give the decision plainly, give the one real reason, and offer the door you can hold open — without pretending the answer is yes.
The technique
- Lead with the no, gently but clearly. Don't bury it under three paragraphs of cushioning that make them think it's a yes.
- Give one honest reason, not a defensive essay. "I can't hit Friday and do it right" beats a paragraph of excuses.
- Offer the alternative you can actually deliver — a different date, a different scope, a referral. A no with a door beats a no with a wall.
- Don't apologize five times. One acknowledgment is respect; five is begging.
- Keep your voice warm. A firm no said warmly keeps the relationship; a mushy maybe said to avoid conflict destroys it later.
Do this, not that
Do: "I can't take the price below $4,000 — below that I'm cutting corners I won't put my name on. What I can do is split it into two payments if cash flow's the issue. Want me to set that up?"
Don't: "Hmm, let me see what I can do… I'll try to work something out and get back to you" — when you already know the answer is no, and the maybe just delays the disappointment and adds a broken promise to it.
Why this works
People respect a clear no and resent a slow one. A fake maybe buys you a few comfortable days and then costs you trust when it turns into a no anyway. Saying it straight, warmly, with a real alternative shows the customer you take the relationship seriously enough to be honest with them — which is exactly why they come back.
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.

