If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncall-summaryExecute the skills CLI command in your project's root directory to begin installation:
Fetches call-summary 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-summary. Access via /call-summary 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
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.
/call-summary <notes or transcript>
Process these call notes: $ARGUMENTS
If a file is referenced: @$1
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β 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 β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
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."
## 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]
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]
When drafting customer-facing emails:
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
Transcripts connected (e.g. Gong, Fireflies):
CRM connected:
Email connected:
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
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
mattpocock/skills
Solid pick for teams standardizing on skills: call-summary is focused, and the summary matches what you get after install.
We added call-summary from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
call-summary fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
call-summary fits our agent workflows well β practical, well scoped, and easy to wire into existing repos.
I recommend call-summary for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: call-summary is focused, and the summary matches what you get after install.
Useful defaults in call-summary β fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
call-summary has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added call-summary from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for call-summary matched our evaluation β installs cleanly and behaves as described in the markdown.
showing 1-10 of 32