call-prep

anthropics/knowledge-work-plugins · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

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

Get fully prepared for any sales call in minutes. This skill works with whatever context you provide, and gets significantly better when you connect your sales tools.

skill.md

Call Prep

Get fully prepared for any sales call in minutes. This skill works with whatever context you provide, and gets significantly better when you connect your sales tools.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                        CALL PREP                                 │
├─────────────────────────────────────────────────────────────────┤
│  ALWAYS (works standalone)                                       │
│  ✓ You tell me: company, meeting type, attendees                │
│  ✓ Web search: recent news, funding, leadership changes         │
│  ✓ Company research: what they do, size, industry               │
│  ✓ Output: prep brief with agenda and questions                 │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + CRM: account history, contacts, opportunities, activities    │
│  + Email: recent threads, open questions, commitments           │
│  + Chat: internal discussions, colleague insights               │
│  + Transcripts: prior call recordings, key moments              │
│  + Calendar: auto-find meeting, pull attendees                  │
└─────────────────────────────────────────────────────────────────┘

Getting Started

When you run this skill, I'll ask for what I need:

Required:

  • Company or contact name
  • Meeting type (discovery, demo, negotiation, check-in, etc.)

Helpful if you have it:

  • Who's attending (names and titles)
  • Any context you want me to know (paste prior notes, emails, etc.)

If you've connected your CRM, email, or other tools, I'll pull context automatically and skip the questions.


Connectors (Optional)

Connect your tools to supercharge this skill:

Connector What It Adds
CRM Account details, contact history, open deals, recent activities
Email Recent threads with the company, open questions, attachments shared
Chat Internal chat discussions (e.g. Slack) about the account, colleague insights
Transcripts Prior call recordings, topics covered, competitor mentions
Calendar Auto-find the meeting, pull attendees and description

No connectors? No problem. Just tell me about the meeting and paste any context you have. I'll research the rest.


Output Format

# Call Prep: [Company Name]

**Meeting:** [Type] — [Date/Time if known]
**Attendees:** [Names with titles]
**Your Goal:** [What you want to accomplish]

---

## Account Snapshot

| Field | Value |
|-------|-------|
| **Company** | [Name] |
| **Industry** | [Industry] |
| **Size** | [Employees / Revenue if known] |
| **Status** | [New prospect / Active opportunity / Customer] |
| **Last Touch** | [Date and summary] |

---

## Who You're Meeting

### [Name] — [Title]
- **Background:** [Career history, education if found]
- **LinkedIn:** [URL]
- **Role in Deal:** [Decision maker / Champion / Evaluator / etc.]
- **Last Interaction:** [Summary if known]
- **Talking Point:** [Something personal/professional to reference]

[Repeat for each attendee]

---

## Context & History

**What's happened so far:**
- [Key point from prior interactions]
- [Open commitments or action items]
- [Any concerns or objections raised]

**Recent news about [Company]:**
- [News item 1 — why it matters]
- [News item 2 — why it matters]

---

## Suggested Agenda

1. **Open** — [Reference last conversation or trigger event]
2. **[Topic 1]** — [Discovery question or value discussion]
3. **[Topic 2]** — [Address known concern or explore priority]
4. **[Topic 3]** — [Demo section / Proposal review / etc.]
5. **Next Steps** — [Propose clear follow-up with timeline]

---

## Discovery Questions

Ask these to fill gaps in your understanding:

1. [Question about their current situation]
2. [Question about pain points or priorities]
3. [Question about decision process and timeline]
4. [Question about success criteria]
5. [Question about other stakeholders]

---

## Potential Objections

| Objection | Suggested Response |
|-----------|-------------------|
| [Likely objection based on context] | [How to address it] |
| [Common objection for this stage] | [How to address it] |

---

## Internal Notes

[Any internal chat context (e.g. Slack), colleague insights, or competitive intel]

---

## After the Call

Run **call-follow-up** to:
- Extract action items
- Update your CRM
- Draft follow-up email

Execution Flow

Step 1: Gather Context

If connectors available:

1. Calendar → Find upcoming meeting matching company name
   - Pull: title, time, attendees, description, attachments

2. CRM → Query account
   - Pull: account details, all contacts, open opportunities
   - Pull: last 10 activities, any account notes

3. Email → Search recent threads
   - Query: emails with company domain (last 30 days)
   - Extract: key topics, open questions, commitments

4. Chat → Search internal discussions
   - Query: company name mentions (last 30 days)
   - Extract: colleague insights, competitive intel

5. Transcripts → Find prior calls
   - Pull: call recordings with this account
   - Extract: key moments, objections raised, topics covered

If no connectors:

1. Ask user:
   - "What company are you meeting with?"
   - "What type of meeting is this?"
   - "Who's attending? (names and titles if you know)"
   - "Any context you want me to know? (paste notes, emails, etc.)"

2. Accept whatever they provide and work with it

Step 2: Research Supplement

Always run (web search):

1. "[Company] news" — last 30 days
2. "[Company] funding" — recent announcements
3. "[Company] leadership" — executive changes
4. "[Company] + [industry] trends" — relevant context
5. Attendee LinkedIn profiles — background research

Step 3: Synthesize & Generate

1. Combine all sources into unified context
2. Identify gaps in understanding → generate discovery questions
3. Anticipate objections based on stage and history
4. Create suggested agenda tailored to meeting type
5. Output formatted prep brief

Meeting Type Variations

Discovery Call

  • Focus on: Understanding their world, pain points, priorities
  • Agenda emphasis: Questions > Talking
  • Key output: Qualification signals, next step proposal

Demo / Presentation

  • Focus on: Their specific use case, tailored examples
  • Agenda emphasis: Show relevant features, get feedback
  • Key output: Technical requirements, decision timeline

Negotiation / Proposal Review

  • Focus on: Addressing concerns, justifying value
  • Agenda emphasis: Handle objections, close gaps
  • Key output: Path to agreement, clear next steps

Check-in / QBR

  • Focus on: Value delivered, expansion opportunities
  • Agenda emphasis: Review wins, surface new needs
  • Key output: Renewal confidence, upsell pipeline

Tips for Better Prep

  1. More context = better prep — Paste emails, notes, anything you have
  2. Name the attendees — Even just titles help me research
  3. State your goal — "I want to get them to agree to a pilot"
  4. Flag concerns — "They mentioned budget is tight"

Related Skills

  • account-research — Deep dive on a company before first contact
  • call-follow-up — Process call notes and execute post-call workflow
  • draft-outreach — Write personalized outreach after research
how to use call-prep

How to use call-prep on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add call-prep
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

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

The skills CLI fetches call-prep from GitHub repository anthropics/knowledge-work-plugins and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/call-prep

Reload or restart Cursor to activate call-prep. Access the skill through slash commands (e.g., /call-prep) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.650 reviews
  • Carlos Flores· Dec 28, 2024

    I recommend call-prep for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Omar Menon· Dec 20, 2024

    call-prep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ganesh Mohane· Dec 16, 2024

    Useful defaults in call-prep — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Nia Ramirez· Dec 8, 2024

    Solid pick for teams standardizing on skills: call-prep is focused, and the summary matches what you get after install.

  • Ama Haddad· Nov 27, 2024

    We added call-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ira Haddad· Nov 11, 2024

    call-prep reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Garcia· Oct 18, 2024

    call-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hana Chawla· Oct 2, 2024

    Registry listing for call-prep matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Piyush G· Sep 21, 2024

    call-prep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ama Thompson· Sep 21, 2024

    Solid pick for teams standardizing on skills: call-prep is focused, and the summary matches what you get after install.

showing 1-10 of 50

1 / 5