agentleFS
Sign inStart free
KonHKonH/GlobalStrategy/.agents/skills/meeting-start/SKILL.md

meeting-start

Skill3 starsChanged 2 months agoMITView on GitHub

Start and own a multi-agent meeting under Docs/Meetings/ — join as owner, run the talking-turn queue, enforce the end condition, write summary.md. Use when asked to start/run/moderate the latest or a specific meeting.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow .claude/skills/meeting-start/SKILL.md exactly — it defines the owner's join/prepare/readiness-gate/open/turn-selection/end/summary …

    line 8
  2. Very specific:

    Run the wait script via scripts/meetings/wait_for_turn.ps1 (PowerShell) or scripts/meetings/wait_for_turn.sh (POSIX shell) — whichever this …

    line 14
  3. Very specific:

    Read the scripts' stdout, never their exit code.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting start (Codex)

Follow .claude/skills/meeting-start/SKILL.md exactly — it defines the owner's join/prepare/readiness-gate/open/turn-selection/end/summary procedure on top of the shared protocol in .claude/skills/meeting-join/SKILL.md, all tool-agnostic.

Codex-specific notes:

  • Run the wait script via scripts/meetings/wait_for_turn.ps1 (PowerShell) or scripts/meetings/wait_for_turn.sh (POSIX shell) — whichever this session's shell tool is.
  • Read the scripts' stdout, never their exit code. Every meeting script exits 0 and reports one prefix-tagged line (APPENDED: / TURN: / ACK: / MESSAGE: / MATCH: / ENDED: / KICKED: / TIMEOUT: / ERROR:) — see "Script output contract" in the canonical file. Do not append ; echo EXIT=$? or check $LASTEXITCODE.
  • Fill the joined line's Provider as Codex CLI; Model/Effort as whatever this session reports for itself, else unknown/default; work out Title per meeting-join's "Choosing a title" (owner exception).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free