agenda-or-cancel
Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line agenda format (purpose, decisions sought, pre-reads), the…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Agenda Or Cancel Skill
The agenda isn't paperwork — it's the meeting's existence test. A meeting whose organizer can't write three lines (what this is for, what we'll decide, what to read first) is a meeting that hasn't earned its attendee-hours, and the kindest outcome is its cancellation or conversion to a message. This skill writes the agenda when one can be written, renders the cancel verdict when it can't, and scripts the graceful exits — because "no agenda, no meeting" only works as a norm when declining is socially cheap.
What This Skill Produces
- The three-line agenda — purpose (one sentence), decisions/outcomes sought (listed), pre-reads with time cost
- The verdict — happen / shorten / convert-to-async / cancel — from the agenda-writing attempt itself
- The scripts — the polite cancel, the convert-to-message, and the decline-without-agenda lines
- The norm rollout — how a team installs the rule without a compliance war
Required Inputs
Ask for these if not provided:
- The meeting's claimed purpose — what the organizer thinks it's for; the agenda attempt tests whether that survives writing down
- The attendee list and length — the cost side (people × time), which the purpose must justify
- What a good outcome looks like — a decision? alignment? information moved? If the outcome is "information moved," the convert-to-async branch is already winning
- The recurring-or-oneoff status — recurring meetings route to [standing-meeting-audit](../standing-meeting-audit/SKILL.md) for the deeper treatment
Framework: The Test Rules
- The agenda is three lines or the meeting is fiction: Purpose: why we're gathering, one sentence. Outcomes: the decisions or artifacts this meeting produces (verbs, not topics). Pre-reads: what to read and how long it takes. If line two can't list a decision or artifact, the meeting is a broadcast — and broadcasts are messages.
- The 24-hour rule: agenda ships with (or ≥24h before) the invite — attendees who can't prepare attend as audience, and audiences don't decide. Meetings that can't produce an agenda a day out aren't urgent; they're unformed.
- The verdict follows the attempt: agenda writes cleanly → happen (at the length the outcomes justify — most three-line agendas fit 25 minutes). Outcomes are all information-transfer → convert to a message/doc. Purpose exists but no decisions this week → shorten or skip this instance. Nothing survives writing down → cancel, with the script.
- Declining needs a cheap script: "Happy to join — could you share the agenda first so I can prep?" does the enforcement politely; the norm survives only if asking is routine, not confrontational. Organizer-side cancel: "Cancelling — the two items resolved async / aren't ready for decisions yet. Reconvening when [trigger]."
- Roll out as a gift, not a law: the team adopts "agenda-or-cancel" by the leader modeling it on their own meetings first (cancelling one publicly is worth ten policy emails), the three-line format pinned where invites happen, and the decline script blessed explicitly so juniors can use it upward.
Output Format
Agenda Test: [meeting]
The Three Lines
Purpose: … Outcomes: [decisions/artifacts, verbs] Pre-reads: [links + minutes]
The Verdict
[Happen ([N] min) / shorten / convert / cancel — with the reasoning from the attempt]
Scripts (as needed)
[The cancel · the convert-to-message · the agenda-first decline]
Rollout (for teams installing the norm)
[Leader models on own meetings · format pinned · decline script blessed downward and upward]
Quality Checks
- [ ] The outcomes line contains decisions or artifacts, not topic nouns
- [ ] Pre-reads carry their time cost
- [ ] The verdict came from the writing attempt, not from meeting-hating priors
- [ ] Every script is usable by the most junior attendee
- [ ] Recurring meetings were routed to the audit instead of one-off verdicts
Anti-Patterns
- [ ] Do not write topic agendas — "discuss roadmap" is a location, not a purpose
- [ ] Do not accept "we'll figure it out live" — that's the agenda test failing in real time, at full attendance
- [ ] Do not use the rule as a weapon — the verdict includes "happen"; meeting-zero is not the goal, meeting-earned is
- [ ] Do not ship the agenda at meeting-start — unprepped deciders are attendees
- [ ] Do not install the norm by decree — the leader's own cancelled meeting is the announcement
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
exports/openclaw/agenda-or-cancel/SKILL.md同一个仓库里的其他技能
同名技能的其他版本
有 3 个不同仓库或目录里都有叫 agenda-or-cancel 的技能。它们内容并不相同,别混用:
- mohitagw15856/pm-claude-skills — Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line
- mohitagw15856/pm-claude-skills — Enforce the simplest meeting rule that works — no agenda, no meeting — with the three-line