acct-meeting-recap-email SKILL.md skillA
acct-meeting-recap-email from polar-bear-org/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add polar-bear-org/claude-skills/acct-meeting-recap-email@git:20261011.dce569cPins git:20261011.dce569c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- polar-bear-org/claude-skills
- Path
packs/account-executives-pack/skills/acct-meeting-recap-email/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261011.dce569c, committed Oct 11, 2026
- Size
- 4,417 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Drafts the meeting recap email to the customer, with what you understood of their situation, what each side committed to with dates, one next step and one check question, internal notes kept out. Use for "run acct-meeting-recap-email", "recap email", "meeting recap email", "follow-up email after a meeting", "summary email to the customer", "confirm what we agreed in writing", "email after a sales call", part of the Claude for Account Executives Pack by Polar Bear.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Meeting Recap Email ## When To Use The customer no longer remembers what was agreed when you follow up. Run this after a meeting, the same day. It answers: how do you confirm in a few lines what each side committed to do? ## When Not To Use The internal write-up, with your weak signals and assumptions, is Sales Call Notes: this email goes to the customer. After a proposal has been sent, run Proposal Follow-Up. ## Inputs - Your call notes from the meeting. - The recipients on the customer side, by name and job role, and who to copy. - An email you already wrote to this customer, if you have one, so the draft keeps your tone. If you have none of this, I start from the commitments and the next step as you dictate them, and mark the output as a first draft. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/acct-meeting-recap-email@sha256:cbe7cc9f8c4f939eThe line at the top of this page pins the label git:20261011.dce569c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cggj5zkkk63es7pc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 11, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4417 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
polar-bear-org/claude-skills · 51 stars · license a license file GitHub does not identify · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cggj5zkkk63es7pc GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/acct-meeting-recap-email GET https://markdownregistry.com/api/v1/blob/cbe7cc9f8c4f939eaf6b55e6bc5ff9a107dbeaed0e0ee6f5b16b931d1047c9cd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.