Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Meetings

ASecurity

Use when someone wants to decide whether a meeting is worth calling,

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentspythongobashapi

Works with

api

Security Analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill meetings --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Meetings?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Meetings
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-meetings/badge)](https://www.skillsdirectory.com/skills/aicodedecode-meetings)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: meetings
description: Use 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 owned action items — or says "should this be a meeting",
  "meeting prep", or "meeting actions". Runs a cost gate (ASYNC / NOT-READY
  / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist
  that flags every orphan.
argument-hint: '[the meeting to gate, or the notes to extract actions from]'
license: MIT
metadata:
  version: 1.0.0
  build_pattern: Path-B discipline skill — Rogelberg/HBR meeting-science canon + deterministic
    gate/agenda/extraction scripts
  distinct_from: project-management (team ceremonies + Jira delivery flow; this is
    personal meeting hygiene); business-operations/internal-comms (org-level communication
    design; this never auto-sends); productivity/capture (private brain-dump triage;
    this parses shared meeting notes)
---

# 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.

```bash
# 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

- [`references/meeting_cost_canon.md`](references/meeting_cost_canon.md) — the real cost of meetings and the should-this-exist gate (7 sources)
- [`references/agenda_discipline.md`](references/agenda_discipline.md) — agendas as questions, timeboxing, decision-first ordering, pre-reads (7 sources)
- [`references/action_item_discipline.md`](references/action_item_discipline.md) — why meetings without owned actions are theater (6 sources)

## Assets

- [`assets/example_agenda.md`](assets/example_agenda.md) — a full worked timeboxed agenda (gate verdict → ordered topics → closing recap)
- [`assets/meeting_gate_worksheet.md`](assets/meeting_gate_worksheet.md) — fillable should-this-be-a-meeting worksheet

## 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.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →