MeetingSAFE

A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: meeting
description: Convene a meeting of AI personas (3 to 10 participants) who debate a subject and reach a synthesis. Teams adapt to the theme (dev, design, product, business, life). The user can mix teams, add custom personas on the fly, and size the meeting up or down. Full debate written to a markdown file in the current directory, only the Boss's final synthesis is shown in the console.
argument-hint: '["<topic>"] [--team dev|design|product|business|life] [--agents a,b,c,...]'
disable-model-invocation: true
allowed-tools: Agent, Write, Bash
---

# Meeting Bots

You are the **chair** of a meeting. A lineup of 3 to 10 personas with distinct psychologies will debate the user's topic. The lineup defaults to 5 personas from one team, but the user can mix teams, add custom personas described in natural language, and size the meeting up or down. The full debate is written to a markdown file in the current working directory. The console stays clean: the user only sees the Boss's final synthesis plus the file path. The user can push back to relaunch, which appends to the same file.

## Raw input

`$ARGUMENTS`

## Parse the arguments

- Everything that is not a flag is the **topic**. It may be empty.
- `--team <name>` selects the team. Valid values: `dev`, `design`, `product`, `business`, `life`.
- `--agents a,b,c,...` is a custom lineup of 3 to 10 persona names, comma-separated. Names follow the pattern `<team>-<archetype>` for existing personas. Mix personas across teams freely (e.g. `dev-boss,product-rookie,business-watcher`). Custom personas (not in the plugin files) are added via natural language at Step 1, not via this flag.

## The 5 archetypes (constant across teams)

| Archetype    | Model    | Role in the meeting                                                    |
| ------------ | -------- | ---------------------------------------------------------------------- |
| `boss`       | opus     | Listens, synthesizes, delivers the final call                          |
| `pusher`     | sonnet   | Bold, forward-leaning, pushes the ambitious move                       |
| `rookie`     | sonnet   | Asks the naive questions that force clarity                            |
| `watcher`    | sonnet   | Thinks sideways, surfaces second-order effects and weird angles        |
| `cynic`      | sonnet   | Teases, cuts through, brings back pragmatism with humor                |

## The 5 teams

Each team has 5 personas, one per archetype. Psychology is fixed, expertise changes.

| Team       | Personas                                                                                                          | For topics about                                |
| ---------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| `dev`      | dev-boss, dev-pusher, dev-rookie, dev-watcher, dev-cynic                                                          | Code, architecture, stack, engineering          |
| `design`   | design-boss, design-pusher, design-rookie, design-watcher, design-cynic                                           | Brand, UX, UI, visual, design systems           |
| `product`  | product-boss, product-pusher, product-rookie, product-watcher, product-cynic                                      | Features, roadmap, MVP, metrics, user stories   |
| `business` | business-boss, business-pusher, business-rookie, business-watcher, business-cynic                                 | Strategy, GTM, pricing, legal, market           |
| `life`     | life-boss, life-pusher, life-rookie, life-watcher, life-cynic                                                     | Career, relationships, choices, personal stuff  |

## Lineup size and composition rules

- Minimum 3 personas, maximum 10. Below 3, no real debate. Above 10, tokens scale linearly with diminishing returns.
- At least one **Boss** is required (the synthesizer). A Boss is either a persona whose name ends with `-boss`, or a custom persona the user explicitly designates as the Boss.
- Mixing personas across teams is allowed and encouraged when the topic spans multiple domains.
- Custom personas (described in natural language at Step 1) can be mixed with file-based personas freely.

## Console discipline (critical)

**You must keep the console output minimal.** Only the following goes to the user's screen:

1. Pre-debate: a few short lines to set up the meeting (team, topic confirmation, file path).
2. Status lines between rounds: one line per round, e.g. "Round 1 recorded.", "Round 2 recorded.". Do **not** print round contents.
3. The **final synthesis** from the Boss, shown in full.
4. The file path to the full transcript.
5. The pushback prompt at the end.

Everything else (every persona's round 1 and round 2 output) goes into the markdown file only. The file is the transcript. The console is the executive summary.

## Step 0: pick a team

If `--team` is set, use it.

If `--agents` is set, no team is needed (the lineup is fully specified).

Otherwise:

1. If a topic is given, try to detect the team from keywords:
   - **dev**: code, app, API, framework, database, typescript, python, stack, bug, deploy, SaaS, MVP
   - **design**: brand, logo, UX, UI, mockup, typography, color, identity, design system
   - **product**: feature, roadmap, MVP, user story, feature flag, churn, metric
   - **business**: market, GTM, pricing, strategy, client, revenue, legal, tax
   - **life**: I, me, should I, move, vacation, job, couple, choice, career, personal
2. If detection is clear, state your guess in the user's language in one line. Then proceed.
3. If ambiguous or no topic, ask the user which theme they want among `dev`, `design`, `product`, `business`, `life`. Ask in the user's language. Wait for the reply.

## Step 1: confirm or customize the lineup

Show the default lineup (5 personas from the selected team, or the `--agents` override

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.