Writing cold open
Generates the first sentence of a message or email when you can't get past the blank cursor. Offers 2-3 openings matched to the relationship and goal, then steps out — you write the rest. Use when user says "cold open", "help me start this message", "how do I begin", "stuck on opening", "first sentence", or invokes /writing-cold-open.From its SKILL.md
npx -y skills add risadams/skills --skill writing-cold-openAssembled 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.5 KB, 704 tokens by cl100k_base, as published. Nobody here has run it
Cold Open
The user knows what they need to say. They cannot type the first word. The blank cursor is winning. Your job is to produce just the opening sentence — not a draft, not a full message, not a plan — so they can get past the activation barrier and finish the rest themselves.
Sibling to task-initiation (which handles tasks) and writing-social-script (which writes the whole script). This one is narrower: just the opener.
Why usually no council
Cold-open is fast by design. For most cases, run inline — three openings, no debate.
For a high-stakes opener (cold outreach to a stranger, a sensitive message, a message you've drafted and deleted three times), invoke clarity-council via Skill in council-single-persona agent with persona_name=psychologist:
- user_problem: "Generate three opening sentences for this message. Each should match a different register (direct / warm / contextual). Predict how each will land for the recipient."
- context: the goal of the message + recipient + relationship + channel.
- desired_outcome: "Three openings, each labelled with register and a one-line landing prediction. Nothing else — they'll write the rest."
- constraints:
[just the opening sentence, no "I hope this email finds you well" template phrases, no preamble before the user's actual content] - depth:
brief.
When to activate
When the user says:
- "How do I start"
- "Stuck on the opening"
- "First sentence"
- "I've been staring at this message"
- "Cold open"
- "What do I even say first"
The questions
Ask in one AskUserQuestion call (skip if already answered):
- What's the message goal? (One sentence — the actual ask or update, not the framing.)
- Who's the recipient and what's the relationship?
- Channel? (Email vs Slack vs text — opening conventions differ a lot.)
Output format
Three openings
Direct — gets to the point in the first sentence:
[Opening sentence]
Warm — one beat of relational acknowledgment, then pivots:
[Opening sentence]
Contextual — names the trigger or shared context first:
[Opening sentence]
For each, in one line: who it works best for.
Pick one. Write the rest.
End with a literal nudge:
Pick one. Paste it in. Keep typing.
That's the whole output. Do not offer to write the rest. Do not write subject lines (unless the user asks). Do not offer revisions until the user comes back asking.
What NOT to do
- Do not write more than three openings — more options = more paralysis
- Do not write past the first sentence — that's not what this skill is for
- Do not use "I hope this email finds you well" or other template phrases
- Do not include a sign-off — the user only needs the opener
- Do not ask "are you sure?" after generating — they came here to be unstuck
- Do not editorialize about how the message should go — just produce the openers
What ships with it: 1 file
11.2 KB alongside SKILL.md
- README.md11.2 KB