cherry-electron-dev
Develop, fix, profile, and test PRs in a tracked Cherry Studio Electron instance. Use for implementation, UI and interaction work, runtime debugging, DevTools inspection, performance analysis, and interactive PR verification with a test report.
Install / Use
npx skills add CherryHQ/cherry-studio --skill cherry-electron-devInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of cherry-electron-dev
cherry-electron-dev scores 87/100 on our quality scale, 1637th of 2,780 Automation skills we index.
Its SKILL.md is 2.9 KB long, split into 5 sections and no code examples: a solid amount of guidance for an agent.
With 53,498 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 2 days ago, so cherry-electron-dev is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
cherry-electron-dev compared with similar skills
All 4 of these similar skills score higher than cherry-electron-dev; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cherry-electron-dev (this skill)by CherryHQ | 87 | 53.5k | 2d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install cherry-electron-dev?
- Run
npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev. The install tabs above show the steps for each supported agent. - Which AI agents does cherry-electron-dev work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is cherry-electron-dev safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is cherry-electron-dev still maintained?
- The repository was last updated 2 days ago, so cherry-electron-dev is actively maintained.
Skill content
View source on GitHubname: cherry-electron-dev description: Develop, 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 cherry-pr-test for that workflow.
Required runtime 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.
Development loop
- State the requested behavior and the evidence that will prove it.
- Read the relevant code and nearby README files.
- Verify and reuse the tracked instance through the runtime reference.
- Reproduce or inspect the current behavior before editing when practical.
- Capture the smallest useful evidence: UI state, DOM, console/network output, main-process logs, persisted state, or performance metrics.
- Trace the responsible code path and make only the requested change.
- Keep Electron running. Use HMR for renderer changes and verify in the same window.
- Repeat the same scenario and compare before/after evidence.
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.
Performance and DevTools
For lag, jank, high CPU, memory growth, leaks, slow startup, or explicit DevTools use, read Performance Debugging.
Store temporary logs, screenshots, and profiles under
.context/cherry-electron-dev/. Compare a quiet baseline with the same bounded
scenario before and after a fix. Detach profiling sessions afterward; do not
close the CDP browser, page, or Electron process.
Handoff
Leave reused user-owned and healthy agent-launched instances running after the instruction. Stop one only when the user asks, a required restart is part of the task, or the instance is unhealthy and blocks progress.
Report the verified PID, whether it remains running, CDP port, tracking file, evidence paths, reproduction, and verification.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
