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

View on GitHub
# Persistent memory

Use server `agent-memory`, tool `memory` for memory that survives across sessions and
workspaces for the same agent. Resolve its callable name from the live session using
the guide's naming rule.

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

## Availability

Ordinarily mounted unless disabled; it may be deferred on some runtimes. Before
claiming absence, check current tools and the discovery your session actually offers,
following the guide's shared availability procedure. If discovery returns nothing,
re-check tools already available and earlier successful discovery: the tool may
already be loaded. Tool discovery is separate from the memory tool's own `search`
action, which queries the journal.

## Intent gate

Memory writes may execute **without an approval card**. Don't write merely because the
tool is available — only when the user asked you to remember something, or a durable
fact is genuinely worth persisting for future sessions.

## Three actions

- **`search`** — query the journal of past events/notes. **Search here before re-asking
  the user** something they may have already told you (a correction, a preference, prior
  context). Note: `search` covers the appended journal, **not** the durable fact file.
- **`append`** — log a one-time event, completed task, or session note to the journal.
- **`update`** — overwrite the durable fact file with long-lived knowledge and decisions.

## Choosing `update` vs. `append`

Decide by longevity — *"Will this still matter in six months?"*

- Durable preferences, standing decisions, corrections to how you should work, and
  reusable tool-usage lessons → **`update`**.
- A thing that just happened → **`append`**.

**`update` overwrites the whole fact file.** Preserve existing durable content when you
rewrite it — add to it, don't clobber it. Read/recall the current durable content first
if you're unsure what it holds.

## Recovery

- **Tool error result** → read the message and correct the call; don't silently retry
  the same arguments.
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