Percerno Skillsbeta
← everything it can do · productivity

Meetings TEXT

Evaluates whether a meeting is necessary by calculating its financial cost and checking for required decision/agenda/owner criteria. If justified, it generates a timeboxed, decision-first agenda and extracts owned action items from raw notes with due dates.

2 uses this weeksource alirezarezvanilicence MIT
Quality gate: PASS · better answers · measured 2026-10-24
Blind-judged against the bare model on 2 requests: average lift +1.5 points (specificity, structure, method, fit).
won 1/2, lift +1.5, tokens ×74.2
Security scan: clean · 2026-10-24 · 9 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Burde vi have et møde om den nye logo? Vi er 5 personer og det tager 30 minutter.”
“/cs-meeting-prep: Vi skal beslutte Q3 budgettet. 4 deltagere, 1 time, snitrate $100/t. Har vi en dagsorden?”
“Jeg har disse rå noter fra standup: 'Alice vil rette bugen fredag', 'Bob skal tjekke serveren', 'TODO: opdater docs'. Udtræk venligst handlingspunkter og marker eventuelle orphans.”
“Should we have a meeting to discuss the new logo? We have 5 people and it will take 30 minutes.”
“/cs-meeting-prep: We need to decide on the Q3 budget. 4 attendees, 1 hour, avg rate $100/hr. Do we have an agenda?”
“I have these raw notes from the standup: 'Alice will fix the bug by Friday', 'Bob needs to check the server', 'TODO: update docs'. Please extract the action items and flag any orphans.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

meeting-costagenda-builderaction-itemsdecision-gatetimeboxingproductivitynotes-parsingowner-assignment

Not for

Do not use this skill for designing recurring team rituals like sprint planning or retrospectives, which belong to project management skills. It is not for drafting general internal communications or email newsletters, which are handled by internal communications skills. It is also not for triaging personal brain dumps or to-do lists that are not derived from a shared meeting context.

Details

When it is the right choice

Use this skill when a user asks if a specific meeting is worth scheduling, wants to calculate the dollar cost of a meeting, needs to create a structured agenda with timeboxes and clear outcomes, or wants to convert raw meeting notes into a checklist of owned action items. It is specifically designed for individual meeting preparation and post-meeting follow-up, not for recurring team ceremonies.

The full recipe the assistant reads

Meetings — Cost Gate → Timeboxed Agenda → Owned Actions

Portability: Reasoning-led skill with 3 stdlib Python scripts. No external APIs, no LLM calls in scripts, nothing auto-sent. The scripts fix the discipline; the user runs the meeting.

What this does

Most meetings should be an email. This skill makes that testable: it prices a meeting in real dollars, refuses to let it exist without a decision + agenda + owner, builds a timeboxed decision-first agenda for the survivors, and afterwards turns raw notes into an owner + due-date checklist that flags every orphan. An ASYNC verdict is a win, not a failure.

Workflow — gate → agenda → run → extract

1. Gate. Before starting, ask one clarifying question if the decision to be made is unstated — the gate cannot run honestly without it. Then price it and apply the three checks. No decision → ASYNC (exit 2): draft a memo instead, stop here. Decision but missing agenda/owner → NOT-READY (exit 3), naming the gap. All present → MEET (exit 0) with total cost and a cost-per-minute line.

2. Agenda. Only for MEET. Every topic needs a desired outcome — empty outcomes are refused by name (exit 2). Decision topics (decide/choose/approve) sort before discuss/inform. Timeboxes plus the mandatory 5-minute closing "actions recap" slot must fit --length, or the overflow is refused with the exact overage (exit 3). Iterate — trim or split the named topic and re-run until it fits; the stop condition is exit 0 (or the meeting goes async). Output includes a pre-read line.

3. Run. The user runs the meeting from the printed agenda. Hold the timeboxes; use the closing slot to read every action aloud with its owner and date.

4. Extract. Feed the raw notes to the extractor: checkboxes, ACTION:/TODO: lines, "@name will …" and "Name will … by date" patterns become a checklist grouped by owner, with ORPHAN (no owner) and NO-DUE flags plus summary counts. Assign every orphan before posting — the meeting is done when every action has an owner and a date; that completion check closes the loop.

# 1. Gate: should this meeting exist?
python scripts/meeting_cost_calculator.py --attendees 6 --minutes 60 \
  --avg-rate 90 --include-refocus --has-decision --has-agenda --has-owner

# 2. Agenda: timeboxed, decision-first, outcomes mandatory
python scripts/agenda_builder.py --length 45 \
  --topic "Q3 pricing:Decide usage-based vs seat-based:15:maria" \
  --topic "Launch risks:Discuss open launch blockers:15:sam"

# 4. Extract: raw notes -> owner + due-date checklist with ORPHAN/NO-DUE flags
python scripts/action_item_extractor.py --input notes.md

Scripts

Script Role
scripts/meeting_cost_calculator.py Dollars (attendees × minutes × rate, optional 23-min refocus overhead per attendee) + decision/agenda/owner gate → ASYNC / NOT-READY / MEET.
scripts/agenda_builder.py Timeboxed decision-first agenda; refuses empty outcomes and overflow; enforces pre-read line + 5-min closing actions-recap slot.
scripts/action_item_extractor.py Raw notes → owner-grouped markdown checklist with due dates, ORPHAN/NO-DUE flags, and summary counts.

References

Assets

Rules

  • Gate before agenda. Never build an agenda for a meeting that hasn't passed the gate.
  • No decision, no meeting. Status updates go async, every time.
  • No desired outcome, no agenda slot. The builder refuses; go get the outcome.
  • Every action item has an owner and a date — or it is not an action item. Flag, never drop.
  • Never auto-send. No invites, no emails, no messages. Output is text the user sends.

Distinct From (don't reach for the wrong skill)

  • project-management/ — team ceremonies, sprint cadence, Jira delivery flow. This gates one meeting at a time for the person calling it.
  • business-operations/internal-comms — org-level communication design. This never designs a comms program and never sends anything.
  • productivity/capture — triages a private brain-dump. This parses a shared meeting's notes.

Version: 1.0.0 Build pattern: Path-B discipline skill — meeting-science canon preserved + deterministic gate/agenda/extraction scripts added.

Files in this skill (10)
  • LICENSE
  • SKILL.md
  • assets/example_agenda.md
  • assets/meeting_gate_worksheet.md
  • references/action_item_discipline.md
  • references/agenda_discipline.md
  • references/meeting_cost_canon.md
  • scripts/action_item_extractor.py
  • scripts/agenda_builder.py
  • scripts/meeting_cost_calculator.py
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path productivity/meetings/skills/meetings, licence MIT. The upstream licence file ships inside the skill.