{"slug":"meeting-transcript-3","title":"meeting-transcript","summary":"Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-28T15:11:43.256183Z","repo":{"url":"https://github.com/huytieu/COG-second-brain","stars":1236,"forks":147,"license":"MIT","updatedAt":"2026-09-28T08:52:07Z"},"bodyHtml":"<hr>\n<h2>name: meeting-transcript\ndescription: Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering\nroles: [product-manager, engineering-lead, founder, designer]\nintegrations: []</h2>\n<h1>COG Meeting Transcript Skill</h1>\n<h2>When to Invoke</h2>\n<ul>\n<li>User shares a meeting transcript or recording notes</li>\n<li>User says \"process meeting\", \"meeting notes\", \"meeting transcript\"</li>\n<li>User has a block of text from a meeting they want structured</li>\n<li>User mentions wanting to extract action items from a meeting</li>\n</ul>\n<h2>Agent Mode Awareness</h2>\n<p><strong>Check <code>agent_mode</code> in <code>00-inbox/MY-PROFILE.md</code> frontmatter:</strong></p>\n<ul>\n<li>If <code>agent_mode: team</code> — use the full parallel agent execution strategy below (3 agents)</li>\n<li>If <code>agent_mode: solo</code> — process sequentially: extract content first, then analyze dynamics, then enrich with context.</li>\n</ul>\n<h2>Purpose</h2>\n<p>Extract strategic insights from meeting recordings and notes with intelligent content filtering to focus on substantive, actionable content while removing noise and irrelevant information.</p>\n<h2>Command: <code>/meeting-transcript</code></h2>\n<h2>Parallel Agent Team Execution Strategy</h2>\n<p><strong>Use parallel agents to process different aspects of the transcript simultaneously.</strong></p>\n<h3>Phase 1: Setup (Orchestrator)</h3>\n<ol>\n<li>Receive transcript content from user</li>\n<li>Detect content type (meeting vs braindump) and classify domain</li>\n<li>Split transcript into logical sections for parallel processing</li>\n</ol>\n<h3>Phase 2: Parallel Processing (Spawn 2-3 Agents Simultaneously)</h3>\n<p><strong>Launch ALL agents in a single message using Task tool with <code>run_in_background: true</code>:</strong></p>\n<h4>Agent 1: \"content-extractor\" (subagent_type: general-purpose)</h4>\n<pre><code>Extract structured content from the meeting transcript.\n\n1. Filter out side chats, technical difficulties, and irrelevant banter\n2. Identify and extract: decisions made (with rationale), action items (with owners/deadlines), strategic themes\n3. Capture key quotes and insights from participants\n4. Note unresolved issues and follow-up needs\n\nReturn: Decisions list, action items list, strategic themes, key quotes, unresolved issues.\n</code></pre>\n<h4>Agent 2: \"dynamics-analyst\" (subagent_type: general-purpose)</h4>\n<pre><code>Analyze team dynamics and meeting effectiveness.\n\n1. Assess communication patterns and participation levels\n2. Identify leadership moments and collaboration quality\n3. Evaluate decision-making process effectiveness\n4. Assess meeting efficiency (time well spent vs wasted)\n5. Note any tensions, disagreements, or alignment issues\n\nReturn: Team dynamics assessment, participation analysis, meeting effectiveness score.\n</code></pre>\n<h4>Agent 3: \"context-enricher\" (subagent_type: general-purpose)</h4>\n<pre><code>Enrich meeting content with project/product context.\n\n1. If project-related: read recent braindumps and notes for context\n2. Check if discussed topics relate to known issues/PRs on GitHub\n3. Connect decisions to existing strategic priorities\n4. Identify competitive intelligence if competitors mentioned\n\nReturn: Contextual connections, related documents, strategic alignment notes.\n</code></pre>\n<h3>Phase 3: Assembly (Orchestrator)</h3>\n<ol>\n<li>Collect results from all processing agents</li>\n<li>Assemble structured meeting summary following Content Structure template</li>\n<li>Add proper metadata (participants, duration, type, action item count)</li>\n<li>Save to appropriate domain meeting folder</li>\n<li>Flag urgent action items for immediate attention</li>\n</ol>\n<h2>Content Filtering Guidelines</h2>\n<h3>EXCLUDE (Filter Out)</h3>\n<ul>\n<li><strong>Side Conversations</strong>: \"Hey, did you see the game last night?\"</li>\n<li><strong>Technical Difficulties</strong>: \"Can you hear me now?\" \"Your mic is muted\"</li>\n<li><strong>Incomplete Thoughts</strong>: \"So I was thinking we should... never mind\"</li>\n<li><strong>Casual Banter</strong>: Weather, personal anecdotes unrelated to work</li>\n<li><strong>Interruptions</strong>: \"Sorry, I have to take this call\"</li>\n<li><strong>Unclear Statements</strong>: Mumbled or inaudible content</li>\n</ul>\n<h3>INCLUDE (Keep and Analyze)</h3>\n<ul>\n<li><strong>Strategic Discussions</strong>: Market analysis, competitive positioning</li>\n<li><strong>Decision Points</strong>: \"We've decided to move forward with Option A\"</li>\n<li><strong>Action Items</strong>: \"Alex will complete the analysis by Friday\"</li>\n<li><strong>Problem Solving</strong>: Discussion of challenges and proposed solutions</li>\n<li><strong>Planning</strong>: Timeline discussions, resource allocation</li>\n<li><strong>Insights</strong>: \"The key insight is that customers want...\"</li>\n<li><strong>Concerns</strong>: \"My concern is that this approach might...\"</li>\n</ul>\n<h2>Metadata Template</h2>\n<pre><code>---\ntype: meeting-transcript\ndomain: [personal|professional|project-specific]\nproject: [project-name] # Only for project-specific meetings\ndate: YYYY-MM-DD\ncreated: YYYY-MM-DD HH:MM\nmeeting_type: [1-on-1|team-meeting|strategic-planning|project-review|other]\nparticipants: [participant1, participant2, participant3]\nduration: [minutes]\ncontent_filtered: true\naccuracy_verified: [true|false|pending]\naction_items_count: [number]\ndecisions_count: [number]\ntags:\n  - meeting\n  - transcript\n  - domain-tag\n  - project-tag\nstatus: [processed|needs-follow-up|action-required]\n---\n</code></pre>\n<h2>Content Structure</h2>\n<h3>1. Meeting Overview</h3>\n<ul>\n<li><strong>Date/Time</strong>: When the meeting occurred</li>\n<li><strong>Participants</strong>: Who was present and their roles</li>\n<li><strong>Purpose</strong>: Primary objective of the meeting</li>\n<li><strong>Duration</strong>: Actual meeting length</li>\n<li><strong>Type</strong>: Category of meeting</li>\n</ul>\n<h3>2. Key Decisions (Verified Content Only)</h3>\n<ul>\n<li><strong>Decision</strong>: What was decided</li>\n<li><strong>Rationale</strong>: Why this decision was made</li>\n<li><strong>Owner</strong>: Who is responsible for implementation</li>\n<li><strong>Timeline</strong>: When decision takes effect</li>\n<li><strong>Impact</strong>: Expected outcomes and implications</li>\n</ul>\n<h3>3. Action Items (Substantive Only)</h3>\n<ul>\n<li><strong>Task</strong>: Specific action to be taken</li>\n<li><strong>Owner</strong>: Person responsible</li>\n<li><strong>Deadline</strong>: When it's due</li>\n<li><strong>Dependencies</strong>: What needs to happen first</li>\n<li><strong>Success Criteria</strong>: How completion will be measured</li>\n</ul>\n<h3>4. Strategic Themes (From Substantial Discussion)</h3>\n<ul>\n<li><strong>Theme</strong>: Major topic or pattern discussed</li>\n<li><strong>Context</strong>: Why this theme is important</li>\n<li><strong>Implications</strong>: What this means for the team/project</li>\n<li><strong>Next Steps</strong>: How to address or leverage this theme</li>\n</ul>\n<h3>5. Unresolved Issues</h3>\n<ul>\n<li><strong>Issue</strong>: Problem or question that remains open</li>\n<li><strong>Context</strong>: Background and importance</li>\n<li><strong>Blocking Factors</strong>: What's preventing resolution</li>\n<li><strong>Proposed Next Steps</strong>: How to move forward</li>\n</ul>\n<h3>6. Team Dynamics Assessment</h3>\n<ul>\n<li><strong>Communication Quality</strong>: How effectively team communicated</li>\n<li><strong>Decision-Making Process</strong>: How decisions were reached</li>\n<li><strong>Participation</strong>: Who contributed and how</li>\n<li><strong>Meeting Efficiency</strong>: Time management and focus</li>\n<li><strong>Areas for Improvement</strong>: Suggestions for better meetings</li>\n</ul>\n<h2>Domain-Specific Processing</h2>\n<h3>Personal Domain Meetings</h3>\n<ul>\n<li>Focus on career development and personal growth</li>\n<li>Maintain strict privacy for personal discussions</li>\n<li>Extract learning and development opportunities</li>\n<li>Save to <code>[CUSTOMIZE: path/to/personal/]meetings/</code></li>\n</ul>\n<h3>Professional Domain Meetings</h3>\n<ul>\n<li>Analyze leadership and team management aspects</li>\n<li>Extract strategic business insights</li>\n<li>Identify professional development opportunities</li>\n<li>Save to <code>[CUSTOMIZE: path/to/professional/]meetings/</code></li>\n</ul>\n<h3>Project-Specific Meetings</h3>\n<ul>\n<li>Connect to project metrics and milestones</li>\n<li>Analyze progress against project goals</li>\n<li>Extract competitive and market intelligence</li>\n<li>Save to <code>[CUSTOMIZE: path/to/projects/][project-name]/meetings/</code></li>\n</ul>\n<h2>Content Filtering Protocol</h2>\n<h3>Step 1: Initial Scan</h3>\n<ul>\n<li>Identify meeting phases (intro, main discussion, wrap-up)</li>\n<li>Mark obvious side conversations and technical issues</li>\n<li>Flag incomplete or unclear statements</li>\n</ul>\n<h3>Step 2: Relevance Assessment</h3>\n<ul>\n<li>Evaluate each segment for strategic value</li>\n<li>Determine if content relates to meeting objectives</li>\n<li>Assess completeness and accuracy of information</li>\n</ul>\n<h3>Step 3: Accuracy Verification</h3>\n<ul>\n<li>Cross-check contradictory statements</li>\n<li>Flag information that seems incorrect</li>\n<li>Note areas requiring clarification</li>\n</ul>\n<h3>Step 4: Context Preservation</h3>\n<ul>\n<li>Ensure decisions have sufficient context</li>\n<li>Maintain background for action items</li>\n<li>Preserve strategic discussion flow</li>\n</ul>\n<h2>Quality Assurance</h2>\n<h3>Verification Standards</h3>\n<ul>\n<li>All decisions must have clear context and rationale</li>\n<li>Action items must have specific owners and deadlines</li>\n<li>Strategic themes must be supported by substantial discussion</li>\n<li>Team dynamics assessment must be based on observable patterns</li>\n</ul>\n<h3>Uncertainty Handling</h3>\n<ul>\n<li>Flag potentially incorrect information for user confirmation</li>\n<li>State confidence levels for interpretations</li>\n<li>Request clarification for ambiguous content</li>\n<li>Explicitly note when information is incomplete</li>\n</ul>\n<h2>Integration with Daily Brief</h2>\n<p>Meeting notes processed by this command feed directly into the daily brief:</p>\n<ul>\n<li><strong>Phase 2, Agent 3</strong> (<code>meeting-reviewer</code>) scans for recent meeting files</li>\n<li><strong>Phase 3</strong> cross-references action items against GitHub PRs and Linear issues</li>\n<li><strong>Section 13</strong> (<code>Meeting Follow-Up Tracker</code>) tracks commitment completion</li>\n</ul>\n<p>This creates accountability: decisions and action items from meetings are automatically tracked against actual execution in code and project management tools.</p>\n<h2>Learning Integration</h2>\n<ul>\n<li>Track meeting effectiveness patterns over time</li>\n<li>Identify successful decision-making processes</li>\n<li>Learn team communication preferences</li>\n<li>Adapt filtering based on user feedback on relevance</li>\n</ul>\n","files":[{"path":"SKILL.md","sizeBytes":9124,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-28T15:13:45.985702Z","sha256":"4BDC2404B750F4B4E8BD5A42B6133A8987F0BFA8B0F9FA4347EC7CF3B9F6CF06","sizeBytes":3909},"review":null,"source":{"repositoryUrl":"https://github.com/huytieu/COG-second-brain","path":".claude/skills/meeting-transcript","license":"MIT","commit":"4cdb6015dc6eb66f74bac513856ff6446ecb5d1b","subtreeSha":"5A01AC9D06DCCEBB94DF7EB5C8D3624FD51A7BF7D9A344FD363340BE8627E0DD","lastSyncedAt":"2026-09-28T15:11:28.148164Z"},"reviewedAt":"2026-09-28T15:17:26.894919Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/huytieu/COG-second-brain/tree/main/.claude/skills/meeting-transcript"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install huytieu-cog-second-brain@llmmart"},{"target":"git","command":"git clone https://github.com/huytieu/COG-second-brain.git"}]}