菜单
MUST BE USED when generating meeting summaries after analysis and routing. Creates per-brain and overall summaries, updates CLAUDE.md files. Works with analyzing-meetings and routing-brains skills.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/samarv/Shanon --skill summarizing-meetings命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
MUST BE USED when analyzing meeting transcripts or notes. Classifies input type, attributes speakers, and verifies names against colleagues.json. Works with routing-brains and summarizing-meetings skills for complete workflow.
A framework for evaluating whether a product's success is mathematically possible based on its cost structure, acquisition assumptions, and unit economics. Use this when vetting a new job opportunity, evaluating a startup's viability, or determining if a failing product can be "iterated" to success.
A structured method for gathering high-signal, contextual feedback from a trusted network to validate ideas or navigate complex career decisions. Use this when facing a "fork in the road" career choice, prioritizing product features, or narrowing down topics for public speaking or content.
基于 SOC 职业分类
| name | summarizing-meetings |
| description | MUST BE USED when generating meeting summaries after analysis and routing. Creates per-brain and overall summaries, updates CLAUDE.md files. Works with analyzing-meetings and routing-brains skills. |
Generate actionable meeting summaries after routing:
For product-specific context, see CLAUDE.local.md.
Role: Programme Manager / Chief of Staff
Mindset:
## [Brain Name] - Meeting Updates
**Meeting**: [Meeting Name] | **Date**: [Date]
### Items Routed to This Brain
#### Decisions
- **[Decision Topic]** (YYYY-MM-DD)
- *Decision*: [What was decided]
- *Rationale*: [Why, if discussed]
- *Impact*: [What this affects]
#### Action Items
| Action | Owner | Due Date | Context |
|--------|-------|----------|---------|
| [Action] | [Name] | [Date] | [Related discussion] |
[Key point 1]
[Key point 2]
: [Why this matters]
: [Pending/Needs Resolution]
[Any items that also affect other brains]
# Meeting Summary | [Meeting Name] | [Date]
## Overview
**Attendees**: [List participants]
**Duration**: [Approximate length]
**Purpose**: [Meeting objective]
## Brain Distribution
| Brain | Items Routed | Key Outcome |
|------------|--------------|-------------|
| [Brain 1] | [N] items | [One-line summary] |
| [Brain 2] | [N] items | [One-line summary] |
| Unmatched | [N] items | Pending assignment |
## Cross-Brain Themes
- [Theme across multiple brains]
- [Dependencies identified]
## Consolidated Action Items
| # | Action | Owner | Due | Brain |
|---|--------|-------|-----|------------|
| 1 | [Action] | [Name] | [Date] | [Brain] |
## Unresolved Items
- [Items requiring follow-up]
## Next Steps
- [Overall next steps]
For short meetings or highlights only:
**Meeting Recap** | [Meeting Name] | [Date]
**Routed to Brains:**
- [Brain 1]: [N] items ([one-line summary])
- [Brain 2]: [N] items ([one-line summary])
**Key Decisions:**
- [Decision 1] → [Brain]
**Action Items:**
- [ ] [Action] - [Owner] - [Due] → [Brain]
**Unmatched Items**: [N] items pending assignment
Append new decisions:
- **[Decision Topic]** (YYYY-MM-DD)
- *Decision*: [What was decided]
- *Rationale*: [Why this choice]
- *Trade-offs*: [What we're giving up]
- *Related docs*: Meeting notes [Date]
Update if meeting changed status:
**Last Updated**: YYYY-MM-DD HH:MM
- **Progress**: [Updated based on discussion]
- **Recent Changes**: [What changed]
- **Next Milestone**: [Updated if discussed]
Before updating any CLAUDE.md, ask:
Should I update [Brain Name]/CLAUDE.md with:
- [N] decisions
- [N] action items
- [N] status updates
- [N] questions resolved
Proceed? (y/n)
Classify items using Leverage-Neutral-Overhead:
| Classification | Criteria | Handling |
|---|---|---|
| Leverage | Decisions affecting multiple brains, blockers, timeline changes | Highlight prominently |
| Neutral | Status updates, routine discussions | Standard placement |
| Overhead | Administrative, scheduling, logistics | Capture briefly or omit |
Before finalizing, ensure summary answers:
| Question | Your Summary Must Answer |
|---|---|
| "What did we decide?" | Clear decisions with owners |
| "Who's doing what by when?" | Action items with deadlines |
| "What's blocking us?" | Blockers with resolution plans |
| "What changed?" | Status updates with impact |
| "What do I need to do?" | Clear next steps for reader |
If any question can't be answered → there's a gap.
Routed items:
- frontend-modernization: 2 decisions, 1 action
- api-platform: 1 blocker, 2 discussions
- Unmatched: 0 items
# Meeting Summary | Weekly Sync | 2026-01-21
## Overview
**Attendees**: Engineering Lead, PM, Designer
**Duration**: 30 minutes
**Purpose**: Weekly status and blockers
## Brain Distribution
| Brain | Items | Key Outcome |
|------------|-------|-------------|
| frontend-modernization | 3 | React migration approved |
| api-platform | 3 | API blocker identified |
## Consolidated Action Items
| # | Action | Owner | Due | Brain |
|---|--------|-------|-----|------------|
| 1 | Create React migration plan | Engineering | Jan 28 | frontend-modernization |
| 2 | Escalate API blocker | PM | Jan 22 | api-platform |
## Next Steps
- React migration kickoff scheduled for next week
- API blocker needs resolution before launch