MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
用 meeting 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要…
Install Meeting Facilitate
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CronusL-1141/AI-company meeting-facilitate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/meeting-facilitate .claude/skills/meeting-facilitate && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .claude/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CronusL-1141/AI-company meeting-facilitate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugin/skills/meeting-facilitate .agents/skills/meeting-facilitate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .agents/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CronusL-1141/AI-company meeting-facilitate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugin/skills/meeting-facilitate .cursor/skills/meeting-facilitate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .cursor/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CronusL-1141/AI-company.git --path plugin/skills/meeting-facilitate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CronusL-1141/AI-company meeting-facilitate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugin/skills/meeting-facilitate .gemini/skills/meeting-facilitate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .gemini/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CronusL-1141/AI-company meeting-facilitateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugin/skills/meeting-facilitate .github/skills/meeting-facilitate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .github/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CronusL-1141/AI-company meeting-facilitate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CronusL-1141/AI-company.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugin/skills/meeting-facilitate .opencode/skills/meeting-facilitate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "meeting-facilitate" agent skill from https://github.com/CronusL-1141/AI-company/tree/master/plugin/skills/meeting-facilitate into .opencode/skills/meeting-facilitate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-facilitate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
meeting-facilitate- GitHub stars
- 371
- Token cost
- ~1.3k tokens
- SKILL.md length
- 315 words
- Files
- 10
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
用 meeting 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要…
- Works in 7 steps: 选择会议模板 → 创建会议（拿到 dispatch_plan） → Spawn 每位参与者（最关键的一步） → …
- Agent Workflows work in your project
- SKILL.md covers 前置要求, 核心原则, 主持流程（7 步） and 端到端示例, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Meeting Facilitate is an agent skill from CronusL-1141/AI-company. 用 meeting 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要触发——那是直接做，或派一个审查 agent。
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files (for example `examples.md`, `templates/brainstorm.md` and `templates/council.md`).
It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: Multi-agent team operating system for Claude Code. 108 MCP tools, 40+ agent templates, 10 lifecycle hooks, 7 pipeline workflows. Persistent teams, structured meetings, task wall… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/meeting-facilitate”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3275b8a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Meeting Facilitate loads about 1.3k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 315 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from CronusL-1141/AI-company at commit 3275b8a, republished under its MIT licence (© CronusL-1141). 315 words, ~1,303 tokens.
Download SKILL.mdSave it as
.claude/skills/meeting-facilitate/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- meeting-facilitate
- description
- 用 meeting_* 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要触发——那是直接做，或派一个审查 agent。
Meeting Facilitate — 会议主持技能
本技能指导你（Leader 或具备主持职责的 Agent）端到端组织一场多 Agent 会议：选模板 → 创建会议 → spawn 真实参与者 → 签到 → 推进轮次 → 验证全员发言 → 结束并汇总。
前置要求
materials 与 context_files 里的路径要先备好：它们会被原样写进参与者 prompt 的必读清单，路径写错参与者只会读不到，不会报错。
核心原则
OS 不会自动 spawn 参与者 — meeting_create 只创建会议记录和 dispatch_plan，真正让参与者到场必须靠你亲自调用 Agent tool。光创建不 spawn = 没人到场 = 会议失败。
（发言署名见 Step 5，出勤校验见 Step 7。）
主持流程（7 步）
Step 1: 选择会议模板
根据会议目的对照下表选模板。详细模板说明见 templates/<name>.md（progressive disclosure）。
| 目的 | 推荐模板 | 轮数 | 为何 |
|---|---|---|---|
| 发散创意、产生新想法 | brainstorm | 4 | 独立发散 → 交叉启发 → 评估 → 汇总 |
| 多方案中做选择 | decision | 3 | 陈述 → 质询 → 收敛 |
| 评审代码 / PR / 交付物 | review | 3 | 陈述 → 独立评审 → 回应裁定 |
| 项目复盘、提取教训 | retrospective | 3 | 4Ls → 改进方向 → 承诺计划 |
| 每日进度同步 | standup | 1 | 三问：完成 / 计划 / 阻塞 |
| 决策有重大分歧或风险 | debate | 4 | 正方陈述 → 反方质疑 → 正方回应 → 裁决 |
| 开放议程、自由议题 | lean_coffee | 3 | 议题收集 → 投票 → 时间盒讨论 |
| 架构 / 方案多视角评审 | council | 3 | 专家视角 → 交叉质询 → 裁决 |
不确定？用 template="free"，OS 会根据 topic 关键词自动推荐。
Step 2: 创建会议（拿到 dispatch_plan）
必须使用结构化 participants（dict 列表），否则 dispatch_plan 里的 launch_call 会是空的，无法 ready-to-paste。
meeting_create(
topic="评审 v0.9 Prompt Registry 架构方案",
template="council", # Step 1 选的模板
team_id="repo-insight-arch", # 可省略，自动用活跃团队
team_name="repo-insight-arch", # 仅 OS 侧归属；不会写进 launch_call
participants=[
{
"name": "arch-lead",
"agent_template": "software-architect",
"role": "评估架构整体可行性与分层合理性",
"context_files": ["docs/v0.9-prompt-registry.md"],
"expected_output": "三段式：可行性 / 风险 / 建议",
},
# 其余参与者同型
],
rounds=[ # 可选，省略则用模板默认 rounds
{"topic": "立场陈述", "rule": "每人 3 段：评估视角 / 风险点 / 评分 1-5"},
],
materials=["docs/v0.9-prompt-registry.md"], # 全员必读
)从返回里记下 data.id（即 meeting_id）与 dispatch_plan，后续每一步都要用。
Step 3: Spawn 每位参与者（最关键的一步）
遍历 dispatch_plan，对每个 ready_to_paste=True 的项目调用 Agent tool，直接把 launch_call.params 整体作为 Agent tool 的参数：
for item in dispatch_plan:
if not item["ready_to_paste"]:
# 旧字符串格式：补结构化参数后重新 meeting_create
continue
Agent(**item["launch_call"]["params"])约束：
- 不要修改
prompt字段的内容 — OS 已经把 meeting_id、角色、必读材料、发言规则、meeting_send_message调用示例、完成后SendMessage("已发言")指令全部预设好了。手动改动反而会破坏闭环。 - 不要省略任何参与者 — 漏掉一个，Step 7 conclude 时就会被 attendance 校验拦下。
- 多个 spawn 可以并行发出（同一个消息里多个 Agent 调用），加快到场速度。
Step 4: 签到 — 等待全员发言
每位参与者发完 SendMessage("已完成发言") 后，调用：
meeting_attendance_check(meeting_id="mtg-abc123")pending 为空才进下一步。久不为空就先 meeting_read_messages 看他们到底发了什么，必要时对 pending 里的人重跑 Step 3。
⚠️ 返回的 timeout_in_seconds 是自 meeting_create 起的已过秒数（elapsed，不按轮重置），不是剩余时间——读成倒计时会让你在参与者早已退出后继续干等。
Step 5: 主持人发言（可选但推荐）
每轮开始或结束时，你可以以主持身份发言引导讨论：
meeting_send_message(
meeting_id="mtg-abc123",
agent_id="team-lead", # 你自己的 agent_id
agent_name="team-lead",
caller_agent_id="team-lead", # ⚠️ 必须与 agent_id 一致
round_number=1,
content="【主持】Round 1 已全员发言。共识：xxx；分歧：yyy。下一轮请聚焦 yyy 的解法。",
)⚠️ 代打警告： 以主持人身份发言时
agent_id与caller_agent_id都填你自己；不一致会被标impersonation=true并写meeting.impersonation事件（OS 只留痕，不会拦下）。永远不要代打他人发言——即使你只是想"帮忙补一段"。
Step 6: 推进下一轮
Round 1 全员发言后，进入 Round 2/3：
- 用 Step 5 的方式发主持人总结消息，明确进入下一轮和新轮次的发言要求
- 为新一轮重新 spawn 参与者（Agent 在完成 Round 1 后通常已退出，需重新唤起）
- 注意：
meeting_create生成的 prompt 默认是 Round 1 的，进入 Round 2 时在prompt里写明本轮编号与规则（description只是界面上的短标签，参与者读不到）
- 注意：
- 回到 Step 4 等待签到
Step 7: 结束会议
确认本轮 attendance_check 的 pending 为空后：
meeting_conclude(
meeting_id="mtg-abc123",
summary="共识：采用方案 A；待办：backend-arch 在 03-20 前出存储 schema；遗留风险：迁移期双写一致性需进一步验证。",
)conclude 默认校验出勤，400 的 detail 直接带 missing / spoken——照 missing 重新 spawn。别顺手 force=true：响应体自带的 hint 正是在教你用它，而用了就把没发言的人算成到场，只留下一条 meeting.forced_conclude_with_missing 事件。
结论必须上墙：summary 不会存成会议结论，也不进记忆。决策与行动项用 task_create 上墙，决策理由写进 task_memo_add(memo_type="decision")；只写在 summary 里等于这场会没留下决策记录。
端到端示例
三份完整端到端示例（council / debate / retrospective）见同目录 examples.md。
故障排查
meeting_attendance_check 的 pending 一直不减
先 meeting_read_messages(meeting_id=...) 看实际收到了什么——常见成因是发言者的 agent_name 与 expected_participants 对不上，而不是没发言。反复重 spawn 同一批人每次都白烧一轮。
Round 2 没人发言
Round 1 的 Agent 发完就退出了，Round 2 没人在场。见 Step 6：必须为新一轮重新 spawn，并说明本轮规则。
参考资料
- 模板详细说明：
templates/<name>.md（每个模板有"何时使用"和"反模式"章节，也是模板定义的唯一来源——src/aiteam/meeting/templates.py直接扫这个目录） - 完整调用示例：
examples.md - 相关 MCP 工具：
meeting_create/meeting_send_message/meeting_attendance_check/meeting_read_messages/meeting_conclude/meeting_template_list/meeting_list/meeting_update/debate_start/debate_code_review
© CronusL-1141, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files in plugin/skills/meeting-facilitate of CronusL-1141/AI-company.
- SKILL.md
- examples.md
- templates/brainstorm.md
- templates/council.md
- templates/debate.md
- templates/decision.md
- templates/lean_coffee.md
- templates/retrospective.md
- templates/review.md
- templates/standup.md
Open the folder on GitHubat commit 3275b8a
Compare with similar skills
Meeting Facilitate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Meeting Facilitate this skillCronusL-1141/AI-company | 371 | — | ~1.3k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| MemPalace Memory SearchMemPalace/mempalace | 60k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
More from CronusL-1141/AI-company
Os Channel
CronusL-1141/AI-company
CC 与 Codex（或两个各自独立运行的 CC 会话）之间用 OS 信道留言、查未读、被新消息唤醒。触发：要跨 harness 把结论交给对端、给对端留言或清未读、用户问"能不能让 Claude 和 Codex 互相沟通"。不适用于派子 agent 或 workflow 内部协作——那是 Agent 与 SendMessage，信道对同会话的子 agent 没有意义。
Os Release
CronusL-1141/AI-company
发布 AI Team OS 新版本的完整清单——预检、版本七处锁步、中英双语 CHANGELOG、双份 dist 构建、私有术语扫描、commit/tag、双仓推送、建 GitHub Release 条目并核对 latest 徽章、事后核对。当准备发版、补建漏掉的 Release 条目、或核对已发版本的线上状态时使用。
Os Workflow
CronusL-1141/AI-company
AI Team OS 里用 CC 内置 Workflow 的两件事：产出回写 OS 的标准模板（§1-2、§4），以及审查分级与派工档位纪律（§3/§3.1）。准备调用 Workflow 编排子 agent 时，或要判定一件事该按 L0/L1/L2 哪一档审查（含「这活要不要开 workflow」）时使用。
Meeting Participate
CronusL-1141/AI-company
你被派来参加 AI Team OS 会议（派你的 prompt 里带 meetingid），且要在 Round 2 及之后发言时用：怎么拿到自己的 agentid、怎么引用前人发言、roundnumber 怎么填。Round 1 的材料、发言规则与调用样例已经写在派你的 prompt 里，不必读本技能。
Related
Works with
Categories
Questions about Meeting Facilitate
What does Meeting Facilitate do?
用 meeting 工具跑一场多 Agent 会议：创建 → 亲自 spawn 参与者 → 推进轮次 → 签到 → conclude 并把决策上墙。仅当已决定以「开会」形式产出一个需上墙的决策时使用；典型场景是减法类提案：回退既有设计决策、砍工具删表、削弱或删除自动检查——这类结论必须留痕。加法（新增检查、加严判据、新增工具）不需要开会，写清理由直接做。用户只是让你评审代码、复盘、比较方案时不要…. Meeting Facilitate is an agent skill from CronusL-1141/AI-company.
When should I use Meeting Facilitate?
Meeting Facilitate fits situations like: agent Workflows work in your project.
How do I install Meeting Facilitate in Claude Code?
Run `npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a claude-code`. Or copy the skill folder (plugin/skills/meeting-facilitate in CronusL-1141/AI-company) into .claude/skills/meeting-facilitate in your project. Claude Code loads it when a task matches its description.
How do I install Meeting Facilitate in Codex?
Run `npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a codex`. Or copy the skill folder (plugin/skills/meeting-facilitate in CronusL-1141/AI-company) into .agents/skills/meeting-facilitate in your project. Codex loads it when a task matches its description.
Can I use Meeting Facilitate in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CronusL-1141/AI-company --skill meeting-facilitate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-facilitate, .gemini/skills/meeting-facilitate, .github/skills/meeting-facilitate and .opencode/skills/meeting-facilitate in your project.
What does Meeting Facilitate need to run?
SKILL.md names no scripts, command-line tools or credentials: Meeting Facilitate is instructions for the agent only.
Does Meeting Facilitate access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Meeting Facilitate safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Meeting Facilitate use?
Meeting Facilitate is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meeting Facilitate use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Meeting Facilitate?
Skills that share tags, products or a category with Meeting Facilitate: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and MemPalace Memory Search (MemPalace/mempalace, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meeting Facilitate?
CronusL-1141 (a GitHub user) maintains it in CronusL-1141/AI-company, which has 371 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.
Source: CronusL-1141/AI-company on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.