Is the Meeting Facilitate skill free?

Yes. The skill itself is free from CronusL-1141/AI-company. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Meeting Facilitate SkillProof Score?

6.4/10 — installs cleanly 4/5, triggers reliably 4/5, output vs. baseline 5/10, docs & honesty 3/5.

How do I install Meeting Facilitate?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Meeting Facilitate with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Meeting Facilitate

Runs multi-agent meetings — needs the 168-tool AI Team OS server behind it

by CronusL-1141 · CronusL-1141/AI-company

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 6.4/10
Tested: Jul 17, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 742d1b6

Copying this skill folder into ~/.claude/skills installs a playbook with nothing underneath it: every one of its seven steps calls meeting_create, meeting_attendance_check or meeting_conclude, which only exist inside the ai-team-os MCP server. Installed that server for real (168 tools, all 10 meeting_* among them), started its FastAPI backend, and the documented behaviour held up — meeting_create returned a dispatch_plan with ready-to-paste Agent params, and conclude was correctly rejected with HTTP 400 and missing:[a1,a2] until participants had spoken. Two documented details did not hold: the impersonation audit trail the skill warns about crashes with "'meeting.impersonation' is not a valid EventType", and the design doc it points you to does not exist in the repo. Most of its advice is also already delivered by the tools themselves, whose responses ship their own dispatch_instructions and attendance_check_command.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 4/5
Triggers reliably 4/5
Output vs. baseline 5/10
Docs & honesty 3/5

What Meeting Facilitate does

A facilitation playbook for multi-agent meetings on the AI Team OS platform: pick a template, create the meeting, spawn each participant as a real subagent, check attendance, then conclude with a summary. It is a plugin component, not a standalone skill — every step calls meeting_* MCP tools.

How to install Meeting Facilitate

git clone https://github.com/CronusL-1141/AI-company.git
mkdir -p ~/.claude/skills
cd AI-company && cp -r plugin/skills/meeting-facilitate ~/.claude/skills/meeting-facilitate
# NOTE: inert on its own. For a working setup use the plugin instead:
# claude plugin marketplace add CronusL-1141/AI-company && claude plugin install ai-team-os

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Meeting Facilitate

/meeting-facilitate Runs multi-agent meetings — needs the 168-tool AI Team OS server behind it

It also activates on plain-language prompts like these:

Spin up a council meeting with two participants and check who's spoken
Create a structured multi-agent meeting and conclude it once everyone's in
Run an attendance check before concluding this AI Team OS meeting

Frequently asked questions

Is the Meeting Facilitate skill free?: Yes. The skill itself is free from CronusL-1141/AI-company. SkillProof publishes the install command and an independent test verdict at no cost.
Does Meeting Facilitate work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 17, 2026. Verdict: Works with setup. Copying this skill folder into ~/.claude/skills installs a playbook with nothing underneath it: every one of its seven steps calls meeting_create, meeting_attendance_check or meeting_conclude, which only exist inside the ai-team-os MCP server. Installed that server for real (168 tools, all 10 meeting_* among them), started its FastAPI backend, and the documented behaviour held up — meeting_create returned a dispatch_plan with ready-to-paste Agent params, and conclude was correctly rejected with HTTP 400 and missing:[a1,a2] until participants had spoken. Two documented details did not hold: the impersonation audit trail the skill warns about crashes with "'meeting.impersonation' is not a valid EventType", and the design doc it points you to does not exist in the repo. Most of its advice is also already delivered by the tools themselves, whose responses ship their own dispatch_instructions and attendance_check_command.
What is the Meeting Facilitate SkillProof Score?: 6.4/10 — installs cleanly 4/5, triggers reliably 4/5, output vs. baseline 5/10, docs & honesty 3/5.
How do I install Meeting Facilitate?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Meeting Facilitate with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.