Conciseness

"This file is a router. It carries only the global rules and the intent → tool → reference table" — every section is non-obvious policy (mutation boundaries, approval gating, error protocol) with zero padding and no explanation of concepts Claude already knows. Lean and efficient; every token earns its place.

Actionability

The routing table gives fully qualified tool names with concrete sequences ("`mcp__cherry-tools__kb_list` → `kb_search` → `kb_read`", "`command -v` check → `cli_list` → `cli_search` → `cli_install`", "run JS/TS with `bun <file>`"), and the body explicitly justifies not restating argument shapes ("the live tool schema in your session is the authoritative source"). Covers the common routing cases concretely; not a 4, which would require gaps in the executable guidance.

Workflow Clarity

Explicit checkpoints ("Check availability first", "resolve IDs first; needs approval") plus a feedback loop for errors ("read the message and correct the call; don't silently retry the same arguments", declined approval → "stop and report — never re-attempt the mutation through a different route") and a diagnostic section distinguishing absent tools from missing dependencies. Matches the explicit-validation-and-recovery anchor; mutation operations are gated, so the destructive-operation cap does not apply.

Progressive Disclosure

A clear overview with a routing table pointing to exactly one reference per intent; all ten linked files (web.md, knowledge.md, documents.md, memory.md, autonomy.md, sessions.md, outputs.md, cli.md, skills.md, mcp.md) exist in references/ and cross-link only laterally — one level deep, well-signaled, easy navigation. Matches the clear-overview-with-one-level-references anchor.

Specificity

Lists multiple specific concrete actions with exact commands — "run JS/TS with `bun <file>`", "one-off JS tools with `bun x`", "run Python with `uv run [--with <pkg>] python`", "one-off Python CLIs with `uvx`", "search with `rg`" — plus comprehensive coverage of every routed capability domain (web/browser, knowledge, memory, schedules/notifications, IM, image generation, CLI, skills, MCP registration). Not a 4: no notable coverage gaps.

Completeness

Explicitly answers both: what — "Cherry Studio first-party tool and bundled-shell routing for general agents" — and when — "Load this guide before changing project dependencies, … reading or converting local Office/PDF files, … or using Cherry-owned … capabilities—even if the user names no tool." Concrete trigger phrases with an explicit load condition.

Trigger Term Quality

Good natural keywords ("dependencies", "Office/PDF files", "Agent Sessions", "schedules/notifications", "image generation") but coverage is not comprehensive: common user phrasings like "search the web", "remind me", or "chat channels" are absent, and several triggers are internal jargon ("Cherry-owned", "bundled-shell routing", "ephemeral or reusable"). Clearly above the some-relevant-keywords anchor (3) but below the synonyms-and-extensions anchor (5).

Distinctiveness Conflict Risk

A clear niche ("Cherry Studio first-party tool and bundled-shell routing") with distinct, product-specific triggers ("MCP-server-registration capabilities", "Cherry-owned web/browser"); minimal risk of firing for the wrong skill. Not a 4: it is not merely "mostly distinct" — the scope is unambiguously owned by this one product surface.