meeting-synthesis
Use when extracting product signals from meeting transcripts - systematically identifies asks, problems, quotes, and evidence across time windows with customer attribution
npx skills add majiayu000/claude-skill-registry --skill meeting-synthesis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Meeting Synthesis ## Purpose Extract actionable product signals from meeting transcripts: - Feature requests and capability asks - Pain points and friction areas - Customer quotes and verbatim feedback - Evidence for epic creation and prioritization - Pattern detection across multiple customers ## When to Use This Skill Activate automatically when: - `product-planning` workflow gathers signals for epics - `cs-prep` workflow compiles customer context for QBRs - `strategy-session` workflow needs customer insights - User explicitly requests meeting synthesis - Any workflow requires customer evidence extraction ## Signal Types ### 1. Feature Requests ("Asks") Explicit requests for new capabilities or enhancements. **Indicators:** - "We need..." - "Can you build..." - "It would be great if..." - "Our team wants..." **Extract:** - What capability is requested? - Why is it needed? (business impact) - Who requested it? (customer, role) - When? (meeting date) ### 2. Pain Points ("Problems") Friction, blockers, or inefficiencies users experience. **Indicators:** - "It's frustrating that..." - "We struggle with..." - "The current process is..." - "Our team spends too much time..." **Extract
- Purpose
- When to Use This Skill
- Signal Types
- 1. Feature Requests ("Asks")
- 2. Pain Points ("Problems")
- 3. Onboarding Friction
- 4. Integration Gaps
- 5. Performance Needs
- Synthesis Process
- 1. Determine Time Window
- 2. Collect Meeting Files
- 3. Extract Signals from Each Meeting
- 4. Cluster Signals
- 5. Compute Signal Metrics
What does the meeting-synthesis skill do?
Use when extracting product signals from meeting transcripts - systematically identifies asks, problems, quotes, and evidence across time windows with customer attribution
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill meeting-synthesis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.