MemPalace Setup and Operation
MemPalace/mempalace
Installs and configures MemPalace as a private local palace, a shared-brain hub or a client of an existing hub, including MCP registration and version-correct initialization.
Routes an agent inside Cherry Studio to the right first-party tool or bundled runtime for local scripts, documents, memory, schedules, knowledge bases, MCP servers and more.
Install Cherry Studio Tool Guide
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/skills/cherry-tool-guide .claude/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .claude/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/skills/cherry-tool-guide .agents/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .agents/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/skills/cherry-tool-guide .cursor/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .cursor/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CherryHQ/cherry-studio.git --path resources/skills/cherry-tool-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/skills/cherry-tool-guide .gemini/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .gemini/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/skills/cherry-tool-guide .github/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .github/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CherryHQ/cherry-studio cherry-tool-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/skills/cherry-tool-guide .opencode/skills/cherry-tool-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cherry-tool-guide" agent skill from https://github.com/CherryHQ/cherry-studio/tree/main/resources/skills/cherry-tool-guide into .opencode/skills/cherry-tool-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cherry-tool-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cherry-tool-guide- GitHub stars
- 52k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 796 words
- Files
- 11 (incl. references)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Routes an agent inside Cherry Studio to the right first-party tool or bundled runtime for local scripts, documents, memory, schedules, knowledge bases, MCP servers and more.
- Deciding whether a script should run with a bundled runtime instead of a global install
- SKILL.md covers Global rules, Routing table, When a tool isn't there and Out of scope
- Calls npm and git
- Reading or converting local Office or PDF files in a Cherry session
What it does
This file is a router, not a manual. Cherry Studio injects tools over four MCP servers, cherry-tools, agent-memory, skills and mcp-manager, and gives shell-capable agents bundled runtimes: bun for JavaScript and TypeScript, uv run or uvx for Python, and rg for search. A table maps each intent to a tool and to one of ten reference files covering autonomy, CLI, documents, knowledge, MCP, memory, outputs, sessions, skills and web.
The global rules say to check that a tool exists in the live tool list before relying on it, and to say so plainly if it is missing instead of faking a result. Knowledge bases, IM channels, schedules, managed CLIs, skills and registered MCP servers may be changed only through Cherry's tools, not by shelling out to npm install, git clone or crontab. Several tools are gated by the session's approval mode, and the live tool schema is the authority for arguments.
When your agent uses it
- Deciding whether a script should run with a bundled runtime instead of a global install
- Reading or converting local Office or PDF files in a Cherry session
- Registering an MCP server or installing a skill through Cherry's managed tools
- Creating schedules, notifications or persistent memory in Cherry
Example prompts
- “Run this TypeScript file with the bundled runtime and tell me the output.”
- “Install the filesystem MCP server through Cherry and confirm it is registered.”
- “Remember that I prefer concise answers, using Cherry's persistent memory.”
Requirements
- A Cherry Studio session with its first-party MCP tools
What it can do on your machine
Read from SKILL.md and the folder at commit c97c23c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cherry Studio Tool Guide loads about 1.9k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 209 tokens; SKILL.md has 796 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from CherryHQ/cherry-studio at commit c97c23c, republished under its AGPL-3.0 licence (© CherryHQ). 796 words, ~1,946 tokens.
Download SKILL.mdSave it as
.claude/skills/cherry-tool-guide/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.- name
- cherry-tool-guide
- description
- Cherry Studio first-party tool and bundled-shell routing for general agents. For straightforward local work in shell-capable sessions, run JS/TS with `bun <file>` and one-off JS tools with `bun x`; run Python with `uv run [--with <pkg>] python` and one-off Python CLIs with `uvx`; search with `rg`. Load this guide before changing project dependencies, deciding whether a tool should be ephemeral or reusable, reading or converting local Office/PDF files, coordinating or delegating across Agent Sessions, or using Cherry-owned web/browser, knowledge, persistent memory, schedules/notifications, IM channels, image generation, artifact reporting, managed CLI, skill, or MCP-server-registration capabilities—even if the user names no tool. Consult it before shell/file workarounds; live tool schemas are authoritative.
- version
- 1.6.0
Cherry Tool Guide
Cherry Studio injects first-party tools into your session over four MCP servers
(mcp__cherry-tools__*, mcp__agent-memory__*, mcp__skills__*, mcp__mcp-manager__*)
and gives shell-capable general agents bundled runtimes for local execution. The MCP
tools act on the running app — the user's knowledge bases, IM channels, schedules,
managed CLIs, skill library, and MCP server registry — through boundaries only Cherry
owns. Shell and file tools cannot reach those app boundaries correctly; use the bundled
runtimes only for the local execution cases routed below.
This file is a router. It carries only the global rules and the intent → tool → reference table. Each reference holds that domain's prerequisites, sequencing, conditional availability, output interpretation, recovery, and examples. Read the one reference the task needs (and any it cross-links to) before calling — don't work from this page alone.
Tool names here are fully qualified (mcp__server__tool); the exact names exposed in
your session are authoritative if they ever differ. This guide never restates argument
shapes — the live tool schema in your session is the authoritative source for
parameter names, enums, and required fields. Read it before every call.
Global rules
- Check availability first. Several tools are conditional (each reference says which). If a tool is not in your live tool list, its capability is unavailable in this session — say so honestly and stop; never pretend a call succeeded or fabricate a result.
- Don't reach around Cherry's mutation boundaries. Knowledge bases, IM channels,
schedules, managed CLIs, skills, and registered MCP servers are mutated only through
these tools. Do not shell out to
npm install,git clone,crontab, or hand-edit knowledge or MCP settings files to accomplish these — the tool does bookkeeping (registration, scoping, approval, sync) that a raw shell command skips. Shell is fine for inspection (e.g.command -vto probe PATH) — just not to perform the owned mutation. - Honor approval.
mcp__cherry-tools__kb_manage,mcp__cherry-tools__cli_install,mcp__cherry-tools__session_create,mcp__cherry-tools__session_send,mcp__skills__install_skill, andmcp__mcp-manager__install_mcp_serverare gated by the session's approval mode. Call them only once the user's intent is clear; if approval is declined, stop and report — do not retry the same effect through another route. - Intent still gates auto-approved effects. Memory writes, schedule changes, notifications, and agent/channel configuration may execute without an approval card. Do not call them merely because they are available; first make sure the user requested the effect or it is necessary to complete an already-approved task.
Show full SKILL.md (411 more words)Show less
Routing table
| User intent | Route to | Reference |
|---|---|---|
| Look up current/online facts, news, docs | mcp__cherry-tools__web_search → mcp__cherry-tools__web_fetch | web.md |
| Browser interaction (click, forms, screenshots) | mcp__browser__* when enabled; load cherry-browser | web.md |
| Answer from the user's own documents | mcp__cherry-tools__kb_list → mcp__cherry-tools__kb_search → mcp__cherry-tools__kb_read | knowledge.md |
| Add / delete / re-index knowledge | mcp__cherry-tools__kb_manage (resolve IDs first; needs approval) | knowledge.md |
| Read or convert a local document | mcp__cherry-tools__to_markdown → read the returned temporary Markdown path as needed | documents.md |
| Recall a past fact, correction, or preference | mcp__agent-memory__memory (search) before re-asking | memory.md |
| Save durable knowledge vs. a one-off event | mcp__agent-memory__memory (update vs. append) | memory.md |
| Schedule a recurring / future task | mcp__cherry-tools__cron (Cherry scheduling only) | autonomy.md |
| Proactively message the user or send a file | mcp__cherry-tools__notify (needs configured recipients) | autonomy.md |
| Inspect / connect / repair IM channels, rename agent | mcp__cherry-tools__config | autonomy.md |
| Find, create, message, or inspect work across Agent Sessions | mcp__cherry-tools__session_list / session_search / session_create / session_send / session_deliveries | sessions.md |
| Generate an image | mcp__cherry-tools__generate_image (needs a painting model) | outputs.md |
| Declare final deliverable file(s) | mcp__cherry-tools__report_artifacts | outputs.md |
| Run JS/TS or Python, invoke a one-off package, search local code/files | bundled bun, uv / uvx, or rg according to task lifetime | cli.md |
| Find / install a command-line tool | command -v check → mcp__cherry-tools__cli_list → mcp__cherry-tools__cli_search → mcp__cherry-tools__cli_install (approval) | cli.md |
| Find / install a new capability skill | mcp__skills__search_skills → mcp__skills__install_skill (approval) | skills.md |
| Register a new MCP server the user supplied | mcp__mcp-manager__install_mcp_server (approval; never invent the config) | mcp.md |
When a tool isn't there
Two different situations, don't confuse them:
- The tool is absent from your live list → the capability is unavailable this session (e.g. no knowledge base in scope, or CLI management disabled for a shell-less agent). Explain what's missing and what the user can do; don't work around it with shell/file tools. The reference for that domain says exactly when it can be absent.
- The tool is listed but reports a missing dependency → e.g.
mcp__cherry-tools__generate_imagewith no painting model. It stays listed and returns a note; relay the note and point the user at configuration — don't retry blindly or fake success.
On any tool error result (bad ID, unsupported channel/file, invalid recipe), read the message and correct the call; don't silently retry the same arguments. On declined approval, stop and report — never re-attempt the mutation through a different route.
Out of scope
Not covered here: SDK-native Read/Edit/Bash and orchestration tools; calling the
tools of a third-party (user-configured) MCP server — only registering one is in scope,
see mcp.md; the AI-SDK chat read_file attachment reader (a
chat-path tool, not exposed on this MCP surface); and the role-specific
mcp__assistant__* navigation/diagnosis tools, which belong to the Cherry Assistant and
its own guide.
© CherryHQ, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 10 other files (references) in resources/skills/cherry-tool-guide of CherryHQ/cherry-studio.
- SKILL.md
- references/autonomy.md
- references/cli.md
- references/documents.md
- references/knowledge.md
- references/mcp.md
- references/memory.md
- references/outputs.md
- references/sessions.md
- references/skills.md
- references/web.md
Open the folder on GitHubat commit c97c23c
Compare with similar skills
Cherry Studio Tool Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cherry Studio Tool Guide this skillCherryHQ/cherry-studio | 52k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| MemPalace Setup and OperationMemPalace/mempalace | 59k | — | ~2.2k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| agentmemory Setup and Diagnosticsrohitg00/agentmemory | 29k | — | ~1k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
Fastmcp Client CLI
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
agentmemory Setup and Diagnostics
rohitg00/agentmemory
Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.
Fastmcp
Tommy-yw/RunbookHermes
Build, test, inspect, install, and deploy MCP servers with FastMCP in Python.
More from CherryHQ/cherry-studio
All 30 skills in this repoOffice File Transform
CherryHQ/cherry-studio
Derives new files from a selected part of a spreadsheet, Word document, PDF or slide deck, such as a cell range, paragraph, page or slide, without ever modifying the source file.
GitHub Issue Creator
CherryHQ/cherry-studio
Creates GitHub issues for the current repository by choosing the matching issue template and following its format, with a permission check for engineering tasks.
Kimi Code Delegation
CherryHQ/cherry-studio
Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
Cherry Studio Regression Tests
CherryHQ/cherry-studio
Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.
Antigravity CLI Runner
CherryHQ/cherry-studio
Runs the Antigravity CLI headlessly with the agy command to analyze a repository or carry out a coding task, then checks its JSON result and the diff.
Related
Works with
Categories
Questions about Cherry Studio Tool Guide
What does Cherry Studio Tool Guide do?
Routes an agent inside Cherry Studio to the right first-party tool or bundled runtime for local scripts, documents, memory, schedules, knowledge bases, MCP servers and more. This file is a router, not a manual. Cherry Studio injects tools over four MCP servers, cherry-tools, agent-memory, skills and mcp-manager, and gives shell-capable agents bundled runtimes: bun for JavaScript and TypeScript, uv run or uvx for Python, and rg for search.
When should I use Cherry Studio Tool Guide?
Cherry Studio Tool Guide fits situations like: deciding whether a script should run with a bundled runtime instead of a global install; reading or converting local Office or PDF files in a Cherry session; registering an MCP server or installing a skill through Cherry's managed tools; creating schedules, notifications or persistent memory in Cherry.
How do I install Cherry Studio Tool Guide in Claude Code?
Run `npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a claude-code`. Or copy the skill folder (resources/skills/cherry-tool-guide in CherryHQ/cherry-studio) into .claude/skills/cherry-tool-guide in your project. Claude Code loads it when a task matches its description.
How do I install Cherry Studio Tool Guide in Codex?
Run `npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a codex`. Or copy the skill folder (resources/skills/cherry-tool-guide in CherryHQ/cherry-studio) into .agents/skills/cherry-tool-guide in your project. Codex loads it when a task matches its description.
Can I use Cherry Studio Tool Guide in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CherryHQ/cherry-studio --skill cherry-tool-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cherry-tool-guide, .gemini/skills/cherry-tool-guide, .github/skills/cherry-tool-guide and .opencode/skills/cherry-tool-guide in your project.
What does Cherry Studio Tool Guide need to run?
Going by SKILL.md and its folder, Cherry Studio Tool Guide needs the command-line tools its instructions call (npm and git). Our summary lists: A Cherry Studio session with its first-party MCP tools.
Does Cherry Studio Tool Guide access the network?
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Cherry Studio Tool Guide safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cherry Studio Tool Guide use?
Cherry Studio Tool Guide is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cherry Studio Tool Guide use?
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.1k tokens, read only when the agent opens those files.
What are the alternatives to Cherry Studio Tool Guide?
Skills that share tags, products or a category with Cherry Studio Tool Guide: MemPalace Setup and Operation (MemPalace/mempalace, 59k stars), MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cherry Studio Tool Guide?
CherryHQ (a GitHub organization) maintains it in CherryHQ/cherry-studio, which has 52,431 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 8, 2026.
Source: CherryHQ/cherry-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.