call-summary
Skill0 starsChanged 7 months agoMITView on GitHub
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- aditya-jaiswal/compound-ostheir own version, first seen Sep 20, 2026
- composio-community/support-skillstheir own version, first seen Apr 10, 2026
- KevinReactiv8/claude-skillsword for word, first seen Mar 30, 2026
Other versions5 projects use a version of this.
Word for word · 1
- KevinReactiv8/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 4
- anthropics/knowledge-work-plugins★ 35ksame name
- composio-community/support-skills★ 18same name
- aditya-jaiswal/compound-os★ 3same name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository91 other files it gives its agents.
- ab-testSkill
- adsSkill
- analyzeSkill
- brand-contextSkill
- brand-memorySkill
- brand-storySkill
- briefSkill
- campaignSkill
- communitySkill
- competeSkill
- contentSkill
- docxSkill
- pdfSkill
- pptxSkill
- scheduleSkill
- setup-coworkSkill
- skill-creatorSkill
- xlsxSkill
- cowork-plugin-customizerSkill
- create-cowork-pluginSkill
- croSkill
- emailSkill
- funnelSkill
- gtm-engineSkill
- gtmSkill
- hookSkill
- landingSkill
- brand-voiceSkill
- campaign-planningSkill
- competitive-analysisSkill
- content-creationSkill
- performance-analyticsSkill
- ab-test-setupSkill
- ad-creativeSkill
- ai-seoSkill
- analytics-trackingSkill
- churn-preventionSkill
- cold-emailSkill
- competitor-alternativesSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- email-sequenceSkill
- form-croSkill
- free-tool-strategySkill
- launch-strategySkill
- marketing-ideasSkill
- marketing-psychologySkill
- onboarding-croSkill
- page-croSkill
- paid-adsSkill
- paywall-upgrade-croSkill
- popup-croSkill
- pricing-strategySkill
- product-marketing-contextSkill
- programmatic-seoSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- schema-markupSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
If a file is referenced: @$1
- Distinctive: line 55
If you have a full transcript from your video conferencing tool (e.g.
- Distinctive: line 121
When drafting customer-facing emails:
- Distinctive: line 154
Create tasks for action items
- Distinctive: line 155
Update next steps field
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/call-summary
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Process call notes or a transcript to extract action items, draft follow-up communications, and update records.
Usage
/call-summary <notes or transcript>Process these call notes: $ARGUMENTS
If a file is referenced: @$1
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CALL SUMMARY │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ Paste call notes or transcript │
│ ✓ Extract key discussion points and decisions │
│ ✓ Identify action items with owners and due dates │
│ ✓ Surface objections, concerns, and open questions │
│ ✓ Draft customer-facing follow-up email │
│ ✓ Generate internal summary for your team │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │
│ + CRM: Update opportunity, log activity, create tasks │
│ + Email: Send follow-up directly from draft │
│ + Calendar: Link to meeting, pull attendee context │
└─────────────────────────────────────────────────────────────────┘What I Need From You
Option 1: Paste your notes Just paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it.
Option 2: Paste a transcript If you have a full transcript from your video conferencing tool (e.g. Zoom, Teams) or conversation intelligence tool (e.g. Gong, Fireflies), paste it. I'll extract the key moments.
Option 3: Describe the call Tell me what happened: "Had a discovery call with Acme Corp. Met with their VP Eng and CTO. They're evaluating us vs Competitor X. Main concern is integration timeline."
Output
Internal Summary
## Call Summary: [Company] — [Date]
**Attendees:** [Names and titles]
**Call Type:** [Discovery / Demo / Negotiation / Check-in]
**Duration:** [If known]
### Key Discussion Points
1. [Topic] — [What was discussed, decisions made]
2. [Topic] — [Summary]
### Customer Priorities
- [Priority 1 they expressed]
- [Priority 2]
### Objections / Concerns Raised
- [Concern] — [How you addressed it / status]
### Competitive Intel
- [Any competitor mentions, what was said]
### Action Items
| Owner | Action | Due |
|-------|--------|-----|
| [You] | [Task] | [Date] |
| [Customer] | [Task] | [Date] |
### Next Steps
- [Agreed next step with timeline]
### Deal Impact
- [How this call affects the opportunity — stage change, risk, acceleration]Customer Follow-Up Email
Subject: [Meeting recap + next steps]
Hi [Name],
Thank you for taking the time to meet today...
[Key points discussed]
[Commitments you made]
[Clear next step with timeline]
Best,
[You]Email Style Guidelines
When drafting customer-facing emails:
- Be concise but informative — Get to the point quickly. Customers are busy.
- No markdown formatting — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client.
- Use simple structure — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it.
- Keep it scannable — If listing items, use plain dashes or numbers, not fancy formatting.
Good:
Here's what we discussed:
- Quote for 20 seats at $480/seat/year
- W9 and supplier onboarding docs
- Point of contact for the contractBad:
**What You Need from Us:**
- Quote for 20 seats at $480/seat/yearIf Connectors Available
Transcripts connected (e.g. Gong, Fireflies):
- I'll search for the call automatically
- Pull the full transcript
- Extract key moments flagged by the platform
CRM connected:
- I'll offer to update the opportunity stage
- Log the call as an activity
- Create tasks for action items
- Update next steps field
Email connected:
- I'll offer to create a draft in ~~email
- Or send directly if you approve
Tips
- More detail = better output — Even rough notes help. "They seemed concerned about X" is useful context.
- Name the attendees — Helps me structure the summary and assign action items.
- Flag what matters — If something was important, tell me: "The big thing was..."
- Tell me the deal stage — Helps me tailor the follow-up tone and next steps.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

