Mmcp.market

cherry-studio-feedback skill

by CherryHQ·CherryHQ/cherry-studio·52k stars·AGPL-3.0

Use when Cherry Studio 用户希望报告、提交或整理 BUG、UI/UX 问题或功能建议,但未明确要求创建 GitHub Issue。

A100/100content scan

Is the cherry-studio-feedback skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the cherry-studio-feedback skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git /tmp/cherry-studio
mkdir -p ~/.claude/skills
cp -r /tmp/cherry-studio/resources/builtin-agents/cherry-assistant/.claude/skills/cherry-studio-feedback ~/.claude/skills/cherry-studio-feedback
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Cherry Studio Feedback

将当前 Support 对话整理成简洁、用户可编辑的问题描述,再把草稿交给用户审阅。Support 只准备草稿;诊断选择、知晓确认和最终提交都由用户完成。

准备草稿

  1. 复用对话中已知的实际结果、期望结果、复现步骤和影响,整理为一段简洁的问题描述。仅追问会实质改变描述的缺失信息。
  2. 仅在用户批准且问题确实需要诊断信息时调用 mcpassistantdiagnose。用户拒绝、工具失败或不需要诊断时,仍使用现有内容继续准备草稿。
  3. 仅在 Cherry Studio 内有实时交互用户时,调用完全限定的草稿工具。渠道或其他 headless 会话不得调用,直接执行第 5 步:
mcp__assistant__prepare_diagnostic_report({ description })
  1. 工具成功后,告诉用户点击消息内的“审阅诊断报告”按钮,在共享弹窗中检查并编辑描述。
  2. 渠道/headless 会话、工具不可用或失败时,不得循环重试模型或工具。让用户从 Cherry Studio 的帮助或设置打开“问题反馈”入口中的“提交诊断报告”,并手动填写问题描述。

用户拥有提交权

preparediagnosticreport 只持久化并返回草稿结果:不会打开弹窗、勾选知晓确认或上传。必须由用户亲自:

  • 点击“审阅诊断报告”。
  • 选择要包含的诊断数据。
  • 勾选知晓确认。
  • 审阅后提交。

禁止事项

  • 不得调用 lark-cli。
  • 不得生成工作区反馈 ZIP。
  • 不得直接打开飞书或其他外部表单。
  • 不得代替用户勾选、上传或完成任何提交。
  • 不得声称已打开弹窗、已上传或已提交。

GitHub Issue

用户明确要求创建 GitHub Issue 时,立即转交 issue-reporter,不再执行本流程。

More skills from CherryHQ/cherry-studio

  • Acherry-assistant-guide从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。
  • Acherry-browserInteract with the user's visible Agent browser in Cherry Studio. Use for page navigation, authenticated websites, screenshots, forms, clicks, and browser debugging. Check live browser tools first; browser control requires the Browser setting and an available Agent pane.
  • Acherry-electron-devDevelop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
  • Acherry-pr-testTest Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
  • Acherry-regression-testRun Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.
  • Acherry-skill-marketplace当用户明确要求搜索、安装、查看、卸载或创建 Skill,或内置 Skill / 工具出现能力缺口、无法完成当前任务时触发。通过 `mcp__skills__search_skills` 搜索并用 `mcp__skills__install_skill` 安装;已安装 Skill 的查看和删除通过产品清单导航到 Skills UI;没有合适结果时调用内置 `skill-creator` 创建并验证自定义 Skill,再继续原任务。普通任务仍先尝试内置能力。
  • Acherry-tool-guideCherry 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.
  • Aclaude-automation-recommenderAnalyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
  • Acode-mate-antigravityRuns Antigravity CLI headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Antigravity CLI or compare its result with another coding agent.
  • Acode-mate-claude-codeRuns Claude Code non-interactively for code analysis and implementation tasks. Use when the user asks to delegate repository work to Claude Code or compare its result with another coding agent.
  • Acode-mate-codexRuns Codex CLI non-interactively for code analysis and implementation tasks. Use when the user asks to delegate repository work to Codex or obtain a second coding-agent result.
  • Acode-mate-deepseek-harnessRuns DeepSeek Harness headlessly for bounded repository tasks. Use when the user asks to delegate analysis or implementation to DeepSeek Harness.

All agent skills → · MCP servers