Plan Down
VCnoC/Claude-Code-Zen-mcp-Skill-Work
Method clarity-driven planning workflow using zen-mcp tools (chat, planner, consensus).
Monitored single-subtask execution workflow. An agent skill from RoboClaw-Robotics/RoboClaw.
Install Monitored Subtask Execution
$ npx skills add RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RoboClaw-Robotics/RoboClaw monitored-subtask-execution --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/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/monitored-subtask-execution .claude/skills/monitored-subtask-execution && 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 "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .claude/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-executionType 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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RoboClaw-Robotics/RoboClaw monitored-subtask-execution --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/monitored-subtask-execution .agents/skills/monitored-subtask-execution && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .agents/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RoboClaw-Robotics/RoboClaw monitored-subtask-execution --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/monitored-subtask-execution .cursor/skills/monitored-subtask-execution && 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 "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .cursor/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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/RoboClaw-Robotics/RoboClaw.git --path skills/monitored-subtask-execution--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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RoboClaw-Robotics/RoboClaw monitored-subtask-execution --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/monitored-subtask-execution .gemini/skills/monitored-subtask-execution && 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 "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .gemini/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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 RoboClaw-Robotics/RoboClaw monitored-subtask-executionInstalls 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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/monitored-subtask-execution .github/skills/monitored-subtask-execution && 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 "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .github/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RoboClaw-Robotics/RoboClaw monitored-subtask-execution --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RoboClaw-Robotics/RoboClaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/monitored-subtask-execution .opencode/skills/monitored-subtask-execution && 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 "monitored-subtask-execution" agent skill from https://github.com/RoboClaw-Robotics/RoboClaw/tree/main/skills/monitored-subtask-execution into .opencode/skills/monitored-subtask-execution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitored-subtask-execution", 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
monitored-subtask-execution- GitHub stars
- 166
- Token cost
- ~1.2k tokens
- SKILL.md length
- 542 words
- Files
- 3 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- None found
At a glance
Monitored single-subtask execution workflow. An agent skill from RoboClaw-Robotics/RoboClaw.
- Works in 4 steps: Safety + Preconditions → Start (set params + auto-start) → Monitor (poll get_status with a timeout) → …
- A larger workflow needs one repeatable
- SKILL.md covers Overview, Inputs (provide per run), Tools (MCP) and Quick Actions, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Monitored Subtask Execution is an agent skill from RoboClaw-Robotics/RoboClaw. Monitored single-subtask execution workflow. Use the repository MCP service corobotmcpserver to start, monitor, stop, and reset one prompt-driven robot rollout through the sequence setevaluateparams, poll getstatus, then stop/reset. Use this skill whenever a larger workflow needs one repeatable, safe execution unit with timeout handling and deterministic cleanup.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/mcp-tool-map.md`).
It sits in Agent Workflows, covering Task breakdown and MCP servers. It works with Model Context Protocol.
When your agent uses it
- A larger workflow needs one repeatable
- Safe execution unit with timeout handling and deterministic cleanup
Example prompts
- “/monitored-subtask-execution”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Safety + Preconditions
- Start (set params + auto-start)
- Monitor (poll get_status with a timeout)
- Handle success / failure deterministically
What it can do on your machine
Read from SKILL.md and the folder at commit 5238184. 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 (its code samples are json).
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
Monitored Subtask Execution loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 542 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 542 words (~1,247 tokens).
“Use a standardized procedure to call corobot_mcp_server MCP tools and execute one monitored robot subtask. In practice this is one CoRobot PolicyTask run defined by a prompt, an optional policy host/port, and an optional step_interval, followed by deterministic monitoring and…”
- name
- monitored-subtask-execution
Files
SKILL.md and 2 other files (references) in skills/monitored-subtask-execution of RoboClaw-Robotics/RoboClaw.
- SKILL.md
- agents/openai.yaml
- references/mcp-tool-map.md
Open the folder on GitHubat commit 5238184
Compare with similar skills
Monitored Subtask Execution 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 |
|---|---|---|---|---|---|---|
| Monitored Subtask Execution this skillRoboClaw-Robotics/RoboClaw | 166 | — | ~1.2k | Automated safety check: Pass | None | |
| Plan DownVCnoC/Claude-Code-Zen-mcp-Skill-Work | 116 | — | ~9.4k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 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 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
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.
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.
Fastmcp Client CLI
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
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.
More from RoboClaw-Robotics/RoboClaw
Long Horizon Execution
RoboClaw-Robotics/RoboClaw
Long-horizon robot task execution workflow for multi-step manipulation tasks.
Eap Data Collection
RoboClaw-Robotics/RoboClaw
EAP data collection workflow for prompt-driven robotic rollouts.
Related
Works with
Categories
Questions about Monitored Subtask Execution
What does Monitored Subtask Execution do?
Monitored single-subtask execution workflow. An agent skill from RoboClaw-Robotics/RoboClaw. Monitored Subtask Execution is an agent skill from RoboClaw-Robotics/RoboClaw. Monitored single-subtask execution workflow.
When should I use Monitored Subtask Execution?
Monitored Subtask Execution fits situations like: A larger workflow needs one repeatable; safe execution unit with timeout handling and deterministic cleanup.
How do I install Monitored Subtask Execution in Claude Code?
Run `npx skills add RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a claude-code`. Or copy the skill folder (skills/monitored-subtask-execution in RoboClaw-Robotics/RoboClaw) into .claude/skills/monitored-subtask-execution in your project. Claude Code loads it when a task matches its description.
How do I install Monitored Subtask Execution in Codex?
Run `npx skills add RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a codex`. Or copy the skill folder (skills/monitored-subtask-execution in RoboClaw-Robotics/RoboClaw) into .agents/skills/monitored-subtask-execution in your project. Codex loads it when a task matches its description.
Can I use Monitored Subtask Execution 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 RoboClaw-Robotics/RoboClaw --skill monitored-subtask-execution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitored-subtask-execution, .gemini/skills/monitored-subtask-execution, .github/skills/monitored-subtask-execution and .opencode/skills/monitored-subtask-execution in your project.
What does Monitored Subtask Execution need to run?
SKILL.md names no scripts, command-line tools or credentials: Monitored Subtask Execution is instructions for the agent only.
Does Monitored Subtask Execution 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 Monitored Subtask Execution 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 Monitored Subtask Execution use?
No licence was found for Monitored Subtask Execution or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Monitored Subtask Execution use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 463 tokens, read only when the agent opens those files.
What are the alternatives to Monitored Subtask Execution?
Skills that share tags, products or a category with Monitored Subtask Execution: Plan Down (VCnoC/Claude-Code-Zen-mcp-Skill-Work, 116 stars), MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monitored Subtask Execution?
RoboClaw-Robotics (a GitHub user) maintains it in RoboClaw-Robotics/RoboClaw, which has 166 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on April 10, 2026.
Source: RoboClaw-Robotics/RoboClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.