meeting-cost-meter
Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this recurring meeting worth it, or make the case for fewer attendees. Produces the cost computation with stated assumptions, the recurring annualization, the cost-per-outcome read, and the reduction levers ranked.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill meeting-cost-meter --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.
# Meeting Cost Meter Skill Meetings are the only five-figure purchases made without a price tag: a weekly hour with nine people at a blended $120/hour loaded rate is ~$56,000 a year — a number nobody approved because nobody computed it. The meter computes it (attendee-hours × honest loaded rates × the recurring multiplier), then asks the only question the number exists for: *what does this price buy, and is there a cheaper supplier* — fewer people, shorter slot, lower frequency, or a document. The output is leverage for change, not gotcha theater: the point is better purchases, not shame. ## What This Skill Produces - **The price** — per instance and annualized, with the rate assumptions stated (loaded, not salary-only, and labeled as estimates) - **The context-switch surcharge** — the honest note that the calendar cost exceeds the clock cost (fragmentation prices separately — see [context-switch-budget](../context-switch-budget/SKILL.md)) - **The cost-per-outcome read** — what the meeting produces, priced per decision/artifact - **The reduction levers, ranked** — attendees, length, frequency, format — each with its recomputed price ## Required Inputs Ask for these if not provided:
- What This Skill Produces
- Required Inputs
- Framework: The Meter Rules
- Output Format
- The Computation
- Cost Per Outcome
- The Levers (recomputed)
- The Proposal Frame
- Quality Checks
- Anti-Patterns
What does the meeting-cost-meter skill do?
Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring multiplier that turns a weekly 30-minutes into a real annual number, and the cost-vs-outcome read that decides what the price buys. Use when asked what does this meeting cost, price our meeting culture, is this recurring meeting worth it, or make the case for fewer attendees. Produces the cost computation with stated assumptions, the recurring annualization, the cost-per-outcome read, and the reduction levers ranked.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill meeting-cost-meter --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.