summarize-meeting

Summarize meeting transcripts into action items, decisions, and key points.

3|Updated Dec 3, 2025

Search Tags:#transcript #tasks #meeting #project-management #summarize #action-items #github-issues

Ready to run

npx skills add https://github.com/braselog/researchAssistant --skill summarize-meeting-braselog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: summarize-meeting
Source: https://github.com/braselog/researchAssistant/tree/main/.ra/skills/summarize-meeting
Command: npx skills add https://github.com/braselog/researchAssistant --skill summarize-meeting-braselog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill extracts action items, decisions, and key points from meeting transcripts and routes items to tasks.md or GitHub Issues based on estimated effort.

Core Features & Use Cases

Action item extraction: Identify tasks, owners, and due dates from transcripts.
Decision capture: Record decisions with context for traceability.
Routing & integration: Automatically route quick tasks to tasks.md and longer tasks to GitHub Issues based on complexity; supports integration with .research/meetings and .research/project_telos.
Use Case: After a lab meeting, summarize outcomes and populate task lists for the next sprint.

Quick Start

Use the summarize-meeting skill to generate a summary from a transcript file located in .research/meetings/transcripts.

Frequently Asked Questions about summarize-meeting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract action items and decisions from meeting transcripts?▼

To extract action items and decisions from meeting transcripts, you need a transcript file, project context, and existing tasks.md. The Skill analyzes the transcript to identify tasks, owners, due dates, and decisions for traceability.

Can I automatically route meeting action items to GitHub Issues and tasks.md?▼

Yes, you can automatically route meeting action items to GitHub Issues and tasks.md. It classifies items based on estimated effort and project context, sending quick tasks to tasks.md and longer tasks to GitHub Issues.

What file structure do I need to summarize meeting transcripts into actionable tasks?▼

You need a transcript file stored under .research/meetings/transcripts, a project context file, and an existing tasks.md file. The Skill uses these inputs to output a structured summary and optional GitHub Issues for longer tasks.

How does transcript summarization classify items into tasks or issues?▼

Transcript summarization classifies items into tasks or issues by analyzing the transcript content alongside project context. It evaluates the estimated effort and complexity of each action item to route it appropriately.

How do I capture key points and outcomes from lab meetings for the next sprint?▼

To capture key points and outcomes from lab meetings for the next sprint, use the Skill to generate a structured summary from your transcript. It identifies decisions and populates task lists based on the meeting outcomes.

Does meeting transcript summarization work without existing project context files?▼

No, meeting transcript summarization requires a project context file to classify items accurately. It uses the project context to determine whether an action item should become a quick task or a GitHub Issue.