force-parent — Claude Code skill: what it does, how to install
force-parent pins the thread you are in to one model through Weave Router, while subagents keep their own routing. Useful when a single task needs a different model.
Apache-2.0 ★ 5,622 updated 2026-10-29
npx skills add weave-os/router --skill force-parent -a claude-codeWhat force-parent does
Call the skill as $force-parent <model-id>[:effort]. The pin covers the invoking thread only, so child threads stay on the routing policy they normally get.
One script, scripts/emit.sh, does the work. The skill runs it with the absolute path of its own directory and hands over the model, plus the optional :effort suffix, as a single quoted argument. Leave the model out and the skill asks which one to pin. The script prints a /force-parent directive with a leading space; the router picks that up from the exec output and lets the turn continue.
The router has to be a build that knows force-parent. Without its acknowledgment the pin did not happen, whatever the script printed. A parent pin outranks a conversation-wide $force-model; $force-model puts the broad pin back and $unforce-model clears whichever mode is active. Compaction that rewrites the thread's first user message gives the thread a new identity, so reapply the pin there.
What it helps with
- pin one thread to another model without touching the rest
- override a conversation-wide
$force-modelfor a single task - pass an effort suffix along with the model id
- get back to normal routing after trying a model
- reapply the pin once compaction changes the thread
Example prompts for the agent
- Run
$force-parent <model-id>to pin this thread to that model - Pin this thread with
$force-parent, and ask me which model if I left it out - Clear the pin on this thread and go back to the usual routing
How to install force-parent
1Skills CLI (Vercel)
npx skills add weave-os/router --skill force-parent -a claude-code2Manually: put the files in place
~/.claude/skills/force-parent/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/force-parent/
1Skills CLI (Vercel)
npx skills add weave-os/router --skill force-parent -a codex2Manually: put the files in place
.agents/skills/force-parent/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add weave-os/router --skill force-parent -a cursor2Manually: put the files in place
.cursor/skills/force-parent/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install weave-os/router install/codex-skills/force-parent2Manually: put the files in place
.github/skills/force-parent/SKILL.md1Skills CLI (Vercel)
npx skills add weave-os/router --skill force-parent -a gemini-cli2Platform CLI
gemini skills install https://github.com/weave-os/router --path install/codex-skills/force-parentManually: put the files in place
.devin/skills/force-parent/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about force-parent
How do I install force-parent in Claude Code?
Run npx skills add weave-os/router --skill force-parent -a claude-code. The skill ends up at ~/.claude/skills/force-parent/SKILL.md.
What does force-parent do?
It pins the parent thread that called it to a model through Weave Router. Subagents stay on their normal routing.
Does it need a particular router version?
Yes. The router must support the force-parent directive, and the pin counts only once the router acknowledges it.
Source text
SKILL.md · Apache-2.0
--- name: force-parent description: "Pin the current parent thread to a model through the Weave Router while subagents route automatically." --- <!-- weave-router managed force-parent skill --> When the user requests `$force-parent <model-id>[:effort]`, run this skill's `scripts/emit.sh` using the absolute path of this skill directory. Pass the model and optional effort as one quoted argument. If no model was supplied, ask which model to pin. The script prints a leading-space `/force-parent` directive. The Weave Router reads that exec output and pins only the invoking thread, then continues this turn. Run it once, do not repeat its output as a user message, and report the router's response. The directive requires a router version supporting `force-parent`; do not claim success without its acknowledgment. `$force-parent` replaces any conversation-wide `$force-model` pin. Children keep their normal routing policy. `$force-model` restores conversation-wide pinning; `$unforce-model` clears either mode. Model aliases and `:effort` suffixes follow `$force-model` syntax. A compaction that changes the thread's first user message changes its identity; reapply the pin in that thread.
© weave-os · Apache-2.0 · weave-os/router