How do I install the Message For The Moment skill?

Run npx skillmds@latest add gabrielmoreira/message-for-the-moment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Message For The Moment safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Message For The Moment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Message For The Moment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Message For The Moment?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Message For The Moment by gabrielmoreira

Name: Message For The Moment
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Message For The Moment

Write the short message you freeze on — a thank-you, condolence, congratulations, apology, or a graceful 'no' to an invite — warm, specific, and in your own voice. Use when asked to write a thank-you note, a sympathy/condolence message, a congratulations, a quick apology, or how to politely decline. Produces two or three ready-to-send options at the right length for the channel, plus the one line that carries the message, never generic filler.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Message for the Moment

Everyone freezes on these — the sympathy text, the thank-you that isn't a form letter, the "I can't make it" that doesn't sound cold. The block is never the words, it's the fear of getting the tone wrong. This writes a few options calibrated to the relationship and the moment, grounded in a real detail you give it, so it sounds like you actually meant it.

What This Skill Produces

2–3 send-ready options at different lengths/warmths for the channel (text, card, email)
The one line that carries it — the specific, personal sentence that makes it land
A note on what to avoid for this particular moment (e.g. don't say "everything happens for a reason" in condolences)

Required Inputs

Ask for these if not provided:

The moment — thank-you / condolence / congrats / apology / decline (or describe it)
Who it's to — relationship and how you'd normally talk (formal? close? work?)
The specific detail — what they did, who they lost, what you're sorry for — one real fact beats a paragraph of generic warmth
Channel & length — a text, a card, an email

Framework: What Makes It Land

Name the specific. "Thank you for driving three hours to be there" beats "thanks for everything."
Match warmth to the relationship — a card to a grandparent and a Slack to a coworker aren't the same register.
Say the hard thing simply. In grief and apology, plain and short beats eloquent and long.
No clichés that hurt. Avoid the stock lines that read as thoughtless for that moment.
End clean. No trailing "anyway…" — close on the feeling or the offer.

Output Format

[Moment] · to [relationship] · [channel]

Option A (short): … Option B (warmer): … Option C (if you want to add an offer/next step): …

The line that carries it: "…" Avoid here: [cliché or misstep specific to this moment]

Quality Checks

At least one option uses the specific detail provided (not generic warmth)
Tone matches the stated relationship and channel
For condolence/apology: plain and short, no clichés that minimise
For a decline: warm, clear, no over-explaining or false promises
Each option is actually send-ready — no brackets left to fill unless input was missing

Anti-Patterns

Generic warmth ("thinking of you at this difficult time") with no specific — the thing that makes it feel automated.
Over-explaining a no — a paragraph of excuses reads worse than a warm, brief decline.
Toxic-positivity in grief — "at least," "everything happens for a reason," "stay strong."
Fabricating a detail you weren't given — ask for it or keep it honestly general.

Example Trigger Phrases

"Help me write a condolence text to a coworker who lost their dad."
"Thank-you note for my aunt who hosted the whole family."
"How do I politely decline a wedding I can't attend?"
"Write a short apology to a friend I stood up."
"Congratulate my teammate on the promotion without sounding fake."

---name: message-for-the-momentdescription: Write the short message you freeze on — a thank-you, condolence, congratulations, apology, or a graceful 'no' to an invite — warm, specific, and in your own voice. Use when asked to write a thank-you note, a sympathy/condolence message, a congratulations, a quick apology, or how to politely decline. Produces two or three ready-to-send options at the right length for the channel, plus the one line that carries the message, never generic filler.--- # Message for the Moment Everyone freezes on these — the sympathy text, the thank-you that isn't a form letter, the "I can't make it" that doesn't sound cold. The block is never the words, it's the fear of getting the tone wrong. This writes a few options calibrated to the relationship and the moment, grounded in a real detail you give it, so it sounds like you actually meant it. ## What This Skill Produces - **2–3 send-ready options** at different lengths/warmths for the channel (text, card, email) - **The one line that carries it** — the specific, personal sentence that makes it land - **A note on what to avoid** for this particular moment (e.g. don't say "everything happens for a reason" in condolences) ## Required Inputs Ask for these if not provided: - **The moment** — thank-you / condolence / congrats / apology / decline (or describe it) - **Who it's to** — relationship and how you'd normally talk (formal? close? work?) - **The specific detail** — what they did, who they lost, what you're sorry for — one real fact beats a paragraph of generic warmth - **Channel & length** — a text, a card, an email ## Framework: What Makes It Land 1. **Name the specific.** "Thank you for driving three hours to be there" beats "thanks for everything." 2. **Match warmth to the relationship** — a card to a grandparent and a Slack to a coworker aren't the same register. 3. **Say the hard thing simply.** In grief and apology, plain and short beats eloquent and long. 4. **No clichés that hurt.** Avoid the stock lines that read as thoughtless for that moment. 5. **End clean.** No trailing "anyway…" — close on the feeling or the offer. ## Output Format ### [Moment] · to [relationship] · [channel] **Option A (short):** … **Option B (warmer):** … **Option C (if you want to add an offer/next step):** … **The line that carries it:** "…" **Avoid here:** [cliché or misstep specific to this moment] ## Quality Checks - [ ] At least one option uses the specific detail provided (not generic warmth) - [ ] Tone matches the stated relationship and channel - [ ] For condolence/apology: plain and short, no clichés that minimise - [ ] For a decline: warm, clear, no over-explaining or false promises - [ ] Each option is actually send-ready — no brackets left to fill unless input was missing ## Anti-Patterns - **Generic warmth** ("thinking of you at this difficult time") with no specific — the thing that makes it feel automated. - **Over-explaining a no** — a paragraph of excuses reads worse than a warm, brief decline. - **Toxic-positivity in grief** — "at least," "everything happens for a reason," "stay strong." - **Fabricating a detail** you weren't given — ask for it or keep it honestly general. ## Example Trigger Phrases - "Help me write a condolence text to a coworker who lost their dad." - "Thank-you note for my aunt who hosted the whole family." - "How do I politely decline a wedding I can't attend?" - "Write a short apology to a friend I stood up." - "Congratulate my teammate on the promotion without sounding fake."

Frequently asked questions