Get up and running with Knowledge Work Plugins in under 5 minutes. This guide walks you through installing the sales plugin and using it to prep for a sales call.
This quickstart uses the sales plugin as an example, but the same process works for any plugin in the marketplace.
Skills activate automatically when Claude detects relevant intent. Let’s try the call-prep skill from the sales plugin.Start a conversation with Claude:
Prep me for my call with Acme Corp tomorrow
Claude will ask you a few questions:
What type of meeting is this? (discovery, demo, negotiation, etc.)
Who’s attending? (names and titles if you know)
Any context you want to share? (paste notes, emails, etc.)
Provide whatever information you have. Claude will:
Research the company using web search
Look up attendees on LinkedIn if you provide names
Generate a comprehensive call prep brief
Example call prep output
# Call Prep: Acme Corp**Meeting:** Discovery Call — Tomorrow**Attendees:** Sarah Chen (VP Engineering), Michael Park (CTO)**Your Goal:** Understand their current workflow and pain points---## Account Snapshot| Field | Value ||-------|-------|| **Company** | Acme Corp || **Industry** | SaaS - Developer Tools || **Size** | 150 employees, Series B || **Status** | New prospect |---## Who You're Meeting### Sarah Chen — VP Engineering- **Background:** Previously led platform at TechCo, Stanford CS- **LinkedIn:** linkedin.com/in/sarahchen- **Role in Deal:** Technical decision maker- **Talking Point:** Recently posted about scaling challenges### Michael Park — CTO- **Background:** Former architect at BigCorp, MIT- **LinkedIn:** linkedin.com/in/michaelpark- **Role in Deal:** Final approver- **Talking Point:** Speaking at DevConf next month on infrastructure---## Recent News- **Series B funding ($25M)** — Announced 2 months ago, focused on product expansion- **Hiring push** — 10 engineering roles posted, suggests scaling challenges---## Suggested Agenda1. **Open** — Reference their recent funding and growth2. **Current State** — How they handle deployments today3. **Pain Points** — What breaks as they scale4. **Vision** — Where they want to be in 6 months5. **Next Steps** — Propose technical deep dive---## Discovery Questions1. What does your deployment process look like today?2. What breaks first when you try to scale?3. How much engineering time goes to infrastructure vs features?4. What's your timeline for solving this?5. Who else should be involved in evaluating solutions?
Commands are explicit workflows you invoke with slash syntax. Let’s try the /call-summary command.After your call with Acme Corp, paste your notes:
/call-summaryMet with Sarah Chen (VP Eng) and Michael Park (CTO) at Acme Corp.They're using Jenkins for CI/CD but it's becoming a bottleneck.Deploys take 2+ hours. Breaking regularly as team grows.Sarah seemed very interested in our multi-region capabilities.Michael asked about SOC 2 compliance timeline.Next steps:- Send them our security questionnaire- Schedule technical deep dive for next week- Sarah will introduce us to their DevOps lead
Claude will process your notes and generate:
Example call summary output
## Call Summary: Acme Corp — Feb 28, 2026**Attendees:** Sarah Chen (VP Engineering), Michael Park (CTO)**Call Type:** Discovery### Key Discussion Points1. **Current CI/CD Setup** — Using Jenkins, experiencing bottlenecks - Deploys taking 2+ hours - Reliability issues as team scales2. **Technical Interests** — Multi-region deployment capabilities3. **Compliance** — SOC 2 timeline is a decision factor### Customer Priorities- Reduce deployment time and improve reliability- Multi-region support for global customers- SOC 2 compliance for enterprise deals### Action Items| Owner | Action | Due ||-------|--------|-----|| You | Send security questionnaire | This week || You | Schedule technical deep dive | Next week || Sarah | Introduce DevOps lead | Next week |### Next Steps- Technical deep dive scheduled for next week- Will meet DevOps lead to discuss current architecture---## Follow-Up EmailSubject: Great meeting today + next stepsHi Sarah and Michael,Thank you for taking the time to meet today. It was great to learn about how you're scaling your deployment infrastructure and the challenges you're facing with Jenkins.Based on our conversation, I'm sending over:1. Our security questionnaire (SOC 2 timeline and compliance details)2. A case study from a similar company that reduced deploy time from 2 hours to 12 minutes3. Multi-region architecture overviewI'll also get that technical deep dive on the calendar for next week. Looking forward to meeting your DevOps lead and diving deeper into your current setup.Let me know if you have any questions in the meantime.Best,[Your name]