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

View on GitHub
# Knowledge base

Covers `mcp__cherry-tools__kb_list`, `mcp__cherry-tools__kb_search`,
`mcp__cherry-tools__kb_read`, and `mcp__cherry-tools__kb_manage` — answering from, and
mutating, the user's own documents.

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

## Conditional availability

The `kb_*` tools appear **only when the agent has a knowledge base in scope** — a bound
base, or one the user picked for this turn. If they're absent, the agent has **no
documents in scope**: tell the user to attach or select a knowledge base. Do **not**
fall back to web search and imply the answer came from their documents.

## Read workflow

When the answer should come from the user's own documents, stay inside the knowledge
tools — do not substitute web search. Typical order:

1. **`mcp__cherry-tools__kb_list`** — enumerate the bases in scope, or outline one base
   to see its documents and their IDs.
2. **`mcp__cherry-tools__kb_search`** — semantic search across the scoped bases for the
   passages that answer the question.
3. **`mcp__cherry-tools__kb_read`** — read a specific document, or grep it for a
   pattern, once search has pointed you at it.

Answer with a citation to the document you used.

## Mutation workflow — `kb_manage`

`mcp__cherry-tools__kb_manage` mutates a base (add / delete / re-index content). It is
**approval-gated**, and **deletion is destructive**. So:

1. **Resolve the exact base/document IDs first** with `mcp__cherry-tools__kb_list` /
   `mcp__cherry-tools__kb_search`. Never guess an ID.
2. Call `mcp__cherry-tools__kb_manage` and let the approval prompt run. Call it only once
   the user's intent is clear.
3. **Never edit the underlying files directly** to achieve the same effect — that skips
   the re-indexing and bookkeeping `kb_manage` performs.

If approval is declined, stop and report — do not retry the mutation through the shell or
file edits.

## Recovery

- **Empty / weak search results** → refine the query, try another base, or widen scope
  before escalating. Only fall back to web search for a knowledge miss if the user is
  fine answering from public sources — and say that's what you did.
- **Tool error result** (bad ID, etc.) → read the message and correct the call; don't
  silently retry the same arguments.

## Example

> "What did our Q3 architecture doc say about the caching layer?"

`mcp__cherry-tools__kb_list` to confirm a base is in scope and find the doc →
`mcp__cherry-tools__kb_search` for "caching layer" → `mcp__cherry-tools__kb_read` the top
hit (or grep it) → answer with a citation. Do not web-search; this is private knowledge.
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