standing-meeting-audit
Audit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our calendar is all standing syncs, which meetings should die, or reset the team's meeting load. Produces the inventory with per-meeting verdicts, the experiment protocol, the merge map, and the re-accretion guard.
npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Standing Meeting Audit Skill Standing meetings are organizational scar tissue: each was created for a reason, the reason healed, the meeting remained. Nobody audits them because each is individually defensible-ish and collectively they're the calendar. The audit tests each slot against three questions — does the original purpose still exist, does the attendance reflect it, what has it produced lately — renders verdicts (keep / shrink / merge / kill / experiment), and deploys the un-arguable tool: *cancel it for two weeks and see what breaks.* Almost nothing breaks, and what breaks reveals the meeting's true minimal form. ## What This Skill Produces - **The inventory** — every recurring meeting: origin purpose, current attendance, recent outcomes, annualized cost (via [meeting-cost-meter](../meeting-cost-meter/SKILL.md)) - **The verdicts** — keep / shrink (length, cast, or frequency) / merge / kill / two-week-experiment, with reasons - **The experiment protocol** — how the pause runs, what "broke" means, and the decision rule at the end - **The re-accretion guard** — expiry dates on new standing meetings, and the quarterly re-audit ## Required Inputs Ask for these if not provided:
- What This Skill Produces
- Required Inputs
- Framework: The Audit Rules
- Output Format
- The Inventory & Verdicts
- The Experiments
- The Merge Map
- The Guard
- Quality Checks
- Anti-Patterns
What does the standing-meeting-audit skill do?
Audit the recurring meetings a team has accreted — each standing slot tested against its original purpose, current attendance reality, and outcomes, with keep/shrink/merge/kill verdicts and the two-week cancellation experiment that settles arguments. Use when asked audit our recurring meetings, our calendar is all standing syncs, which meetings should die, or reset the team's meeting load. Produces the inventory with per-meeting verdicts, the experiment protocol, the merge map, and the re-accretion guard.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.