Skip to content

CherryHQ/cherry-studio / resources/skills/cherry-tool-guide

cherry-tool-guide

Verified

Cherry tool routing: bun, uv, rg, knowledge, memory, schedules, skills, MCP, web. Read before shell workarounds.

FileKindSize
SKILL.mdskill md8.6 KB
references/automation.mdmarkdown1.5 KB
references/autonomy.mdmarkdown6.7 KB
references/cli.mdmarkdown4.3 KB
references/documents.mdmarkdown3.1 KB
references/knowledge.mdmarkdown2.6 KB
references/mcp.mdmarkdown2.8 KB
references/memory.mdmarkdown2.1 KB
references/outputs.mdmarkdown1.5 KB
references/sessions.mdmarkdown5.4 KB
references/skills.mdmarkdown1.9 KB
references/web.mdmarkdown2.4 KB

references/mcp.md

View on GitHub
# MCP servers

Covers `mcp__mcp-manager__install_mcp_server` — registering a new MCP server in Cherry
and binding it to the current agent.

Get exact argument shapes from the live tool schema — this reference gives routing,
sequencing, and safety only.

## Availability

Present for agents that compose with the user's environment. Absent for sealed built-in
agents (Cherry Support), where registering servers is not available this session.

## Approval

`mcp__mcp-manager__install_mcp_server` mutates durable state and is **approval-gated**.
For a `stdio` server the config you pass *is* a local command line: `command` + `args`
launch a real process on the user's machine with the `env` you supply. Install only once
the user has signaled intent; if approval is declined, stop and report — don't register
the server by editing settings files or shelling out.

## Never invent a config

Unlike a skill's opaque `install_source`, here **you author the whole config** — so a
hallucinated package name or endpoint becomes a real command or a real request. Install
only a config the user pasted, linked, or explicitly confirmed. If you are working from
a server's documentation, show the user the exact config you are about to register and
get confirmation first. Never guess a `command`, an `args` package name, or a `baseUrl`.

`env` and `headers` typically carry API keys. Take them from the user; never fabricate a
placeholder and never echo a secret back in full.

## Workflow

1. **Get the config from the user** — `stdio` (local process) needs `command`; `sse` and
   `streamableHttp` (remote) need `baseUrl`. `name` is required for all three.
2. **Confirm, then call** with `activate` omitted. The server is registered **inactive
   and untrusted**, bound to this agent, for the user to enable in Settings → MCP.
3. **Only if the user explicitly asks to turn it on now**, pass `activate: true` — that
   marks it active and trusted and starts it, so its tools appear on the next tool
   re-list without a restart.

Report which of the two happened. A registered-but-inactive server runs nothing yet;
telling the user their tools are live when they are not sends them debugging a
non-problem.

## Recovery

- **Tool error result** (missing `command`/`baseUrl`, rejected field, duplicate name) →
  read the message and correct that field; don't retry the same arguments, and don't
  fall back to editing MCP settings by hand.
- **Approval declined** → stop and report; don't register through another route.

## Example

> "Add the GitHub MCP server, here's my token: ghp_…"

Confirm the config you'll register (`npx -y @modelcontextprotocol/server-github`, token
in `env`), then call `mcp__mcp-manager__install_mcp_server` without `activate`. Tell the
user it's registered and where to enable it — unless they asked you to enable it now, in
which case pass `activate: true` and say it's live.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall