Agent skill

Standing Meeting Audit

by mohitagw15856 in mohitagw15856/pm-claude-skills

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…

MITAuto-check passed

Install Standing Meeting Audit

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills standing-meeting-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/standing-meeting-audit .claude/skills/standing-meeting-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
standing-meeting-audit
GitHub stars
1.4k
Token cost
~1.4k tokens
SKILL.md length
709 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 5 steps: Origin vs. present tense: every standing… → Attendance is testimony: chronic… → Outcomes or ritual: last month's notes… → …
  • Asked audit our recurring meetings
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Audit Rules and Output Format, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Standing Meeting Audit is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked audit our recurring meetings
  • Our calendar is all standing syncs
  • Which meetings should die
  • Reset the teams meeting load

Example prompts

  • “/standing-meeting-audit”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Origin vs. present tense: every standing meeting was born for a purpose — the audit asks whether that purpose still exists in present…
  2. Attendance is testimony: chronic optional-izing, half the room multitasking, the same three people talking while nine watch — attendance…
  3. Outcomes or ritual: last month's notes show decisions and actions, or they show weather. Meetings producing only status updates get the…
  4. The two-week experiment beats debate: contested verdicts get the pause — cancelled two cycles, with a visible parking lot for what would…
  5. Guard the re-accretion: every new standing meeting gets an expiry (12 weeks default) — renewal requires the three-question test again; and…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Standing Meeting Audit loads about 1.4k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 709 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 709 words, ~1,421 tokens.

Download SKILL.mdSave it as .claude/skills/standing-meeting-audit/SKILL.md (or your agent's skills folder).
name
standing-meeting-audit
description
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.

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)
  • 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:

  • The calendar's recurring population — the standing meetings with their casts, lengths, frequencies; the audit needs the census, not the impressions
  • Per meeting, the archaeology — why it was created (ask the oldest attendee), what it decided/produced last month (check the notes — absent notes are themselves a finding)
  • The dependencies — which meetings feed others (the prep meeting for the review meeting is a chain; verdicts consider chains whole)
  • The authority — who can actually kill what; auditing meetings the auditor can't touch produces resentment reports, not calendars

Framework: The Audit Rules

  1. Origin vs. present tense: every standing meeting was born for a purpose — the audit asks whether that purpose still exists in present tense ("the launch coordination sync" for a launch that shipped in March). Purpose-expired meetings are the easy kills, and there are always more than expected.
  2. Attendance is testimony: chronic optional-izing, half the room multitasking, the same three people talking while nine watch — attendance reality testifies about value more honestly than any survey. A nine-person meeting that's actually a three-person conversation gets shrunk to the conversation.
  3. Outcomes or ritual: last month's notes show decisions and actions, or they show weather. Meetings producing only status updates get the async-instead conversion test — status moves in documents; discussion needs rooms. No notes at all = the meeting itself doesn't believe it produces anything worth recording.
  4. The two-week experiment beats debate: contested verdicts get the pause — cancelled two cycles, with a visible parking lot for what would have been raised. Outcome A: nothing broke → kill confirmed. Outcome B: two things broke → the meeting returns as those two things (shorter, smaller). The experiment converts opinion wars into evidence, and its reversibility is why owners accept it.
  5. Guard the re-accretion: every new standing meeting gets an expiry (12 weeks default) — renewal requires the three-question test again; and the audit itself recurs quarterly at 30 minutes, because scar tissue regrows. The guard is what makes this an immune system instead of a purge.
Show full SKILL.md (218 more words)Show less

Output Format

Standing Meeting Audit: [team] — [N] recurring slots, ~$[annual total]

The Inventory & Verdicts

MeetingOrigin purpose (still live?)Attendance realityRecent outcomesAnnual costVerdict

The Experiments

[Contested meetings → the two-cycle pause · the parking lot location · the decision rule at cycle end]

The Merge Map

[Overlapping slots → the combined form · chains resolved whole]

The Guard

[Expiry-by-default on new standings · the quarterly 30-minute re-audit, owned by (role)]

Quality Checks

  • Every recurring slot is in the inventory with cost annualized
  • Origin purposes were checked in present tense, not assumed alive
  • Verdicts cite attendance and outcome evidence, not vibes
  • Contested kills route through the experiment, not the argument
  • The expiry default and re-audit cadence are installed

Anti-Patterns

  • Do not audit by survey — people defend meetings they multitask through; behavior testifies, opinions perform
  • Do not kill by decree what an experiment can kill by evidence — reversibility is the political unlock
  • Do not shrink everything politely instead of killing anything — ten 25-minute zombies still eat the calendar
  • Do not ignore the chains — killing the prep meeting while keeping the review it feeds breaks both
  • Do not audit once — without the expiry guard, the calendar regrows to baseline in two quarters

Example Trigger Phrases

  • "Audit our recurring meetings."
  • "Our calendar is all standing syncs."
  • "Which meetings should die?"
  • "Reset the team's meeting load."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/standing-meeting-audit of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Standing Meeting Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Standing Meeting Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Standing Meeting Audit this skillmohitagw15856/pm-claude-skills1.4k—~1.4kAutomated safety check: PassMIT
Meetingsalirezarezvani/claude-skills28k—~1.5kAutomated safety check: PassMIT
Meeting Minutesgithub/awesome-copilot40k2 repos~2kAutomated safety check: PassMIT
Meeting Action ItemsNousResearch/hermes-agent252k—~950Automated safety check: PassMIT
Meeting Notesoutline/outline41k—~551Automated safety check: PassCustom licence
Summarize Meetingphuryn/pm-skills27k—~749Automated safety check: PassMIT

Similar skills

  • Meetings

    alirezarezvani/claude-skills

    A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…

    28k GitHub stars~1.5k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Meeting Minutes

    github/awesome-copilot

    Official

    Generate concise, actionable meeting minutes for internal meetings.

    40k GitHub starsUsed in 2 repos~2k tokens
    Productivity & AutomationAuto-check passed
  • Meeting Action Items

    NousResearch/hermes-agent

    Turn meeting notes into cited decisions, owners, tickets. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~950 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Meeting Notes

    outline/outline

    Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.

    41k GitHub stars~551 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Summarize Meeting

    phuryn/pm-skills

    Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.

    27k GitHub stars~749 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Meeting Distiller Pro

    sickn33/agentic-awesome-skills

    Transform messy meeting notes and transcripts into structured action items, decisions, and follow-ups.

    47k GitHub starsUsed in 1 repo~1k tokens
    Productivity & AutomationAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Standing Meeting Audit

What does Standing Meeting Audit 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…. Standing Meeting Audit is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Standing Meeting Audit?

Standing Meeting Audit fits situations like: asked audit our recurring meetings; our calendar is all standing syncs; which meetings should die; reset the teams meeting load.

How do I install Standing Meeting Audit in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit -a claude-code`. Or copy the skill folder (skills/standing-meeting-audit in mohitagw15856/pm-claude-skills) into .claude/skills/standing-meeting-audit in your project. Claude Code loads it when a task matches its description.

How do I install Standing Meeting Audit in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit -a codex`. Or copy the skill folder (skills/standing-meeting-audit in mohitagw15856/pm-claude-skills) into .agents/skills/standing-meeting-audit in your project. Codex loads it when a task matches its description.

Can I use Standing Meeting Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill standing-meeting-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/standing-meeting-audit, .gemini/skills/standing-meeting-audit, .github/skills/standing-meeting-audit and .opencode/skills/standing-meeting-audit in your project.

What does Standing Meeting Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Standing Meeting Audit is instructions for the agent only.

Does Standing Meeting Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Standing Meeting Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Standing Meeting Audit use?

Standing Meeting Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Standing Meeting Audit use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Standing Meeting Audit?

Skills that share tags, products or a category with Standing Meeting Audit: Meetings (alirezarezvani/claude-skills, 28k stars), Meeting Minutes (github/awesome-copilot, 40k stars), Meeting Action Items (NousResearch/hermes-agent, 252k stars) and Meeting Notes (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Standing Meeting Audit?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.