Skip to main content

Business Operations

Meeting Notes Processor

Meeting Notes Processor takes rough meeting notes and turns them into something a team can publish internally without cleanup. It extracts outcomes, organizes follow-ups, and formats the result for fast sharing across communication channels. Operations teams, chiefs of staff, project leads, and agencies benefit when meeting artifacts need to move quickly from notes to updates. It is especially good for recurring meeting workflows where consistency and speed matter more than custom formatting each time. Production-grade reliability comes from its structured output model. Instead of improvising a summary every time, it produces repeatable meeting-note objects and ready-to-send summaries that fit operational systems.

Nexus CertifiedClaude CodeCodexOpenClawGoogle Antigravity
meeting-notessummariesactionsprocessingoperations

One-Time Purchase

$19.99

Sample Output

Sprint Retro Recap — FinTrack Platform

Sprint: Sprint 14 (closed yesterday) · 45-minute retro · Facilitator: Alex (Eng Manager) Attendees: Alex, Sam (Senior Dev), Jordan (QA Lead), Pat (Product Owner)

What changed

The team shipped the notifications feature on schedule despite two systemic drags: flaky CI cost six hours of cumulative blocked deploy time, and three mid-sprint scope changes traced back to design specs landing too late. Two corrective commitments came out of the room — a CI stability allocation for next sprint and a 48-hour spec lockout before sprint planning. Morale read positive; the team is owning the diagnosis, not assigning blame.


What went well vs what needs work

What went well

Shipped on time under friction

Notifications feature, mobile UX rework, alerting refactor

Notifications feature deliveredOn time
Mid-sprint scope changes vs last sprint2 fewer
Code review turnaround under 24h100%
Cross-team pairing on the alerting refactorStrong

What needs work

CI and spec readiness are the real drag

Patterns observed across the last three sprints, not one-time noise

Blocked deploy time from flaky CI6h
Tests identified as chronically flaky8
Mid-sprint scope changes from late specs3
Days lost to context switching2

Decisions

Decision 1

Allocate two days of next sprint to CI stability work. Sam owns. Six hours of blocked deploy time per sprint is the current baseline — this is the cost ceiling the team is willing to keep paying before it gets a dedicated fix.

Decision 2

Design specs must be approved 48 hours before sprint planning, no exceptions. Pat owns the template and the approval checklist. Three mid-sprint scope changes this sprint were traced directly to specs that arrived during planning, not before.


Action items

#TaskOwnerDuePriority
1Identify and quarantine the eight flakiest CI tests; document eachSamend of next weekP0
2Create design spec template with approval checklistPatthree days from todayP1
3Document the three mid-sprint scope changes with root causesJordantomorrowP1
4Schedule a CI-stability follow-up retro for end of next sprintAlexwithin two weeksP2

Open questions to settle at next sprint planning

Carry into planning

Flaky-test quarantine: dedicated sprint goal or side task?Sam
Should the 48-hour spec rule apply to bugfix-only sprints?Pat
Are we tracking CI flakiness as a sprint metric or just an incident log?Alex

Watch next sprint

If a fourth mid-sprint scope change happens after the spec rule is in place, that signals the rule is being bypassed or specs are incomplete on paper. Either way the next retro will need a harder conversation.


This sample illustrates the skill's output format. FinTrack Platform is a fictional company used recurringly across these sample outputs. Real client data is never included in sample outputs.

View full sample →

All sales final. No refunds on digital products.

Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.

Also in Meeting Suite

Bundle price: $55. Compare this skill with the full workflow bundle or Pro access.

Best for

Chiefs of staff turning a leadership offsite’s raw notes into a circulated readout, project managers converting weekly working-session notes into status updates, and consultants processing a workshop’s flip-chart photos into a shareable summary. Especially useful when the same notes need to land in two or three different formats (exec recap, action-item list, internal wiki page).

Not ideal for

Real-time scribing in the room — for that, use Meeting Scribe instead. Also a poor fit when the input is already a polished AI-generated transcript with timestamps and speaker labels; in that case you mostly want excerpting, not the full processor pipeline.

Included in this purchase

  • Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
  • Setup guidance for the right adapter in your workspace.
  • One-time license for the purchased skill version.

Setup

Plan for a short copy-and-configure setup in your preferred agent workspace. No custom integration is required for the skill file itself.

Claude CodeCodexOpenClawGoogle Antigravity

Related Skills

Meeting Suite
Featured
Meeting Scribe & Participant
Joins meetings, captures notes, answers in-session questions, and returns structured outcomes. Useful for live calls that need reliable documentation.
Claude CodeCodexOpenClawGoogle Antigravity
meetingstranscriptionnotes

$19.99

One-time license

View Skill
Meeting Suite
Featured
Meeting Prep
Builds pre-meeting intelligence packs with context, account changes, agenda ideas, and watchouts. Helps teams arrive prepared for important conversations.
Claude CodeCodexOpenClawGoogle Antigravity
meeting-prepbriefingsaccount-context

$19.99

One-time license

View Skill
Meeting Suite
Daily Briefing
Generates a daily briefing with schedule, priorities, communications, reminders, and watchlist items. Designed to help operators start the day aligned.
Claude CodeCodexOpenClawGoogle Antigravity
daily-briefingschedulepriorities

$19.99

One-time license

View Skill

Future Updates

This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.

Upgrade to Pro