Codex with ChatGPT Planning Loop
XiaoDuoYa/codex-with-chatgpt
Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.
Reference for the meetings-mcp tools — how a meeting runs turn by turn, who may call which tool, moderator and participant practice, and an example flow.
Install Meetings Guide
$ npx skills add OtoDock/oto-dock --skill meetings-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OtoDock/oto-dock meetings-guide --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/OtoDock/oto-dock.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .claude/skills/meetings-guide && 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 "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .claude/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guideType 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 OtoDock/oto-dock --skill meetings-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OtoDock/oto-dock meetings-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .agents/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .agents/skills/meetings-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .agents/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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 OtoDock/oto-dock --skill meetings-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OtoDock/oto-dock meetings-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .cursor/skills/meetings-guide && 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 "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .cursor/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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/OtoDock/oto-dock.git --path mcps/custom/meetings-mcp/skills/meetings-guide--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 OtoDock/oto-dock --skill meetings-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OtoDock/oto-dock meetings-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .gemini/skills/meetings-guide && 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 "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .gemini/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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 OtoDock/oto-dock meetings-guideInstalls 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 OtoDock/oto-dock --skill meetings-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .github/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .github/skills/meetings-guide && 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 "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .github/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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 OtoDock/oto-dock --skill meetings-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OtoDock/oto-dock meetings-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OtoDock/oto-dock.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/mcps/custom/meetings-mcp/skills/meetings-guide .opencode/skills/meetings-guide && 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 "meetings-guide" agent skill from https://github.com/OtoDock/oto-dock/tree/main/mcps/custom/meetings-mcp/skills/meetings-guide into .opencode/skills/meetings-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meetings-guide", 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
meetings-guide- GitHub stars
- 190
- Token cost
- ~949 tokens
- SKILL.md length
- 455 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Reference for the meetings-mcp tools — how a meeting runs turn by turn, who may call which tool, moderator and participant practice, and an example flow.
- Works in 6 steps: Call start_meeting(topic, agents) — you… → Use direct_to(agents=[...]) to address… → If you don't call direct_to, your… → …
- Tasks that involve MCP servers
- SKILL.md covers How meetings work, Tool guide, Best practices and Example flow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Meetings Guide is an agent skill from OtoDock/oto-dock. Reference for the meetings-mcp tools — how a meeting runs turn by turn, who may call which tool, moderator and participant practice, and an example flow. Load before starting or joining a multi-agent meeting.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers and Multi-agent orchestration. The repository describes itself as: The agentic company OS. The brains of your company, built on Claude Code and Codex, working on your Anthropic and OpenAI subscriptions.
When your agent uses it
- Tasks that involve MCP servers
- Tasks that involve Multi-agent orchestration
Example prompts
- “/meetings-guide”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Call start_meeting(topic, agents) — you become the moderator
- Use direct_to(agents=[...]) to address specific agents — they respond next (in parallel if multiple)
- If you don't call direct_to, your response broadcasts to all participants
- All responses are visible to everyone in the transcript, regardless of routing
- As moderator, call end_meeting to conclude — your response becomes the summary
- Any agent can call propose_conclude to suggest ending — you (moderator) decide
What it can do on your machine
Read from SKILL.md and the folder at commit 5308f5a. 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
Meetings Guide loads about 949 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 455 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 455 words (~949 tokens).
“The meetings card in your instructions carries the rules (when a meeting is right, who you can meet, the start_meeting rule, the do-nots). This guide is the reference behind them.”
- name
- meetings-guide
Files
Just SKILL.md in mcps/custom/meetings-mcp/skills/meetings-guide of OtoDock/oto-dock.
Open the folder on GitHubat commit 5308f5a
Compare with similar skills
Meetings Guide 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 |
|---|---|---|---|---|---|---|
| Meetings Guide this skillOtoDock/oto-dock | 190 | — | ~949 | Automated safety check: Pass | Custom licence | |
| Codex with ChatGPT Planning LoopXiaoDuoYa/codex-with-chatgpt | 7.1k | — | ~11k | Automated safety check: Notes | MIT | |
| Puppetmaster Agent Orchestrationprofessorpalmer/Puppetmaster | 467 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Agent Deck Sessionsartwist-polyakov/polyakov-claude-skills | 206 | — | ~965 | Automated safety check: Pass | MIT | |
| Ruflo Multi-Agent Orchestrationruvnet/ruflo | 74k | 1 repos | ~975 | Automated safety check: Pass | MIT | |
| Marm InitLyellr88/marm-memory | 418 | — | ~7.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Puppetmaster Agent Orchestration
professorpalmer/Puppetmaster
Operates and supervises Puppetmaster, a multi-agent orchestrator, through its MCP tools or CLI, picking the right verb for edits, reviews, audits and long-running jobs.
Agent Deck Sessions
artwist-polyakov/polyakov-claude-skills
Launches, monitors and collects results from child AI agent sessions with the agent-deck terminal session manager.
Ruflo Multi-Agent Orchestration
ruvnet/ruflo
Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.
Marm Init
Lyellr88/marm-memory
Guided MARM MCP setup. An agent skill from Lyellr88/marm-memory.
Hermes Mission Control
Th0rgal/sandboxed.sh
Teaches Hermes to monitor and steer long-running sandboxed.sh missions: spot where a model is stuck, switch backends or models between turns, and send targeted hints.
More from OtoDock/oto-dock
All 19 skills in this repoAgent Creation
OtoDock/oto-dock
How to author an agent template folder and install it as a new agent - folder layout, manifest fields, persona rules, shipped apps and checks, and the scaffold-validate-create flow.
Checks
OtoDock/oto-dock
How checks work on OtoDock — named units that judge an agent's work at the end of a turn (schema, script, handler and judge kinds), conditions on what the turn changed, rounds, where a check lives…
Image Search Usage
OtoDock/oto-dock
Search the web for images with filters and download them. An agent skill from OtoDock/oto-dock.
Subtitle Burning
OtoDock/oto-dock
Transcribe audio and burn styled subtitles into videos. An agent skill from OtoDock/oto-dock.
Triggers Guide
OtoDock/oto-dock
Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…
MCP Authoring
OtoDock/oto-dock
Author an MCP package for OtoDock: the manifest.json fields and their rules, the package layout, what the installer refuses or drops, credentials and instances, skills bundled with an MCP, and the…
Related
Categories
Questions about Meetings Guide
What does Meetings Guide do?
Reference for the meetings-mcp tools — how a meeting runs turn by turn, who may call which tool, moderator and participant practice, and an example flow. Meetings Guide is an agent skill from OtoDock/oto-dock. Reference for the meetings-mcp tools — how a meeting runs turn by turn, who may call which tool, moderator and participant practice, and an example flow.
When should I use Meetings Guide?
Meetings Guide fits situations like: tasks that involve MCP servers; tasks that involve Multi-agent orchestration.
How do I install Meetings Guide in Claude Code?
Run `npx skills add OtoDock/oto-dock --skill meetings-guide -a claude-code`. Or copy the skill folder (mcps/custom/meetings-mcp/skills/meetings-guide in OtoDock/oto-dock) into .claude/skills/meetings-guide in your project. Claude Code loads it when a task matches its description.
How do I install Meetings Guide in Codex?
Run `npx skills add OtoDock/oto-dock --skill meetings-guide -a codex`. Or copy the skill folder (mcps/custom/meetings-mcp/skills/meetings-guide in OtoDock/oto-dock) into .agents/skills/meetings-guide in your project. Codex loads it when a task matches its description.
Can I use Meetings Guide 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 OtoDock/oto-dock --skill meetings-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meetings-guide, .gemini/skills/meetings-guide, .github/skills/meetings-guide and .opencode/skills/meetings-guide in your project.
What does Meetings Guide need to run?
SKILL.md names no scripts, command-line tools or credentials: Meetings Guide is instructions for the agent only.
Does Meetings Guide 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 Meetings Guide 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 Meetings Guide use?
Meetings Guide has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Meetings Guide use?
About 949 tokens (SKILL.md is roughly 3.8k 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 Meetings Guide?
Skills that share tags, products or a category with Meetings Guide: Codex with ChatGPT Planning Loop (XiaoDuoYa/codex-with-chatgpt, 7.1k stars), Puppetmaster Agent Orchestration (professorpalmer/Puppetmaster, 467 stars), Agent Deck Sessions (artwist-polyakov/polyakov-claude-skills, 206 stars) and Ruflo Multi-Agent Orchestration (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meetings Guide?
OtoDock (a GitHub organization) maintains it in OtoDock/oto-dock, which has 190 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: OtoDock/oto-dock on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.