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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncall-prepExecute the skills CLI command in your project's root directory to begin installation:
Fetches call-prep from anthropics/knowledge-work-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate call-prep. Access via /call-prep in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
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.
┌─────────────────────────────────────────────────────────────────┐
│ 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 │
└─────────────────────────────────────────────────────────────────┘
When you run this skill, I'll ask for what I need:
Required:
Helpful if you have it:
If you've connected your CRM, email, or other tools, I'll pull context automatically and skip the questions.
Connect your tools to supercharge this skill:
| Connector | What It Adds |
|---|---|
| CRM | Account details, contact history, open deals, recent activities |
| 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.
# 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
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
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
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
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend call-prep for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
call-prep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in call-prep — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: call-prep is focused, and the summary matches what you get after install.
We added call-prep from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
call-prep reduced setup friction for our internal harness; good balance of opinion and flexibility.
call-prep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for call-prep matched our evaluation — installs cleanly and behaves as described in the markdown.
call-prep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
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