GuruDevvv/my-claude-skills / external/meeting-minutes-taker
meeting-minutes-taker
VerifiedTransforms raw meeting transcripts into high-fidelity, structured meeting minutes (notes / summaries). Use when (1) a meeting transcript is provided and meeting minutes, notes, or a summary are requested; (2) multiple versions of minutes must be merged without losing content; (3) existing minutes need review against the original transcript for missing items; (4) the transcript has anonymous speakers like "Speaker 1/2/3" or "发言人1" that need identifying (optionally mapped via a context.md team directory). Triggers on 会议纪要 / 会议记录 / 整理纪要 / 妙记转纪要, "write meeting minutes", "summarize this meeting", "merge these minutes", "what's missing from these notes". For fixing ASR/STT recognition errors in the raw transcript first, use transcript-fixer; this skill structures clean transcripts into minutes.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 1.5 KB |
| SKILL.md | skill md | 39.7 KB |
| references/completeness_review_checklist.md | markdown | 4.2 KB |
| references/context_file_template.md | markdown | 2.6 KB |
| references/meeting_minutes_template.md | markdown | 2.9 KB |
| КАК_ИСПОЛЬЗОВАТЬ.md | markdown | 592 B |
references/meeting_minutes_template.md
View on GitHub# Meeting Minutes Template
## Meeting Metadata
```markdown
---
title: [Meeting Title]
date: [YYYY-MM-DD]
attendees:
- Name (Role)
- Name (Role)
duration: [X hours/minutes]
location: [Virtual/Room Name]
---
```
## Document Structure
### 1. Executive Summary
Brief 2-3 sentence overview of what was discussed and decided.
### 2. Reviewed Materials (Optional)
If the meeting reviewed specific documents, mockups, or artifacts, list them here with brief descriptions. Include images inline if available.
```markdown

```
### 3. Key Decisions
For each major decision:
```markdown
### 3.X [Category] Decision Title
* **Decision:** Specific decision made
* **Logic:**
* Reasoning point 1
* Reasoning point 2
* **Quote:**
> "Exact quote from transcript supporting this decision" - **Speaker Name**
```
Categories: Architecture, API Design, Data Model, Process, Security, etc.
### 4. Discussion Details
Detailed breakdown by topic. Include:
- Context and background
- Options considered
- Trade-offs discussed
- Final direction
Use Mermaid diagrams where applicable:
```mermaid
sequenceDiagram
participant A as Component A
participant B as Component B
A->>B: Action description
B-->>A: Response
```
### 5. Action Items
| # | Task | Owner | Priority | Due Date | Notes (conditions/expiry) |
|---|------|-------|----------|----------|---------------------------|
| 1 | Task description | Person Name | P1/P2/P3 | YYYY-MM-DD | e.g. "slips to Tue if env not ready" |
The Notes column exists because conditional commitments ("report due Friday, slips to Tuesday if the environment isn't ready") lose their expiry condition in a four-column row — and the condition is exactly what a future reader queries when the deadline passes. Leave it empty when a task is unconditional; never bury a stated condition in Discussion prose only.
### 6. Parking Lot (Deferred Items)
Items explicitly deferred to future phases or follow-up discussions:
| Item | Reason Deferred | Follow-up |
|------|-----------------|-----------|
| Feature X | Out of MVP scope | Phase 2 |
| Decision Y | Needs more research | Offline discussion |
### 7. Open Questions
Unresolved questions that need follow-up:
- Question 1 - Owner to investigate
- Question 2 - Pending external input
---
## Formatting Guidelines
### Quote Format (CRITICAL)
Always use blockquote on separate line:
```markdown
* **Quote:**
> "This is the correct format" - **Speaker Name**
```
NOT inline:
```markdown
* **Quote:** > "This is wrong" - **Speaker**
```
### Speaker Attribution
Use consistent role-based attribution throughout:
- **Backend**, **Frontend**, **PM**, **TPM**, **Designer**, etc.
### Technical Terms
Preserve in English: API names, entity names, technical terminology, abbreviations
### Diagrams
Use Mermaid for:
- Sequence diagrams (data flow)
- ER diagrams (data models)
- Flowcharts (processes)
- State diagrams (state machines)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |