Collects resolved questions and practical solutions in a project FAQ, checking for duplicates before adding or updating entries. It also searches saved keywords when new questions arrive, so relevant answers can be reused.
将成功解决的用户问题收录到 FAQ 知识库。问题解决后自动判断是否收录。也可以在用户说"收录到 FAQ"、"记录这个问题"、"add to FAQ"时手动触发。
Review the instructions the agent will receive before you install.
收录标准: 通用性高、有明确方案、配置/操作类、非直觉问题。不收录: 纯个人环境问题、已有相同条目、未解决问题。
文件: <project_root>/.cherry-assistant/faq.md（目录不存在则 mkdir -p .cherry-assistant 创建）
条目格式（追加到末尾）:
### Q: [通用化问题表述]
**A:** [简洁方案]
[分步骤操作]
- **关键词**: [逗号分隔]
- **相关文件/Issue**: [路径或#编号]
- **版本**: vX.X.X | **收录日期**: YYYY-MM-DD
---
流程: 问题解决→判断收录标准→读FAQ查重→无重复则通用化后追加→有相似但更好则更新
搜索匹配: 用户提问时先读FAQ关键词匹配→命中直接给答案→未命中走正常诊断
与 Issue Reporter 协作: 先收录FAQ(记录方案)→如果是Bug再提Issue→FAQ记关联Issue编号
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.
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.
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.