More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Meeting Recap Email: Follow-Up Draft From Your Transcript

    1

    Skip writing the follow-up. Ask once and the recap, with real dates, is waiting in your Gmail or Outlook drafts.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Meeting Recap Email: Follow-Up Draft From Your Transcript

    Meeting Recap Email: Follow-Up Draft From Your Transcript

    Example session with this skill installed

    Get the transcript from my 1:1 with Devon this morning and draft the follow-up email.

    • Read your context and instructions
    • Compiled the meeting recap email

    The recap is in your Gmail drafts as "Recap: Weekly 1:1 (10/13)", and nothing was sent. The To line is empty because I couldn't find an address for Devon in your mail. Add it before you send.

    Check before sending:

    "Next Wednesday". Devon said it on a Tuesday, so I read it as Oct 21. If they meant tomorrow (Oct 14), change the date.

    Thanksgiving. Devon said "the 24th through the 26th" without a month. I wrote Nov 24 to 26, which fits Thanksgiving on Nov 26.

    Henderson figure. Devon wasn't sure if it was "forty-eight or fifty-eight". I left the number out and wrote only that it came back lower than last year and they want to drop weekend coverage.

    Support team complaint. I left out Devon's remarks about the support team and Raj (tickets sitting for a week, "nobody reads anything"). It's criticism of people who weren't there and lands harder in writing. I kept a neutral to-do for you, "Think about how to raise the Henderson support issue". Say if you'd rather add the detail or drop that line.

    No-meeting Friday. I left it out. It was only floated, and you answered "maybe, something to think about".

    Sam's compliment. It's under your to-dos, since you said you'd pass it on.

    Suggestion, not in the email. Devon could forward you the Henderson email, so you'd have the real number when you talk to Priya.

    I saved your name, the sign-off and Gmail drafts as the default in ~/.meeting-recap/settings.md. I also noted Devon in the people list.

    Anything you'd change? I'll remember it for next time.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem. After a meeting, the follow-up email takes longer than it should. You scroll an hour of transcript, work out who owes what, turn "next Wednesday" into a real date, and decide what should not go in writing. Ask this skill instead and the recap is waiting in your drafts: the main point first, every deadline as a real date, both sides' to-dos, and a short list of what to check before you send.

    What it does. Say "Get the transcript from my 1:1 with Devon this morning and draft the follow-up email." With your meeting tool connected (Google Drive for Google Meet transcripts, Read AI, Plaud, Otter, Fathom, Fireflies, Zoom or Teams), it finds the transcript and tells you which one it used. With Gmail or Outlook connected, the email lands in your drafts as "Recap: Weekly 1:1 (10/13)". No connectors? Paste the transcript or point it at a file, and you get an .eml file your mail app opens, or copy-ready text.

    Every recap:

    • Leads with the one idea worth remembering, in the words used in the meeting, so it survives the week.
    • Turns deadlines into dates, like "Wednesday (Oct 21)", and flags the ones it had to guess, so nobody argues later about which Wednesday.
    • Lists your to-dos and theirs, so the email reads as an agreement, not a list of demands.
    • Leaves out small talk and asks nobody made, so you are not walking back something you never asked for.
    • Ends with a check-before-sending list of remarks it left out (a jab at a coworker, internal pricing on a client call), numbers it would not guess and dates it resolved, so you can add anything back before you send.
    • Remembers your settings and the people you meet with, so after one correction the next recap follows the new rule.

    It is built to stop at a draft: you read it, fix a line if needed, and hit send yourself. It handles 1:1s, team meetings and client calls, each with its own template.

    Why this beats prompting it yourself.

    Asking an AI without the skill:

    • "Next Wednesday" stays "next Wednesday".
    • The main point lands at the bottom, after the to-dos.
    • The email sits in the chat for you to copy, and nothing is remembered.

    With the skill:

    • "Wednesday (Oct 21)", flagged when it had to pick.
    • The main point opens the email, in the same structure every time.
    • The draft waits in Gmail or Outlook, and your corrections stick.

    Customize it in plain words: "sign it Mike", "always give me a file", "put takeaways first". It tells you each rule it saves. Say "show my recap settings" to see what it remembers, or "forget that" to undo a rule.

    Limits. Fetching the transcript needs your meeting tool connected, and inbox drafts need a Gmail, Outlook or Microsoft 365 connector. Settings and learning persist only in agents that can save files. A garbled transcript gives a careful recap, not a perfect one: unclear names and numbers are flagged, not fixed.

    $5. Pays for itself the first time it turns a vague "next Wednesday" into a date, or keeps a remark out of an email you would have regretted sending.

    • It is built to stop at a draft or file, and you send it yourself. That is an instruction to your agent, not a technical lock on your email connector.
    • Email drafts need an email connector in your agent. Without one, it writes an .eml file: Outlook for Windows opens it ready to send; in Apple Mail use Message, Send Again.
    • Settings and learning persist only in agents that can save files. In web chats you paste a short settings block into your project instructions to keep them.
    • Recap quality depends on the transcript. Garbled names and numbers are flagged, not fixed.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Gmail
    Outlook

    Permissions

    Read Files
    Write Files

    Allowed Hosts

    gmail.googleapis.com
    graph.microsoft.com

    File Scopes

    ~/.meeting-recap/**
    ~/Documents/Meeting
    Recaps/**

    No scripts, no installs, no network calls of its own, no credentials or environment reads. Gmail and Outlook are optional: it uses an email connector you already connected only to look up recipient addresses and create drafts, and its instructions forbid send tools. It reads the transcript you point it at, writes its settings and approved rules to ~/.meeting-recap/, and writes recap files to ~/Documents/Meeting Recaps or the folder you choose. It saves names, roles and addresses of people you meet with, never transcript text.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    It is plain SKILL.md instructions with no scripts, so any agent that loads skills can use it. The demo ran in Claude Code. Drafting into your inbox needs an email connector in that agent.

    It is built not to. Its instructions forbid send tools, even if you say "send it", so it stops at a draft or a file and you send from your mail app.

    Just ask for it. With a meeting tool connected (Google Drive for Google Meet transcripts, Read AI, Plaud, Otter, Fathom, Fireflies, Zoom or Teams), it searches for the meeting you named, newest first, and tells you which one it used. You can also paste the transcript or point it at a text file (.txt, .md, .vtt, .srt).

    Your settings, rules you approved, and the names, roles and email addresses of people you meet with. Never meeting content. Say "show my recap settings" to see it all, "forget that" to remove a rule, or "reset recap settings" to start over.

    Yes. External meetings use their own template: your next steps first, and anything internal, like a pricing floor mentioned before the client joined, stays out and is flagged to you.

    New in Productivity