Router On
weave-os/router
Route Codex through the Weave Router again (turn it back on).
Identify the user's true contract-work intent and route it to the correct scenario (C1-C9).
No licenceAuto-check passed
Install Contract Scenario Router
$ npx skills add infometa/workbuddyskills --skill contract-scenario-router -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills contract-scenario-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/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .claude/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .claude/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-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 infometa/workbuddyskills --skill contract-scenario-router -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills contract-scenario-router --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .agents/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .agents/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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 infometa/workbuddyskills --skill contract-scenario-router -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills contract-scenario-router --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .cursor/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .cursor/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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/infometa/workbuddyskills.git --path experts/contract-expert/skills/contract-scenario-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 infometa/workbuddyskills --skill contract-scenario-router -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills contract-scenario-router --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .gemini/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .gemini/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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 infometa/workbuddyskills contract-scenario-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 infometa/workbuddyskills --skill contract-scenario-router -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .github/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .github/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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 infometa/workbuddyskills --skill contract-scenario-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 infometa/workbuddyskills contract-scenario-router --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/contract-expert/skills/contract-scenario-router .opencode/skills/contract-scenario-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 "contract-scenario-router" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/contract-expert/skills/contract-scenario-router into .opencode/skills/contract-scenario-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contract-scenario-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.
Facts
- Skill name
contract-scenario-router- GitHub stars
- 348
- Token cost
- ~773 tokens
- SKILL.md length
- 142 words
- Files
- 2 (incl. references)
- Skills in repo
- 218
- Repo updated
- First seen
- Licence
- None found
At a glance
Identify the user's true contract-work intent and route it to the correct scenario (C1-C9).
- Works in 5 steps: 命中的合同场景（来自 C1–C9 场景决策表） → 该场景的核心应用目的、输出标准、典型工作流 → 是否需要交互采集：合同工作高度依赖交易细节，绝大多数场景需先采集；判断是否进入… → …
- SKILL.md covers 本 skill 解决什么, 工作步骤, 输出档位与交付形态 and 关键约束, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Contract Scenario Router is an agent skill from infometa/workbuddyskills. Identify the user's true contract-work intent and route it to the correct scenario (C1-C9). Use this skill FIRST for every contract request to determine scenario type, core objective, binding output standard, whether interactive intake is required, output weight tier, and the next skill in the chain — before any drafting, review or research happens.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/contract-scenario-table.md`).
The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
Example prompts
- “/contract-scenario-router”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 命中的合同场景（来自 C1–C9 场景决策表）
- 该场景的核心应用目的、输出标准、典型工作流
- 是否需要交互采集：合同工作高度依赖交易细节，绝大多数场景需先采集；判断是否进入 contract-intake
- 输出档位与交付形态：写明【输出档位】【交付物形态】【下一步技能】
- 是否有需向用户澄清的关键缺口
What it can do on your machine
Read from SKILL.md and the folder at commit 91b77ea. 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
Contract Scenario Router loads about 773 tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 142 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 142 words (~773 tokens).
- name
- contract-scenario-router
Files
SKILL.md and 1 other file (references) in experts/contract-expert/skills/contract-scenario-router of infometa/workbuddyskills.
- SKILL.md
- references/contract-scenario-table.md
Open the folder on GitHubat commit 91b77ea
Compare with similar skills
Contract Scenario 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 |
|---|---|---|---|---|---|---|
| Contract Scenario Router this skillinfometa/workbuddyskills | 348 | — | ~773 | Automated safety check: Pass | None | |
| Router Onweave-os/router | 5.6k | — | ~169 | Automated safety check: Pass | Apache-2.0 | |
| Acp Routeropenclaw/openclaw | 392k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Router Offweave-os/router | 5.6k | — | ~183 | Automated safety check: Pass | Apache-2.0 | |
| OmniRoute Routing CLIdiegosouzapw/OmniRoute | 75k | — | ~342 | Automated safety check: Pass | MIT | |
| Intent Routerangel291592/Intent-Router | 1k | — | ~7.9k | Automated safety check: Pass | MIT |
Similar skills
Acp Router
openclaw/openclaw
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either…
Router Off
weave-os/router
Route Codex to its default provider again (turn the Weave Router off).
OmniRoute Routing CLI
diegosouzapw/OmniRoute
Creates, switches, and inspects OmniRoute model-routing combos, plus a suggestion command with cost and latency constraints.
Intent Router
angel291592/Intent-Router
Turns an underspecified do-something request into a typed IntentSpec by looking things up, asking only necessary questions or halting, before any planning or coding.
OmniRoute Combo Routing
diegosouzapw/OmniRoute
Manages OmniRoute routing combos through its REST API: create and update combos, choose from 19 strategies, set fallback chains, test outcomes and read metrics.
More from infometa/workbuddyskills
All 218 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Questions about Contract Scenario Router
What does Contract Scenario Router do?
Identify the user's true contract-work intent and route it to the correct scenario (C1-C9). Contract Scenario Router is an agent skill from infometa/workbuddyskills. Identify the user's true contract-work intent and route it to the correct scenario (C1-C9).
How do I install Contract Scenario Router in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill contract-scenario-router -a claude-code`. Or copy the skill folder (experts/contract-expert/skills/contract-scenario-router in infometa/workbuddyskills) into .claude/skills/contract-scenario-router in your project. Claude Code loads it when a task matches its description.
How do I install Contract Scenario Router in Codex?
Run `npx skills add infometa/workbuddyskills --skill contract-scenario-router -a codex`. Or copy the skill folder (experts/contract-expert/skills/contract-scenario-router in infometa/workbuddyskills) into .agents/skills/contract-scenario-router in your project. Codex loads it when a task matches its description.
Can I use Contract Scenario Router 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 infometa/workbuddyskills --skill contract-scenario-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/contract-scenario-router, .gemini/skills/contract-scenario-router, .github/skills/contract-scenario-router and .opencode/skills/contract-scenario-router in your project.
What does Contract Scenario Router need to run?
SKILL.md names no scripts, command-line tools or credentials: Contract Scenario Router is instructions for the agent only.
Does Contract Scenario Router 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 Contract Scenario Router 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 Contract Scenario Router use?
No licence was found for Contract Scenario Router or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Contract Scenario Router use?
About 773 tokens (SKILL.md is roughly 3.1k 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 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Contract Scenario Router?
Skills that share tags, products or a category with Contract Scenario Router: Router On (weave-os/router, 5.6k stars), Acp Router (openclaw/openclaw, 392k stars), Router Off (weave-os/router, 5.6k stars) and OmniRoute Routing CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contract Scenario Router?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 348 GitHub stars. The repository holds 218 skills in this directory. The repository was last updated on October 9, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.