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/cli.md

View on GitHub
# Shell runtimes and managed CLIs

Covers the bundled shell runtimes plus `mcp__cherry-tools__cli_list`,
`mcp__cherry-tools__cli_search`, and `mcp__cherry-tools__cli_install`. The first group
executes local, project-scoped, or one-off work; the MCP tools install reusable CLIs in
Cherry's **isolated managed environment**.

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

## Choose by lifetime

Use the shortest-lived mechanism that fits:

| Need | Use |
| --- | --- |
| Run a JS/TS file | `bun <file>` |
| Install an existing JS project's dependencies / add a project dependency | `bun install` / `bun add <pkg>` in the project cwd |
| Run a one-off JavaScript package | `bun x <tool>` — only `bun` is bundled, not a `bunx` shim |
| Run a Python file | `uv run python <file>` |
| Run Python with a temporary dependency | `uv run --with <pkg> python <file>` |
| Run a one-off Python CLI | `uvx <tool>` |
| Search local files or contents | `rg` |
| Keep a CLI for later tasks, login, or durable configuration | the managed CLI workflow below |

Shell-capable general agents receive `bun`, `uv` / `uvx`, and `rg` on their execution
PATH. Prefer them over `node` / `npm` / `npx` / `pip`, which are not guaranteed to
exist. Do not assume a version or source: a Cherry-managed or system executable may
shadow the bundled fallback. If `command -v` cannot resolve one of these expected
commands, report an environment problem rather than pretending the command ran.

Keep dependency changes inside the current project. Global installs (`-g` /
`--global`, `uv tool install`, `pip install --user`) and direct `mise` mutations are
blocked because they leak state across agent sessions. Use `bun x` / `uvx` for one-off
tools and the managed workflow for anything persistent. Do not use `cli_install` for a
project library, and do not use an ephemeral runner for a CLI that needs login or reuse.

## Conditional availability

The built-in Assistant does not expose the `cli_*` tools. For every other role, the live
tool list is authoritative. If they're absent, you cannot install CLIs in this session —
say so; don't work around it. The bundled shell-runtime guidance above likewise applies
only when the session exposes a shell.

## Approval

`mcp__cherry-tools__cli_install` mutates durable state and is **approval-gated**. Call it
only once intent is clear; if approval is declined, stop and report — don't retry through
the shell.

## Workflow

Before installing anything:

1. **Probe the agent's effective PATH.** `mcp__cherry-tools__cli_list` reports only Cherry-managed
   binaries and does **not** see the system PATH — so a tool it calls "unavailable" may
   already resolve in the agent shell. Run `command -v <name>` (shell inspection is
   fine) to inspect the agent's effective PATH before installing a duplicate. This PATH
   includes Cherry-managed and bundled locations as well as the user's shell PATH; do
   not treat it as a pure system-only probe. Use `mcp__cherry-tools__cli_list` to see
   what Cherry already manages.
2. **`mcp__cherry-tools__cli_search`** — look up the exact `name`/`tool` recipe from the
   registry. Never guess the executable name or recipe.
3. **`mcp__cherry-tools__cli_install`** — install using the recipe from search (or one
   translated from trusted docs). Approval runs here.

## Don't reach around the managed environment

**Do not** substitute `npm install -g`, `pipx install`, `cargo install`, `brew install`,
or a manual download — those bypass Cherry's managed environment.
`mcp__cherry-tools__cli_install` accepts the same backends, so there's no capability you
gain by shelling out — you only lose Cherry's bookkeeping.

## Recovery

- **Invalid recipe / wrong name** → the tool returns an error; correct the recipe (re-run
  `cli_search`) rather than retrying blindly.
- **Approval declined** → stop and report; don't install via the shell.

## Example

> "I need `jq` available for later data-processing tasks."

`command -v jq` to check the agent's effective PATH → if absent, `mcp__cherry-tools__cli_list` to see
if Cherry already manages it → `mcp__cherry-tools__cli_search` "jq" for the exact recipe →
`mcp__cherry-tools__cli_install` with that recipe (approval runs). Never `brew install` /
`apt install` it yourself.
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