stack-the-deck-close
Skill0 starsChanged 4 months agoMITView on GitHub
Right before the close, line up everything the buyer gets in one stack so the price lands as small against the total — then ask. At the moment of decision — the end of a proposal, the close of a call, the upsell page. When the buyer is about to weigh price against value.
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
- 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
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 16
Before you name the price, remind them of everything they're getting.
≈ “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
Restack the Value Before the Ask
Before you name the price, remind them of everything they're getting. Stack the pieces — each a real, specific thing — so the total dwarfs the number, then make the ask. The order is the whole trick.
The technique
- List the components right before the price, each one concrete: not "support," but "a same-day answer whenever a job's on the line."
- Make every line a real thing with standalone worth — something the buyer would pay for on its own.
- Stack the total so it visibly beats the price. The number should feel small against the pile, not the other way around.
- Name the price once, plainly, right after the stack — not buried, not apologized for.
- Then ask, clearly. The stack earns the right to a direct ask; don't waste it on "let me know your thoughts."
Do this, not that
Do: "You're getting the full build, the brain set up from your real business, three workers configured to your jobs, and a call where I hand you the keys. Separately that's well into four figures of work. It's $997. Want me to send the booking link?"
Don't: Lead with "It's $997" cold, before they've been reminded what's in it — so the number is the first and biggest thing in their head and everything after sounds like justifying.
Why this works
Price feels expensive or cheap only relative to what it's next to. Name it before the value and it's a big number standing alone; name it after a stack of real things and it's a small number against a large total. Same price, opposite feeling. The stack does the persuading; the ask just collects the yes.
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.

