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 annua…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
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:
- The meeting's shape — attendees (count and rough seniority mix), length, frequency
- The rate basis — real loaded rates if known, or the placeholder bands (stated as placeholders: loaded cost ≈ 1.3–1.6× salary; senior-heavy rooms price differently than mixed ones)
- The outcomes — what this meeting demonstrably produces (decisions per month, the artifact, the alignment that prevented X); the meter prices against something or it's just a big number
- The political intent — pruning a calendar? Making a case to a boss? Auditing a culture? The output's framing follows the use
Framework: The Meter Rules
- Loaded rates, labeled honest: salary ÷ 2000 undercounts by 30–60% (benefits, overhead) — the meter uses loaded bands and states them as assumptions, because a cost argument built on precise-looking fake numbers dies at the first challenge. Ranges beat points.
- The recurring multiplier is the reveal: per-instance costs feel small; ×48 weeks is where the number gets attention. Every recurring meeting gets annualized — "this standing sync is a $56k/year line item" is the sentence that changes calendars.
- Price against the outcomes: decisions-per-quarter, the artifact produced, the coordination that visibly prevented rework — cost ÷ outcomes gives cost-per-decision, and a $4,600 monthly review producing zero decisions for three months prices its own verdict. Meetings with unpriceable-but-real outcomes (trust, cohesion) get that stated honestly, not zeroed — the meter informs judgment, it doesn't replace it.
- Levers in leverage order: attendee count first (the only lever that's linear and painless — two optional attendees off a weekly hour = ~$12k/year back), then length (60→25 min is usually free), then frequency (weekly→biweekly halves), then format (the async conversion, via [async-instead](../async-instead/SKILL.md)). Each lever ships with its recomputed price so the proposal is arithmetic, not opinion.
- The meter serves proposals, not prosecutions: the output frames as "here's what we're paying and three cheaper options" — cost-shaming a meeting its owner loves entrenches it; showing the owner what $30k of savings buys elsewhere converts them.
Output Format
Meeting Price: [meeting]
The Computation
[Attendees × length × loaded band = per instance · × frequency = annual · assumptions stated as ranges]
Cost Per Outcome
[The outcomes claimed/observed · price per decision/artifact · the unpriceable-but-real noted honestly]
The Levers (recomputed)
| Lever | Change | New annual price | Saved |
|---|---|---|---|
The Proposal Frame
[The one-paragraph case: current price → recommended lever(s) → what the savings buy]
Quality Checks
- [ ] Rates are loaded, banded, and labeled as assumptions
- [ ] Recurring meetings show the annualized number
- [ ] The cost is priced against stated outcomes, with unpriceables acknowledged
- [ ] Every lever carries its recomputed price
- [ ] The framing proposes, not prosecutes
Anti-Patterns
- [ ] Do not price with salary-only rates — undercounting discredits the whole meter
- [ ] Do not present per-instance costs for recurring meetings — the multiplier is the truth
- [ ] Do not zero the unpriceable outcomes — cohesion is real; the meter flags, judgment weighs
- [ ] Do not lead with the biggest number as an accusation — converted owners cut meetings; shamed owners defend them
- [ ] Do not stop at the price — the meter's product is the cheaper-supplier proposal, priced
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 meeting-cost-meter 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring m
- mohitagw15856/pm-claude-skills — Price meetings in money and focus — the attendee-hours × loaded-rate math, the recurring m