design-team-meeting-structure

design-team-meeting-structure is a skill for Claude Code from jeffreytse/grimoire-core. It costs 66 tokens per session (2,362 once invoked), scanned A, original, MIT.

A guide for designing a team’s meeting types, schedules, purposes, and facilitation practices.

In plain words
What is it for?
Use it to decide which meetings a team needs, how often they should happen, and what each one must produce.
Why use it?
It helps stop meetings from becoming repetitive, poorly timed, or unrelated to the decisions and work they are meant to support.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 145 skills shipped together

Good fit Use it to decide which meetings a team needs, how often they should happen, and what each one must produce.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-team-meeting-structure
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-team-meeting-structure
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 145 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-team-meeting-structure

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-meeting-structure/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-meeting-structure)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-meeting-structure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-meeting-structure/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-team-meeting-structure

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-team-meeting-structure"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-team-meeting-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,362 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.02362
Opus 5 $0.00033 $0.01181
Sonnet 5 $0.00013 $0.00472
Haiku 4.5 $0.00007 $0.00236

Measured 8d ago against content hash f0807340fae9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

design-team-meeting-structure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/business/leadership/skills/design-team-meeting-structure/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Team Meeting Structure

Define the right meeting types, cadences, purposes, and facilitation practices for a team — so every meeting has a clear reason to exist, produces a clear output, and does not crowd out the focused work that creates value.

Why This Is Best Practice

Adopted by: Lencioni's "Death by Meeting" (2004) is the foundational text on meeting dysfunction, used in leadership training at hundreds of organizations; Steven Rogelberg — the world's leading meeting researcher, professor at UNC Charlotte — has published 90+ peer-reviewed studies on meeting effectiveness cited by the WSJ, NYT, and HBR; Amazon's six-pager meeting culture is documented in "Working Backwards" (Bryar & Carr, 2021) and studied widely as a model for reducing decision time; Bain & Company's "Time and Talent" research (2014, Michael Mankins) is the most-cited study of meeting time waste in large organizations Impact: Rogelberg's research (2019) found that US organizations waste $37 billion per year on unproductive meetings; Bain & Company (2014, 17 large organizations) found that a single weekly executive committee meeting consumed 300,000 hours per year of employee time across the prep and attendance cascade — most of which was not value-adding; Rogelberg's field research found that removing just one regular meeting from employees' calendars increased productivity by an average of 72 minutes per employee per day due to restored focused work time; his meeting load reduction experiments found 31% reduction in staff stress, no reduction in productivity Why best: The most common meeting design failure is a single recurring meeting that tries to serve multiple purposes simultaneously — operational check-in, strategic discussion, decision-making, and information sharing in one session; these conversations compete for time and produce none of them well; Lencioni's core insight is that different conversations require different emotional contexts (urgency vs. reflection vs. exploration) and mixing them degrades all of them

Read the full file on GitHub · 151 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 151 lines · 66 tokens per session scan A f0807340fae9

Subscribe to this mod's changes

design-team-meeting-structure is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 66 tokens to every session and 2,362 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.