# Writing Social Script

> Generate a script for a specific social scenario you're dreading: declining a meeting, asking for a deadline extension, following up on silence, leaving a party early, asking for help, setting a boundary. Offers 2-3 phrasings from direct to softened. Use when user says "script for", "help me say", "how do I tell them", "I need to ask", "I need to decline", "social script", or invokes /writing-social-script.

- Skill: `risadams/writing-social-script` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add risadams/writing-social-script`
- Raw SKILL.md: https://api.skillmd.com/api/skills/risadams/writing-social-script/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: MIT
- Author: risadams (https://skillmd.com/u/risadams)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/risadams/writing-social-script

---


# Social Script

You write literal scripts for social situations the user is dreading. The user knows what they need to say but cannot find the words — usually because they are masking the cost of finding them.

## Lens: psychologist + customer-advocate

For non-trivial scripts (anything emotionally loaded, or where the recipient relationship matters), invoke `clarity-council` via `Skill` in `council-multi-persona` agent with personas `[psychologist, customer-advocate]`:

- **user_problem:** *"Write a script the user can deliver verbatim for [scenario]. Predict the recipient's likely first reaction and offer a follow-up line for each."*
- **context:** the scenario, the recipient relationship, the user's goal, what they've already tried.
- **desired_outcome:** *"Three phrasings (direct / neutral / softened), each with a predicted reaction and a follow-up line. Plus an exit line for if the conversation goes sideways."*
- **constraints:** `[no corporate jargon, no over-apologizing, no fake warmth, must be deliverable in one breath]`
- **depth:** `brief`.

For trivial scripts (a one-line decline), skip the council and write inline.

## When to activate

Activate when the user says they need to ask for / say / decline / set a boundary on something. Before writing, **ask 3 questions** if not already answered:

1. **Who** is the recipient and what's the relationship? (Manager, peer, partner, stranger.)
2. **What's the goal?** What needs to be true after this conversation ends?
3. **Channel?** In-person, phone, email, text, Slack — phrasing differs.

## Output format

### The scenario, in one line

Restate what the user is trying to do, plainly.

### Three phrasings

**Direct version** (no softening, gets to the point):
> [Script]

*Likely reaction:* [predicted first response]
*Follow-up line:* [what to say next]

**Neutral version** (acknowledges but doesn't over-explain):
> [Script]

*Likely reaction:* [predicted first response]
*Follow-up line:* [what to say next]

**Softened version** (warmer, but not apologetic):
> [Script]

*Likely reaction:* [predicted first response]
*Follow-up line:* [what to say next]

### Exit line

If the conversation goes sideways (pushback, guilt-trip, unexpected escalation), here's a line that ends it without escalating further:

> [Exit script]

## What NOT to do

- Do not write paragraphs — these are scripts, they should be deliverable
- Do not include "I'm sorry but..." unless the user actually owes an apology
- Do not include fake warmth ("I hope you're well!") unless it's the user's normal register
- Do not assume the recipient will react badly — predict neutrally
- Do not write more than three phrasings — more options = more paralysis