skillboardUpdated every 6 hours
skillboardDevelop, 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.
Cherry Studio Development Use this skill for ongoing work in the current checkout. Do not use it to check out or report on PRs; use for that workflow. Required runtime workflow Before reading or controlling Electron UI, read Electron Instance Management and use its policy. That reference is the only authority for instance discovery, , CDP target selection, launching, replacement, shutdown, and troubleshooting. Do not reproduce those procedures here or substitute generic Electron app control.…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/cherry-electron-dev · pinned to the source commit
git clone https://github.com/CherryHQ/cherry-studio.git
cd cherry-studio
git checkout 18c287b020ff95cc2a12fc389ea4748957fbaf49
mkdir -p ".claude/skills/cherry-electron-dev"
cp -r ".agents/skills/cherry-electron-dev" ".claude/skills/cherry-electron-dev"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 18c287b020ff. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.