Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cherryhq/cherry-tool-guide
Cherry Studio first-party tool and bundled-shell routing for general agents. For straightforward local work in shell-capable sessions, run JS/TS with `bun <file>` and one-off JS tools with `bun x`; run Python with `uv run [--with <pkg>] python` and one-off Python CLIs with `uvx`; search with `rg`. Load this guide before changing project dependencies, deciding whether a tool should be ephemeral or reusable, reading or converting local Office/PDF files, or using Cherry-owned web/browser, knowledge
Passed 17 of 22 test cases with the skill, and 3 of 22 without it.
and 17 more in the full report
15 fixed3 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
The user requested a custom logo image for their project. What tool creates images, and what condition must be met for it to succeed?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies `mcp__cherry-tools__generate_image` for generating images. | Missed | Passed |
| States that a painting model must be configured for image generation. | Missed | Passed |
The instructions your model reads when the skill loads.
Cherry Studio injects first-party tools into your session over four MCP servers
(mcp__cherry-tools__*, mcp__agent-memory__*, mcp__skills__*, mcp__mcp-manager__*)
and gives shell-capable general agents bundled runtimes for local execution. The MCP
tools act on the running app — the user's knowledge bases, IM channels, schedules,
managed CLIs, skill library, and MCP server registry — through boundaries only Cherry
owns. Shell and file tools cannot reach those app boundaries correctly; use the bundled
runtimes only for the local execution cases routed below.
This file is a router. It carries only the global rules and the intent → tool → reference table. Each reference holds that domain's prerequisites, sequencing, conditional availability, output interpretation, recovery, and examples. Read the one reference the task needs (and any it cross-links to) before calling — don't work from this page alone.
Tool names here are fully qualified (mcp__server__tool); the exact names exposed in
your session are authoritative if they ever differ. This guide never restates argument
shapes — the live tool schema in your session is the authoritative source for
parameter names, enums, and required fields. Read it before every call.
npm install, git clone, crontab, or hand-edit
knowledge or MCP settings files to accomplish these — the tool does bookkeeping (registration, scoping, approval, sync)
that a raw shell command skips. Shell is fine for inspection (e.g. command -v to
probe PATH) — just not to perform the owned mutation.mcp__cherry-tools__kb_manage, mcp__cherry-tools__cli_install,
mcp__cherry-tools__session_create, mcp__cherry-tools__session_send,
mcp__skills__install_skill, and mcp__mcp-manager__install_mcp_server are gated by
the session's approval mode. Call them only once the user's intent is clear; if approval is
declined, stop and report — do not retry the same effect through another route.test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.