SuperSkill

Overview Schema Source Related Servers Discussions Admin

worktree_activate

Idempotent

Install the shared build-cache policy for this repo: policy file in .git/superskill, guarded post-checkout hook, and host session hooks. Call with confirm=false first to preview; only pass confirm=true after the user agrees.

Instructions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "confirm": "<confirm>"
    },
    "name": "worktree_activate"
  }
}

Input Schema

Name	Required	Description
`json`	No	Return JSON instead of text
`seed`	No	Seed cache manifests into worktrees (default true)
`hooks`	No	Install the guarded post-checkout hook (default true)
`hosts`	No	Host session-hook adapters to install (default: all detected)
`confirm`	Yes	true applies changes; false previews first (required)
`dry_run`	No	Preview only; write nothing
`install`	No	Run toolchain installs after activation (default false)
`workspace_path`	No	Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.0Oct 12, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare idempotentHint=true and destructiveHint=false, and the description reinforces the safety profile with 'Nothing is ever deleted' plus enumerates exactly what gets installed. The confirm-gating behavior adds useful context beyond annotations. It does not describe reversibility or how to undo, leaving a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its artifacts, then the critical workflow constraint, then the safety reassurance. Every sentence earns its place with no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter install tool with full schema coverage and no output schema, the description covers what is installed, the required confirm workflow, and safety. It could say more about default behaviors for hooks/hosts/seed and what preview output looks like, but nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all 8 parameters are already documented in the schema. The description only elaborates on confirm (preview vs apply), which the schema also covers; it does not add syntax or meaning for hooks, hosts, seed, or workspace_path. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb (Install) on a named resource (shared build-cache policy) and lists the concrete artifacts it touches: policy file in .git/superskill, guarded post-checkout hook, and host session hooks. This clearly separates it from siblings like worktree_status or worktree_audit, though it does not explicitly name the alternative install/uninstall siblings (worktree_apply, worktree_uninstall).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit workflow guidance: call with confirm=false first to preview, and only pass confirm=true after the user agrees. This defines the intended two-step invocation clearly. It lacks explicit when-not guidance or named alternatives, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.