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.From its SKILL.md
npx -y skills add risadams/skills --skill writing-social-scriptAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.3 KB, 635 tokens by cl100k_base, as published. Nobody here has run it
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:
- Who is the recipient and what's the relationship? (Manager, peer, partner, stranger.)
- What's the goal? What needs to be true after this conversation ends?
- 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
What ships with it: 1 file
10.3 KB alongside SKILL.md
- README.md10.3 KB