recurring-meeting-pruner
Prune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurring, which meetings can I stop attending, or leave a meeting politely. Produces the personal audit with role verdicts, the exit move per meeting, the scripts, and the calendar-shape after.
npx skills add mohitagw15856/pm-claude-skills --skill recurring-meeting-pruner --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.
# Recurring Meeting Pruner Skill The [standing-meeting-audit](../standing-meeting-audit/SKILL.md) fixes a *team's* meetings; this skill fixes *yours* — the personal version, where the question isn't "should this meeting exist" but "should it contain me." Most personal calendars carry meetings attended by inertia: invited once for a project that ended, kept for fear of missing something, present as a spectator. The prune audits your actual role in each (decider, contributor, informed, or furniture), applies the four exit moves, and scripts the departures — because leaving well costs one message, while ghosting costs standing. ## What This Skill Produces - **The personal audit** — every recurring meeting: your honest role, your last contribution, what you'd lose by absence - **The verdict per meeting** — stay / leave (with script) / delegate / downgrade-to-notes / halve (alternate weeks) - **The exit scripts** — the graceful leave, the delegate handoff, the notes-instead request - **The after-shape** — the reclaimed hours and what they're re-blocked for (unblocked reclaimed time evaporates) ## Required Inputs Ask for these if not provided: - **The recurring load** — the standing meet
- What This Skill Produces
- Required Inputs
- Framework: The Prune Rules
- Output Format
- The Audit
- The Moves + Scripts
- The After-Shape
- Quality Checks
- Anti-Patterns
What does the recurring-meeting-pruner skill do?
Prune your own recurring-meeting load — the personal calendar audit (your role in each, honestly), the four exit moves (leave, delegate, downgrade to notes, halve), and the graceful exit scripts that don't burn standing. Use when asked get me out of some of these meetings, my calendar is 80% recurring, which meetings can I stop attending, or leave a meeting politely. Produces the personal audit with role verdicts, the exit move per meeting, the scripts, and the calendar-shape after.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill recurring-meeting-pruner --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.