Skip to content
Back to skills

Meeting Optimizer

ASecurity

Make meetings fewer, shorter, and better: agenda design, facilitation, async alternatives, and meeting audits. Use when calendars are full of low-value meetings or you're redesigning team collaboration norms.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aicodedecode/awesome-muse-skills --skill meeting-optimizer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meeting Optimizer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Meeting Optimizer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-meeting-optimizer/badge)](https://www.skillsdirectory.com/skills/aicodedecode-meeting-optimizer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: meeting-optimizer
description: Make meetings fewer, shorter, and better: agenda design, facilitation, async alternatives, and meeting audits. Use when calendars are full of low-value meetings or you're redesigning team collaboration norms.
category: productivity
---

# Meeting Optimizer

## Overview

Meetings are the most expensive communication: everyone's time simultaneously, plus prep and recovery.

Most run on autopilot: no agenda, wrong attendees, no decisions, no follow-through.

Optimize = question each meeting (async instead?), design survivors, facilitate tightly, record decisions.

Goal isn't zero meetings — it's meetings that earn their cost.

## When to use

- Team complains about too many meetings (or silently disengages in them)
- Meetings run over, drift, or end without decisions
- Designing meeting culture for a new team or company
- Deciding between a meeting and an async alternative
- Preparing to facilitate an important meeting well

## Core concepts

- **Purpose before scheduling.**
  Decide, align, create, or connect. 'Sync' isn't a purpose — what decision or output justifies gathering everyone?
- **The agenda is the meeting.**
  Topics, owner per topic, timeboxes, pre-reads — shared 24h ahead. No agenda = permission to decline.
- **Minimum viable attendees.**
  Roles: decider, contributor, informed. Informed people get notes, not invites. Easier to add than to un-waste an hour.
- **Async by default.**
  Status, FYI, approvals, doc feedback, first-draft brainstorming — all better async: written, on your schedule, with a record.
- **Decisions need records.**
  Close every meeting: what was decided, owner, date. Share within hours. Unrecorded decisions get re-litigated.
- **Timebox ruthlessly.**
  25/50 defaults, hard stops, visible parking lot. Ending 10 min early is a gift; overrun steals from the next commitment.
- **Pre-reads, not presentations.**
  Information transfer happens before, in writing. Meeting time is for questions, debate, decisions.
- **Facilitator + note-taker.**
  Separate roles, rotate them. Facilitator runs the agenda; note-taker captures decisions and actions live.

## Practical workflow

1. **Audit current meetings.**
   List recurring meetings: purpose, attendees, frequency, cost (people x time x freq). Score: keep / shorten / async / kill.
2. **Apply the async test.**
   'Could a doc + 48h of comments do this?' If yes, convert. Start with status meetings — almost always convertible.
3. **Template the survivors.**
   Decision meeting (options, recommendation, decision), weekly team (wins, priorities, blockers), 1:1 (their agenda first).
4. **Set facilitation norms.**
   Start on time regardless, timebox visibly, end 5 min early for action review. Rotate facilitation team-wide.
5. **Run tight meetings.**
   Open with purpose + desired outcome, work the agenda, park tangents visibly, close with decisions read back aloud.
6. **Follow through fast.**
   Notes within hours. Actions into task systems with dates — not left in the doc. Review open actions next time.
7. **Re-audit quarterly.**
   Every recurring meeting re-earns its slot. Kill liberally; calendars refill on their own if you let them.
8. **Default to shorter.**
   Change your defaults to 25/50. Most 60-min meetings fit in 50; most 30-min in 25. The constraint sharpens discussion.

## Common pitfalls

- **Status meetings as docs-in-disguise.**
  Written updates are faster to consume and searchable. The most convertible — and most common — waste.
- **Inviting everyone 'just in case'.**
  Twelve attendees, three talkers. Contributors get invites; everyone else gets notes.
- **No pre-reads.**
  Burning synchronous time on what could be read. Send materials early; start with questions.
- **Decision-free endings.**
  'Great discussion!' with no decision or owners. Even 'decide Tuesday with Sam's data' is a decision + owner + date.
- **Back-to-back scheduling.**
  No prep, debrief, or note capture. Buffers are hygiene, not luxury.
- **Recurring meeting inertia.**
  A 2022 weekly nobody would schedule today. Sunset it; let it be re-proposed with fresh purpose if needed.
- **Camera theater.**
  Mandating cameras without fixing purpose. Fix agenda and size first; engagement follows good design.
- **No written record.**
  Verbal decisions remembered differently by each attendee. Notes are the meeting's only durable output.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…