meeting-synthesis
Meeting Synthesis extracts structured intelligence from meeting notes or transcripts by separating decisions, action items, risks, and unresolved questions into a durable record. Use it to synthesize partner meetings, customer calls, diligence sessions, or internal strategy discussions into decision logs, action briefs, or follow-up messages that preserve both conclusions and honest uncertainty about what remains open.
git clone --depth 1 https://github.com/NateBJones-Projects/OB1 /tmp/meeting-synthesis && cp -r /tmp/meeting-synthesis/skills/meeting-synthesis ~/.claude/skills/meeting-synthesisSKILL.md
# Meeting Synthesis ## Problem Meeting notes are usually either too raw to reuse or too polished to trust. This skill turns them into a durable record of what happened, what was decided, what is still unresolved, and what needs to happen next. ## Audience - Primary: both operators and investors ## When to Use - Summarizing a partner, diligence, customer, or internal strategy meeting - Extracting decisions, actions, and follow-up items from transcripts or notes - Producing a clean meeting brief for a team or memo workflow - Turning discussion into reusable decision context ## When Not to Use - Broad source synthesis across many documents: use `research-synthesis` - Competitive market mapping without a meeting artifact: use `competitive-analysis` - Final memo drafting from a full diligence packet: use `deal-memo-drafting` - Reviewing spreadsheet assumptions: use `financial-model-review` ## Required Context Gather or confirm: - transcript, notes, or a faithful meeting summary - attendees and their roles if known - the meeting purpose - any surrounding project, deal, or strategic context - whether the desired output is internal notes, a decision log, or a follow-up message ## Process 1. Frame the meeting. - State what meeting this was and why it mattered. 2. Extract the real signal. - Separate decisions, action items, risks, unresolved questions, and useful context. 3. Attribute where possible. - Name owners and decision-makers when the notes support it. 4. Preserve uncertainty honestly. - If a point sounds important but was not resolved, keep it as unresolved. 5. Produce the right artifact. - Decision log, action list, follow-up draft, or meeting brief depending on the ask. 6. Optionally use Open Brain. - Search for prior related meetings or project notes before starting. - Capture key decisions or the final synthesis after the work is complete. ## Evidence and Judgment Rules - Use the meeting artifact as the primary source of truth. - Do not inflate tentative discussion into final decisions. - Keep attribution explicit when it is known and unforced when it is not. - Preserve material disagreement or open risk instead of smoothing it away. - Separate "decided", "assigned", and "discussed". ## Output Default output: - meeting purpose and quick summary - decisions made - action items with owners if known - risks and unresolved questions - recommended next follow-up - optional follow-up message or memo input ## Works Well With - `research-synthesis` when interviews or diligence calls become part of the evidence set - `deal-memo-drafting` when management or partner calls inform the recommendation - `competitive-analysis` when customer or market conversations sharpen the market picture ## Notes - This skill should reduce ambiguity, not create false closure. - The most valuable meeting output is often the list of unresolved questions.
Use Nate Jones OB1 Agent Memory from OpenClaw with provenance, scope, review, and use-policy discipline.
Continuous learning system that extracts reusable knowledge from work sessions. Triggers: (1) /aiception command, (2) 'save this as a skill' or 'extract a skill from this', (3) 'what did we learn?', (4) after non-obvious debugging or trial-and-error discovery. Creates new skills when valuable reusable knowledge is identified. Integrates with Open Brain to prevent duplicates.
Morning digest of yesterday's Open Brain thoughts, drafted to Gmail
Generate infographic images from any research doc, Open Brain thoughts, or analysis. Auto-chunks content, writes prompts, generates images via Gemini API (free tier), and saves to media/. Use --premium for better text rendering.
|
Use when processing voice transcripts, brain dumps, stream-of-consciousness notes, or any raw multi-topic capture. Extracts every idea thread, then evaluates each one with deep brainstorming, then captures results to Open Brain. Trigger on transcripts, exports, "process this", "pan for gold", "brain dump", "what did I say", or multi-topic markdown files.
|