Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cherryhq/cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance.
Passed 11 of 16 test cases with the skill, and 6 of 16 without it.
and 6 more in the full report
7 fixed8 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before editing any code to fix a bug in Cherry Studio, what is the very first step of the required development loop?
| Checked | Without skill | With skill |
|---|---|---|
| Requires stating the requested behavior and the proving evidence before modifying code. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill for ongoing work in the current checkout. Do not use it to check
out or report on PRs; use cherry-pr-test for that workflow.
Before reading or controlling Electron UI, read
Electron Instance Management and use its
persistent policy.
That reference is the only authority for instance discovery, instance.json,
CDP target selection, launching, replacement, shutdown, and troubleshooting.
Do not reproduce those procedures here or substitute generic Electron app
control.
Inspect the real window at the relevant size and theme for UI work. Check both renderer and main-process evidence for renderer failures.
Restart only for a non-reloadable layer, crash, unreliable runtime state, or
startup profiling. Use the reference's exact-instance replacement procedure,
refresh instance.json, and keep the replacement running.
Run the narrowest relevant validation and follow current user and repository instructions for lint, formatting, and tests.
test cases passed, vs 6 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.