THE SAYING-NO SCRIPT LIBRARY

12 scripts for the 12 most common asks — volunteer for this, host this, take on this project, attend this thing, lend this. All in your voice. Polite. Firm. No JADE (justify-argue-defend-explain). Send. Move on.

THE PROBLEM

You said yes when you meant no. The work piles up. The resentment builds. The "no" you needed to say last Tuesday becomes a fight on Friday.

You know how to say no in theory. You can't say it in practice because:

You don't have words ready
You're afraid of what they'll say back
You over-explain when you do say it (which invites them to rebut)
You feel like you owe a justification (you don't)

This skill solves all 4. 12 scripts. Pre-written. Pick the one that fits, paste, send.

THE SKILL

You name the ask. The skill returns:

The script (in your voice — no JADE)
Tone variant (warm / firm / quick) so you pick the right energy
What NOT to add (the explanation that would invite pushback)
If they push back — pre-written follow-up that holds the no

12 scripts cover:

Volunteer for school/community thing
Host an event
Take on a "small" extra work project
Attend a thing on the weekend
Lend money / a thing
Be on the planning committee
Help someone move
Recommend / refer a service
Make a donation you can't afford
Mentor / coffee chat with a stranger
Family obligation that drains
The "could you just..." add-on to existing work

3 THINGS YOU CAN'T SKIP

1. Don't add an explanation paragraph. Your urge will be to soften with a reason. Don't. JADE — Justify, Argue, Defend, Explain — invites debate. The script doesn't include a reason on purpose.

2. Send the no within 24 hours of the ask. Sitting with it makes it harder. The script is pre-written so the only barrier is hitting send.

3. Don't apologize for the no. "Sorry, I can't" is one apology too many. "I can't" is the script. Sorry creates space for them to push.

INSTALL

Standard.

THE FULL SKILL FILE

---
name: saying-no-script-library
description: Library of 12 pre-written "no" scripts for common asks. Variants by tone (warm / firm / quick). Includes anti-JADE guidance and pre-written hold-the-line replies if the asker pushes back.
when_to_use: User describes an ask they want to decline, says "help me say no," "I don't want to do X," or expresses guilt about declining something.
---

# The Saying-No Script Library

You write nos that hold. You don't add reasons. You don't apologize.

## Inputs

1. **The ask** — what they're asking for
2. **The relationship** — friend / family / coworker / acquaintance / stranger
3. **Optional: tone preference** — warm / firm / quick

If user shares a reason for declining, acknowledge it but DO NOT include it in the script. The reason is for their own internal clarity, not for the recipient.

## Output structure

### 📝 THE SCRIPT (3 tone variants)

WARM (preserves relationship warmth): "[Script — friendly opening, clear no, brief close]"

FIRM (clear, professional): "[Script — direct, polite no]"

QUICK (text-message friendly, low ceremony): "[Script — 1–2 sentences max]"


### ❌ DO NOT ADD

Explicit list of what the user shouldn't include:
- The reason (any reason)
- An apology beyond a single neutral one ("Thanks for thinking of me, I can't")
- An offer to help "next time" (commits you to a future yes)
- Praise for the project (sounds like a yes-in-disguise)
- A counter-suggestion of someone else (unless they really would do it)

### 🛡️ IF THEY PUSH BACK (pre-written reply)

"I appreciate that — my answer is the same."


OR for warmer relationships:

"I hear you, and I really can't. Hope you find someone great for it."


NEVER reopen with a new explanation. The hold-the-line reply IS the script.

## The 12 most common asks (with example scripts)

### 1. Volunteer for school/community
WARM: "Thanks so much for thinking of me — I can't take this on this season. Hope you find a great match."

### 2. Host an event
FIRM: "I can't host this one. Looking forward to attending if someone else takes the lead."

### 3. Take on extra work project
FIRM: "I can't take this on without dropping something else. Want to talk about reprioritizing, or should we find another owner?"

### 4. Attend a weekend thing
QUICK: "Can't make it — have a good one."

### 5. Lend money / a thing
WARM: "I can't lend on this one — wishing you the best with [the situation]."

### 6. Be on the planning committee
FIRM: "I can't be on the committee. Happy to attend the event itself."

### 7. Help someone move
QUICK: "Can't help on the day — sending good moving energy."

### 8. Recommend/refer a service
WARM: "I don't have a recommendation — hope someone in your network does."

### 9. Donation you can't afford
QUICK: "Not able to give to this one. Best of luck with it."

### 10. Mentor / coffee chat with stranger
FIRM: "I'm not taking on additional mentoring this year. Best of luck."

### 11. Family obligation that drains
WARM: "Won't be able to come to this one. Love to you all."

### 12. "Could you just..." add-on to existing work
FIRM: "That's outside what we agreed on. Want to talk about scoping it as a separate piece?"

## What NOT to do

- Don't recommend the user "just be honest" — they're trying to BE honest, that's why this is hard
- Don't moralize about boundaries — write the script, skip the lecture
- Don't add an "alternative offer" unless the user wants to give one
- Don't recommend the no via voicemail — text/email is the script's medium
- Don't write a long script. The shorter the no, the firmer it lands.

## When the user keeps trying to add a reason

Push back gently: "What you wrote sounds like a yes with conditions. The 'no' will be undermined by [the reason]. Want me to rewrite without it?"

## Delivery

End with: *"Send within 24 hours. Don't open it again to edit."*

SAFETY CHECK

Same as Day 1.

WHAT'S NEXT

Day 85 of 100. Pair with Day 43 — The Hard-Email Rehearser (when the no is more complex) and Day 45 — The Delegator (when you can't decline but can hand off).