Meeting Audit
Most knowledge workers spend the better part of a working week each month in meetings that produced no decision and no output. 'Have fewer meetings' is not a plan. The Meeting Audit classifies every meeting on your calendar with a verdict and a replacement — Keep, Restructure, Async, or Kill.
What this skill does
Crawler-style "audit your meetings" advice tells you to cancel things. That works for a week — then the meetings come back, because nobody had a defensible reason for which ones to cut and which to keep. The skill is triage, and triage has to be specific. Every meeting on your calendar gets scored on four criteria and assigned one of four verdicts with a tailored action.
The framework is VETO. Value produced — does the meeting actually generate decisions, alignment, or unblocked work, or is it information that could be a doc? Essentiality of your presence — are you needed, or there "just in case"? Time efficiency — is the duration proportional to the output, or is half of it filler and stragglers? Outcome clarity — does anyone leave with written decisions and action items, or is it a "we discussed" meeting? Score across all four and the verdict drops out: Keep (protect it), Restructure (shorten, tighten, fewer attendees), Async (here's the specific replacement format), Kill (here's the polite decline script).
Before any of that runs you get the Meeting Tax — total hours, percentage of your week, plus a context-switch penalty of 15 minutes per meeting for the mental ramp-down/ramp-up. The number is usually larger than people expect, and it changes how the rest of the audit lands. The output is a verdict table with hours saved per category, followed by per-meeting breakdowns and replacement scripts. Reclaimed time gets blocked as deep work the same session, because unprotected free hours get re-colonised by new meetings within a fortnight.
It handles the constrained cases. Boss's standing meeting you can't decline? RESTRUCTURE: attend the first 15 minutes, exit when your topic is done. New joiner who inherited 11 recurring slots? Attend each once for firsthand VETO assessment, then run the full audit at week two. And it builds in the follow-through — 2-week check (did the async replacements actually happen?), 4-week review (has total meeting time crept back up?). Meeting creep is gravity. The audit is the resistance.
When this triggers
- ·Your week is 28+ hours of meetings and you've forgotten what doing the actual work feels like
- ·You suspect three of your recurring meetings could be a Slack post but haven't done the analysis
- ·You want a defensible Keep/Cut/Restructure list to take to your manager or your team
- ·You just started a new role and inherited recurring meetings nobody can explain
- ·You can't kill the meetings (boss's standing, regulatory) but want every one of them shorter
Example
Trigger
User pastes one week of calendar — 22 meetings, 27 hours.
Output
Meeting Tax: 27h meetings + 5.5h context-switch penalty = 32.5h consumed / 40h week. Effective work: 7.5h. Verdicts (22 meetings): · KEEP: 4 (8h) — decisions made, you're essential, ends on time · RESTRUCTURE: 7 (10.5h → 5.5h saved) · ASYNC: 6 (7.5h saved) — pure status, no decisions · KILL: 5 (3.5h saved) — optional attendance, no output Top targets: · "Weekly product sync" (8 ppl, 60min, no agenda, no decisions logged in 4 weeks) → ASYNC: 2-min Loom + thread. · "Engineering / design alignment" (60min, runs 15 min late) → RESTRUCTURE: 30 min with pre-read. · "Optional roadmap review" → KILL: decline script attached. Reclaimed: 16.5h/week. Block 8h NOW as deep work before meetings re-colonise the time.
Get this skill + 15 more
Included in the The Agency Owner Stack — scale delivery without scaling headcount. Save $130+ vs buying individually.
Get The Agency Owner Stack — $149What you get
- 172-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Project Management
Doesn't write teleprompter scripts — it writes structured talking outlines that make the speaker sound prepared, not robotic
Doesn't write internal status reports — it writes client-facing documents that manage expectations and build the relationship
Doesn't just format text — it filters for signal, highlight blockers early, and write updates that make managers confident without requiring follow-up questions
Doesn't just tell people to block time — it analyzes their role, energy patterns, and meeting load to engineer a schedule where deep work is structurally guaranteed, not aspirational
Doesn't give vague advice like "check email twice a day" — it builds the specific rules, filters, templates, and workflows that make inbox zero sustainable
Doesn't summarize meetings — it extracts the commitments that make meetings worth having
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles