call-summary

작성자: anthropic

통화 기록이나 대화록을 처리하여 — 실행 항목을 추출하고, 후속 이메일을 작성하며, 내부 요약을 생성합니다. 대략적인 메모나 대화록을 붙여넣은 후에 사용하세요.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill call-summary

/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:

  1. Be concise but informative — Get to the point quickly. Customers are busy.
  2. No markdown formatting — Don't use asterisks, bold, or other markdown syntax. Write in plain text that looks natural in any email client.
  3. Use simple structure — Short paragraphs, line breaks between sections. No headers or bullet formatting unless the customer's email client will render it.
  4. 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 contract

Bad:

**What You Need from Us:**
- Quote for 20 seats at $480/seat/year

If 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

  1. More detail = better output — Even rough notes help. "They seemed concerned about X" is useful context.
  2. Name the attendees — Helps me structure the summary and assign action items.
  3. Flag what matters — If something was important, tell me: "The big thing was..."
  4. Tell me the deal stage — Helps me tailor the follow-up tone and next steps.

anthropic의 다른 스킬

access
anthropic
Discord 채널 접근을 관리합니다 — 페어링 승인, 허용 목록 편집, DM/그룹 정책 설정. 사용자가 페어링 요청, 승인, 허용된 사람 확인 등을 요청할 때 사용합니다.
official
session-report
anthropic
~/.claude/projects 트랜스크립트에서 Claude Code 세션 사용량(토큰, 캐시, 하위 에이전트, 스킬, 고비용 프롬프트)에 대한 탐색 가능한 HTML 보고서를 생성합니다.
official
build-mcp-server
anthropic
이 스킬은 사용자가 "MCP 서버 구축", "MCP 생성", "MCP 통합 만들기", "Claude용 API 래핑", "도구 노출" 등을 요청할 때 사용해야 합니다.
official
cookbook-audit
anthropic
Anthropic Cookbook 노트북을 루브릭에 따라 감사합니다. 노트북 리뷰나 감사가 요청될 때마다 사용하세요.
official
handle-complaint
anthropic
들어오는 고객 불만을 처음부터 끝까지 처리합니다 — 맥락을 파악하고, 응답을 작성하며, 운영상의 수정을 제안합니다. 선택적으로 이메일이나 티켓 ID를 받습니다…
official
use-case-triage
anthropic
처리 활동이 PIA, 필수 GDPR DPIA가 필요한지 또는 진행 가능한지 신속히 판단하여 개인정보 처리방침 충돌을 표시하고 적절한 경로로 안내합니다…
official
board-minutes
anthropic
이사회 또는 위원회 회의록을 사내 형식으로 작성합니다. 캘린더에서 예정된 이사회 및 위원회 회의를 자동으로 감지하고, 안건을 요청한 후…
official
renewal-tracker
anthropic
유지 관리되는 갱신 등록부를 기반으로 취소 마감일이 다가오는 계약을 표시하고 통지 기간이 종료되기 전에 경고합니다. 사용자가 요청할 때 사용합니다.
official