{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/call-summary",
  "version": "1.0.0",
  "name": "call-summary",
  "description": "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.",
  "system_prompt_fragment": "# /call-summary\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).\n\nProcess call notes or a transcript to extract action items, draft follow-up communications, and update records.\n\n## Usage\n\n```\n/call-summary <notes or transcript>\n```\n\nProcess these call notes: $ARGUMENTS\n\nIf a file is referenced: @$1\n\n---\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                      CALL SUMMARY                                │\n├─────────────────────────────────────────────────────────────────┤\n│  STANDALONE (always works)                                       │\n│  ✓ Paste call notes or transcript                               │\n│  ✓ Extract key discussion points and decisions                  │\n│  ✓ Identify action items with owners and due dates              │\n│  ✓ Surface objections, concerns, and open questions             │\n│  ✓ Draft customer-facing follow-up email                        │\n│  ✓ Generate internal summary for your team                      │\n├─────────────────────────────────────────────────────────────────┤\n│  SUPERCHARGED (when you connect your tools)                      │\n│  + Transcripts: Pull recording automatically (e.g. Gong, Fireflies) │\n│  + CRM: Update opportunity, log activity, create tasks          │\n│  + Email: Send follow-up directly from draft                    │\n│  + Calendar: Link to meeting, pull attendee context             │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n---\n\n## What I Need From You\n\n**Option 1: Paste your notes**\nJust paste whatever you have — bullet points, rough notes, stream of consciousness. I'll structure it.\n\n**Option 2: Paste a transcript**\nIf 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.\n\n**Option 3: Describe the call**\nTell 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.\"\n\n---\n\n## Output\n\n### Internal Summary\n```markdown\n## Call Summary: [Company] — [Date]\n\n**Attendees:** [Names and titles]\n**Call Type:** [Discovery / Demo / Negotiation / Check-in]\n**Duration:** [If known]\n\n### Key Discussion Points\n1. [Topic] — [What was discussed, decisions made]\n2. [Topic] — [Summary]\n\n### Customer Priorities\n- [Priority 1 they expressed]\n- [Priority 2]\n\n### Objections / Concerns Raised\n- [Concern] — [How you addressed it / status]\n\n### Competitive Intel\n- [Any competitor mentions, what was said]\n\n### Action Items\n| Owner | Action | Due |\n|-------|--------|-----|\n| [You] | [Task] | [Date] |\n| [Customer] | [Task] | [Date] |\n\n### Next Steps\n- [Agreed next step with timeline]\n\n### Deal Impact\n- [How this call affects the opportunity — stage change, risk, acceleration]\n```\n\n### Customer Follow-Up Email\n```\nSubject: [Meeting recap + next steps]\n\nHi [Name],\n\nThank you for taking the time to meet today...\n\n[Key points discussed]\n\n[Commitments you made]\n\n[Clear next step with timeline]\n\nBest,\n[You]\n```\n\n---\n\n## Email Style Guidelines\n\nWhen drafting customer-facing emails:\n\n1. **Be concise but informative** — Get to the point quickly. Customers are busy.\n2. **No markdown formatting** — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client.\n3. **Use simple structure** — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it.\n4. **Keep it scannable** — If listing items, use plain dashes or numbers, not fancy formatting.\n\n**Good:**\n```\nHere's what we discussed:\n- Quote for 20 seats at $480/seat/year\n- W9 and supplier onboarding docs\n- Point of contact for the contract\n```\n\n**Bad:**\n```\n**What You Need from Us:**\n- Quote for 20 seats at $480/seat/year\n```\n\n---\n\n## If Connectors Available\n\n**Transcripts connected (e.g. Gong, Fireflies):**\n- I'll search for the call automatically\n- Pull the full transcript\n- Extract key moments flagged by the platform\n\n**CRM connected:**\n- I'll offer to update the opportunity stage\n- Log the call as an activity\n- Create tasks for action items\n- Update next steps field\n\n**Email connected:**\n- I'll offer to create a draft in ~~email\n- Or send directly if you approve\n\n---\n\n## Tips\n\n1. **More detail = better output** — Even rough notes help. \"They seemed concerned about X\" is useful context.\n2. **Name the attendees** — Helps me structure the summary and assign action items.\n3. **Flag what matters** — If something was important, tell me: \"The big thing was...\"\n4. **Tell me the deal stage** — Helps me tailor the follow-up tone and next steps.",
  "applicable_domains": [
    "sales",
    "crm"
  ],
  "invocation": [
    "/call-summary",
    "/call-summary <call notes or transcript>"
  ],
  "tags": [
    "sales",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/sales/skills/call-summary/SKILL.md",
  "lifecycle": "stable",
  "category": "sales",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/sales/skills/call-summary/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}