CherryHQ/cherry-studio / resources/skills/cherry-tool-guide
cherry-tool-guide
VerifiedCherry tool routing: bun, uv, rg, knowledge, memory, schedules, skills, MCP, web. Read before shell workarounds.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.6 KB |
| references/automation.md | markdown | 1.5 KB |
| references/autonomy.md | markdown | 6.7 KB |
| references/cli.md | markdown | 4.3 KB |
| references/documents.md | markdown | 3.1 KB |
| references/knowledge.md | markdown | 2.6 KB |
| references/mcp.md | markdown | 2.8 KB |
| references/memory.md | markdown | 2.1 KB |
| references/outputs.md | markdown | 1.5 KB |
| references/sessions.md | markdown | 5.4 KB |
| references/skills.md | markdown | 1.9 KB |
| references/web.md | markdown | 2.4 KB |
references/web.md
View on GitHub# Web research
Covers `mcp__cherry-tools__web_search` and `mcp__cherry-tools__web_fetch`, plus the hard
limits of Cherry's web built-ins.
Get exact argument shapes from the live tool schema — this reference gives routing,
sequencing, and limits only.
## Availability
Both tools are ordinarily present for general agents. If either is absent from your live
tool list, web capability is unavailable this session — say so; don't approximate it
with shell commands.
## Workflow
1. **`mcp__cherry-tools__web_search`** — fire one call per distinct question. When
researching several topics, issue the searches **in parallel** rather than
serializing them. Search returns snippets and URLs, not full pages.
2. **`mcp__cherry-tools__web_fetch`** — call only on the few URLs whose full text you
actually need. Fetching every result wastes context — be selective.
If a search returns nothing useful, **refine the query before fetching** anything. Don't
fetch low-relevance URLs just because they came back.
## Browser interaction
Load the bundled `cherry-browser` skill for the live Automation REPL. Bind with
`var tab = await browser.getTab()` and read the emitted documentation before acting.
It controls the current conversation’s visible browser pane when Browser control is
enabled, independently of Code Mode. See [automation.md](automation.md) for entry
points and recovery. History and login-data imports are managed in Browser settings.
The separate web search/fetch tools cannot:
- click, hover, or otherwise interact with a page,
- fill or submit forms,
- navigate authenticated / logged-in pages,
- capture screenshots or render dynamic content.
If a task needs any of that and no separate browser-automation tool is exposed in your
session, **tell the user the interaction is unavailable** rather than approximating it
with shell commands or pretending a fetch achieved it.
## Recovery
- **Empty / weak results** → refine the query, try different terms, or widen scope
before giving up. Don't fetch noise.
- **Tool error result** → read the returned message and correct the call; don't silently
retry identical arguments.
## Web vs. the user's own documents
If the answer should come from the user's private documents, this is the wrong domain —
use the knowledge tools instead (see [knowledge.md](knowledge.md)). Only fall back to
web search for a *knowledge* miss when the user is fine with public sources, and say
that's what you did.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| 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: 195k | Updated | Claude CodeCodex | Verified | Install |
| 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: 195k | Updated | Claude CodeCodex | Verified | Install |