SuperAPI AI Directory

should-i-send-this

General & other

View repository

Updated 10-16 01:18

About this skill

Should I Send This

Sent is forever. The angry reply, the 2am overshare, the passive-aggressive "per my last email" — they feel right in the moment and wrong an hour later. This is the pause between writing and sending: it reads how your message will actually land for the person receiving it, flags what's emotion-driven or misreadable, checks whether now is even the right time to send, and offers a calmer version — so you send the message you'd stand behind tomorrow.

What This Skill Produces

  • The recipient's-eye read — how the message will likely land for them, not how it feels to you
  • The risk flags — the parts that could be misread, the emotion leaking through, the thing you'll regret, the overshare
  • The timing check — whether to send now, wait, or not send at all (some messages are better not sent)
  • A calmer rewrite — if it needs one, a version that gets your point across without the damage
  • The verdict — send as-is / send the rewrite / wait / don't send

Required Inputs

Ask for these if not provided:

  • The message — what you're about to send (paste it)
  • The recipient & relationship — who's getting it and your dynamic
  • Your state — calm, angry, hurt, anxious (be honest — it changes everything)
  • What you want to achieve — the actual goal of the message

Framework: Read It As Them, Then Decide

  1. Read it from the recipient's side. How will they receive it — the tone they'll hear, not the one you mean? This is where regret hides.
  2. Spot the emotion leak. Flag what's being sent from anger, hurt, or anxiety — those parts are usually the regrettable ones.
  3. Find the misreads and overshares. The lines that could be taken wrong, and anything you're sharing that you can't unshare.
  4. Check the timing. Sometimes the message is fine but now isn't — hot moments especially warrant a wait. And some messages are better never sent.
  5. Offer the calm version and a verdict. If it needs softening, rewrite it to keep the point and lose the damage — then a clear send / rewrite / wait / don't-send call.

Output Format

The message: [what you want to send] · to [recipient] · you feel [state]

How it'll land for them: [recipient's-eye read]. Risk flags: [emotion leaking / misreadable lines / regret / overshare]. Timing: [send now / wait — you're hot / this may be better unsent]. Calmer version (if needed):

[rewrite that keeps the point, loses the damage] Verdict: [send as-is / send the rewrite / wait an hour / don't send].

Quality Checks

  • Reads the message from the recipient's perspective
  • Flags the emotion-driven and regrettable parts
  • Catches misreadable lines and overshares
  • Checks whether now is the right time (or whether to send at all)
  • Offers a calmer rewrite when warranted
  • Gives a clear verdict

Anti-Patterns

  • Judging by how it feels to send rather than to receive.
  • Rubber-stamping a clearly hot message.
  • Rewriting away the point along with the heat.
  • Ignoring timing — sometimes the fix is just "wait."
  • Never flagging "don't send" when that's the answer.

Example Trigger Phrases

  • "Should I send this angry reply to my boss? Check it first."
  • "Is this text okay to send, or will I regret it?"
  • "Read this before I hit send on it."
  • "I'm hurt and about to send this — should I?"
  • "Gut-check this message for me."