Draft replies, follow-ups, and new emails in Superhuman using the user's writing style. It reads the full conversation, updates an existing draft when present, and checks recipients and CCs, leaving the draft for the user to send.
Draft a reply, a follow-up, or a new email in Superhuman in the user's own voice — read the whole thread first, reuse an existing draft instead of adding a second one, keep the right people on the thread, and leave sending to the user unless they asked for it. Use when the user says reply to, answer, follow up with, draft an email to, or send, or when a triage turned up threads that need a response.
Run score Not tested
See how to installDrafts replies, follow-ups, and new emails in Superhuman to match the user's writing style and signature. It reads the full thread, including team comments, to understand who is waiting for an answer. If a draft already exists, it checks its contents and send status, then updates it instead of creating a duplicate. It also checks the recipients and CCs against the conversation. When the draft is ready, it reports the recipients, subject, and body, and leaves the message in Superhuman Drafts.
Use it to answer a long conversation, finish a message already in progress, or write a follow-up or new email in the user's usual style. Shared team snippets can provide a starting point when they fit the situation.
The Superhuman integration is required. Attachments other than images and audio are returned as download links, so PDFs and spreadsheets are treated as unread until the user opens them. A request to reply is treated as a request to draft; sending requires separate confirmation. If the user asks to send, an undo window is set, and the message can be recalled if they say to stop.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
A draft in Superhuman is the user's to send; the job is to make it the one they would have written. Read the whole thread, draft once, and stop at the draft.
get_thread with drafts and comments included. The last message is not the
whole ask: an earlier message often holds the question, a team comment may say
how to answer it, and the question itself may sit in an attachment.
get_attachment returns images and audio directly; for anything else it
returns a download link, so a PDF or a spreadsheet is unread until the user
opens it. When the thread is trimmed, raise message_limit. Note who is on the thread and who
spoke last; the reply goes to the person waiting, not to whoever wrote first.
list_drafts filtered by thread_id. If a draft exists, get_draft and read
it: the user may have started a reply in Superhuman, and the right move is to
finish theirs, not to add a second one. Check get_draft_send_status before
touching it. pending means it is already on its way, and a draft the user
sent from Superhuman minutes ago looks exactly like one that still needs work.
create_or_update_draft with type reply or reply_all and the thread id
for a thread, or type new with to for a fresh email, where subject can
be left for the writer and from picks one of the user's aliases. Give it
instructions (what to say, what to ask, what tone the thread calls for) and
let it write in the user's style and signature. Pass body only when the user
dictated exact wording, or when forwarding, where body holds the intro and
the forwarded message is appended for you.
reply_all when others on the thread need the answer; reply when the user
is answering one person. Keep the CCs the thread already had.subject on a reply; it inherits the thread's.list_snippets, get_snippet) hold wording the team already
agreed on for common replies; start from one when it fits.To revise, pass draft_id and thread_id back so the draft updates in place.
Recipient fields replace rather than merge, so pass the full list each time. An
update can rewrite the subject, so when it carries a prefix or a ticket tag
that must survive, discard the draft and recreate it instead.
Report the draft: to, cc, subject, the body, and that it is in the user's
Drafts in Superhuman. Sending is the user's action, so this skill does not
pre-approve send_draft and a send always asks first. When the user does ask
you to send, set an undo_timeout and report the undo token, and call
undo_send the moment they say stop. send_at schedules a send; smart_send
lets Superhuman pick the time.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.