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.
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
$ npx skills add parcadei/Continuous-Claude-v3 --skill workflow-router -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install parcadei/Continuous-Claude-v3 workflow-router --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/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/workflow-router .claude/skills/workflow-router && 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 "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .claude/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-routerType 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 parcadei/Continuous-Claude-v3 --skill workflow-router -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install parcadei/Continuous-Claude-v3 workflow-router --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/workflow-router .agents/skills/workflow-router && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .agents/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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 parcadei/Continuous-Claude-v3 --skill workflow-router -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install parcadei/Continuous-Claude-v3 workflow-router --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/workflow-router .cursor/skills/workflow-router && 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 "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .cursor/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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/parcadei/Continuous-Claude-v3.git --path .claude/skills/workflow-router--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 parcadei/Continuous-Claude-v3 --skill workflow-router -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install parcadei/Continuous-Claude-v3 workflow-router --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/workflow-router .gemini/skills/workflow-router && 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 "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .gemini/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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 parcadei/Continuous-Claude-v3 workflow-routerInstalls 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 parcadei/Continuous-Claude-v3 --skill workflow-router -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/workflow-router .github/skills/workflow-router && 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 "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .github/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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 parcadei/Continuous-Claude-v3 --skill workflow-router -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install parcadei/Continuous-Claude-v3 workflow-router --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/workflow-router .opencode/skills/workflow-router && 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 "workflow-router" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/workflow-router into .opencode/skills/workflow-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-router", 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.
workflow-routerGoal-based workflow orchestration - routes tasks to specialist agents based on user goals
Workflow Router is an agent skill from parcadei/Continuous-Claude-v3. Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
Its SKILL.md is about 1.5k 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. The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d07ff4b. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Workflow Router loads about 1.5k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 414 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.
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.
The full file from parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 414 words, ~1,491 tokens.
.claude/skills/workflow-router/SKILL.md (or your agent's skills folder).You are a goal-based workflow orchestrator. Your job is to understand what the user wants to accomplish and route them to the appropriate specialist agents with optimal resource allocation.
Use this skill when:
First, determine the user's primary goal. Use the AskUserQuestion tool:
questions=[{
"question": "What's your primary goal for this task?",
"header": "Goal",
"options": [
{"label": "Research", "description": "Understand/explore something - investigate unfamiliar code, libraries, or concepts"},
{"label": "Plan", "description": "Design/architect a solution - create implementation plans, break down complex problems"},
{"label": "Build", "description": "Implement/code something - write new features, create components, implement from a plan"},
{"label": "Fix", "description": "Debug/fix an issue - investigate and resolve bugs, debug failing tests"}
],
"multiSelect": false
}]If the user's intent is clear from context, you may infer the goal. Otherwise, ask explicitly using the tool above.
Before proceeding, check for existing plans:
ls thoughts/shared/plans/*.md 2>/dev/nullIf plans exist:
Determine how many agents to use. Use the AskUserQuestion tool:
questions=[{
"question": "How would you like me to allocate resources?",
"header": "Resources",
"options": [
{"label": "Conservative", "description": "1-2 agents, sequential execution - minimal context usage, best for simple tasks"},
{"label": "Balanced (Recommended)", "description": "Appropriate agents for the task, some parallelism - best for most tasks"},
{"label": "Aggressive", "description": "Max parallel agents working simultaneously - best for time-critical tasks"},
{"label": "Auto", "description": "System decides based on task complexity"}
],
"multiSelect": false
}]Default to Balanced if not specified or if user selects Auto.
Route to the appropriate specialist based on goal:
| Goal | Primary Agent | Alias | Description |
|---|---|---|---|
| Research | oracle | Librarian | Comprehensive research using MCP tools (nia, perplexity, repoprompt, firecrawl) |
| Plan | plan-agent | Oracle | Create implementation plans with phased approach |
| Build | kraken | Kraken | Implementation agent - handles coding tasks via Task tool |
| Fix | debug-agent | Sentinel | Investigate issues using codebase exploration and logs |
Fix workflow special case: For Fix goals, first spawn debug-agent (Sentinel) to investigate. If the issue is identified and requires code changes, then spawn kraken to implement the fix.
Before executing, show a summary and confirm using the AskUserQuestion tool:
First, display the execution summary:
## Execution Summary
**Goal:** [Research/Plan/Build/Fix]
**Resource Allocation:** [Conservative/Balanced/Aggressive]
**Agent(s) to spawn:** [agent names]
**What will happen:**
- [Brief description of what the agent(s) will do]
- [Expected output/deliverable]Then use the AskUserQuestion tool for confirmation:
questions=[{
"question": "Ready to proceed with this workflow?",
"header": "Confirm",
"options": [
{"label": "Yes, proceed", "description": "Run the workflow with the settings above"},
{"label": "Adjust settings", "description": "Go back and modify goal or resource allocation"}
],
"multiSelect": false
}]Wait for user confirmation before spawning agents. If user selects "Adjust settings", return to the relevant step.
Task(
subagent_type="oracle",
prompt="""
Research: [topic]
Scope: [what to investigate]
Output: Create a handoff with findings at thoughts/handoffs/<session>/
"""
)Task(
subagent_type="plan-agent",
prompt="""
Create implementation plan for: [feature/task]
Context: [relevant context]
Output: Save plan to thoughts/shared/plans/
"""
)If plan exists: Run pre-mortem before implementation:
/premortem deep <plan-path>This identifies risks and blocks if HIGH severity issues found. User can accept, mitigate, or research solutions.
After premortem passes:
Task(
subagent_type="kraken",
prompt="""
Implement: [task]
Plan location: [if applicable]
Tests: Run tests after implementation
"""
)# Step 1: Investigate
Task(
subagent_type="debug-agent",
prompt="""
Investigate: [issue description]
Symptoms: [what's failing]
Output: Diagnosis and recommended fix
"""
)
# Step 2: If fix identified, spawn kraken
Task(
subagent_type="kraken",
prompt="""
Fix: [issue based on Sentinel's diagnosis]
"""
)/premortem deep on the plan to catch risks early© parcadei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/workflow-router of parcadei/Continuous-Claude-v3.
Open the folder on GitHubat commit d07ff4b
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.
Workflow Router 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 |
|---|---|---|---|---|---|---|
| Workflow Router this skillparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
parcadei/Continuous-Claude-v3
Full 5-layer analysis of a specific function. An agent skill from parcadei/Continuous-Claude-v3.
parcadei/Continuous-Claude-v3
Transform session learnings into permanent capabilities (skills, rules, agents).
parcadei/Continuous-Claude-v3
Problem-solving strategies for gradient methods in optimization
parcadei/Continuous-Claude-v3
Systematic hook debugging workflow. An agent skill from parcadei/Continuous-Claude-v3.
parcadei/Continuous-Claude-v3
Unified math capabilities - computation, solving, and explanation.
parcadei/Continuous-Claude-v3
Routes problems to appropriate mathematical frameworks using expert heuristics
Categories
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals. Workflow Router is an agent skill from parcadei/Continuous-Claude-v3.
Workflow Router fits situations like: agent Workflows work in your project.
Run `npx skills add parcadei/Continuous-Claude-v3 --skill workflow-router -a claude-code`. Or copy the skill folder (.claude/skills/workflow-router in parcadei/Continuous-Claude-v3) into .claude/skills/workflow-router in your project. Claude Code loads it when a task matches its description.
Run `npx skills add parcadei/Continuous-Claude-v3 --skill workflow-router -a codex`. Or copy the skill folder (.claude/skills/workflow-router in parcadei/Continuous-Claude-v3) into .agents/skills/workflow-router in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add parcadei/Continuous-Claude-v3 --skill workflow-router -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-router, .gemini/skills/workflow-router, .github/skills/workflow-router and .opencode/skills/workflow-router in your project.
SKILL.md names no scripts, command-line tools or credentials: Workflow Router is instructions for the agent only.
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.
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.
Workflow Router is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Workflow Router: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,940 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.
Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.