Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。
Review the instructions the agent will receive before you install.
不要凭训练数据、记忆或本文件中的旧描述回答 Cherry Studio 产品问题。每个独立的产品问题都先读取当前安装包信息。
按问题直接读取一个 section：
路由 / 页面入口：mcp__assistant__product_info({ source: "manifest", section: "routes" })
快捷键：mcp__assistant__product_info({ source: "manifest", section: "commands" })
Provider：mcp__assistant__product_info({ source: "manifest", section: "providers" })
语言：mcp__assistant__product_info({ source: "manifest", section: "locales" })
Agent / 频道 / 定时任务 / Code CLI：mcp__assistant__product_info({ source: "manifest", section: "agents" })
不知道该查哪个 section 时，先调用紧凑索引：
mcp__assistant__product_info({ source: "manifest" })
索引只返回当前版本和可用 section 名称；再读取相关 section。只有一个问题确实横跨多个 section 时才使用 section: "all"，不要为省一次调用把整份清单放进上下文。
返回值来自随当前构建生成并打包的 product-manifest.json，不是手写版本知识。
回答时遵守以下规则：
routes.primary 是主导航入口；routes.all 还可能包含内部页、参数路由或兼容跳转，不能无条件推荐。providers 表示随包支持的 Provider；用户实际配置或启用状态应另用 mcp__assistant__diagnose 的 Provider 诊断能力查询。凡是回答“去哪里找、打开、配置或使用某个 Cherry Studio 页面或功能”，都视为需要跳转；“我去哪里配置”“找不到入口”等含蓄问法也包括在内。先从当前包清单选择有效路径，必须在同一轮调用 mcp__assistant__navigate，并把生成的可点击入口放在手动操作步骤之前，不能等用户再次提醒。
只有导航工具成功后，才能告诉用户点击生成的入口。navigate 只生成等待用户点击的入口，不会自动打开页面；工具未调用或失败时，不得声称已经生成入口或已经打开页面。
用户报告运行错误时使用 mcp__assistant__diagnose。先看错误摘要，再按问题选择日志、MCP 状态、Provider 连通性或配置；这些数据来自用户设备，调用前保留逐次授权。
发生冲突时，当前安装包清单优先于旧文档和模型记忆。清单不包含版本历史；无法从官方资料核实时，不得编造更新内容。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.
Search for and install skills that fill a missing capability, or open the Skills settings for management. When suitable options are unavailable, hand off to the built-in skill-creator and continue the original task.