New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cherry Studio Electron Dev

by CherryHQ in CherryHQ/cherry-studio

Develops, debugs and profiles Cherry Studio in a tracked Electron instance, reusing a verified running instance and capturing before and after evidence for each change.

AGPL-3.0Auto-check passedDevelopment

Install Cherry Studio Electron Dev

skills CLI
$ npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CherryHQ/cherry-studio cherry-electron-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cherry-electron-dev .claude/skills/cherry-electron-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cherry-electron-dev
GitHub stars
52k
Token cost
~739 tokens
SKILL.md length
349 words
Files
3 (incl. references)
Skills in repo
30
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Develops, debugs and profiles Cherry Studio in a tracked Electron instance, reusing a verified running instance and capturing before and after evidence for each change.

  • Works in 8 steps: State the requested behavior and the… → Read the relevant code and nearby README… → Verify and reuse the tracked instance… → …
  • Implementing a UI or interaction change in Cherry Studio
  • SKILL.md covers Required runtime workflow, Development loop, Performance and DevTools and Handoff
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

For ongoing work in the current checkout, the agent first reads references/electron-instance.md and follows its persistent policy, which alone governs instance discovery, instance.json, CDP target selection, launching, replacement and shutdown. The development loop states the expected behavior and its proof, reads the relevant code, verifies the tracked instance, reproduces the current behavior, captures the smallest useful evidence such as DOM, console and network output, main-process logs or metrics, makes only the requested change and repeats the same scenario.

Electron stays running during the work, with HMR for renderer changes, and restarts are reserved for non-reloadable layers, crashes or startup profiling. Lag, jank, high CPU, memory growth, leaks and slow startup go to references/performance-debugging.md, with temporary logs, screenshots and profiles kept under .context/cherry-electron-dev and profiling sessions detached afterward. Checking out and reporting on PRs belongs to a different cherry-pr-test skill.

When your agent uses it

  • Implementing a UI or interaction change in Cherry Studio
  • Investigating lag, jank or high CPU in the running app
  • Checking for memory growth or leaks with the same scenario before and after a fix
  • Analyzing slow startup of the Electron app

Example prompts

  • “Fix the sidebar flicker in Cherry Studio and show me before and after evidence.”
  • “Profile CPU usage while I scroll a long chat and find the hot code path.”
  • “Check the running instance for memory growth over a repeated open and close scenario.”

Requirements

  • A Cherry Studio checkout that can launch Electron
  • A tracked instance with a CDP port, as described in references/electron-instance.md

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. State the requested behavior and the evidence that will prove it.
  2. Read the relevant code and nearby README files.
  3. Verify and reuse the tracked instance through the runtime reference.
  4. Reproduce or inspect the current behavior before editing when practical.
  5. Capture the smallest useful evidence: UI state, DOM, console/network output,
  6. Trace the responsible code path and make only the requested change.
  7. Keep Electron running. Use HMR for renderer changes and verify in the same
  8. Repeat the same scenario and compare before/after evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit dd0767e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cherry Studio Electron Dev loads about 739 tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 349 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~739
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CherryHQ/cherry-studio at commit dd0767e, republished under its AGPL-3.0 licence (© CherryHQ). 349 words, ~739 tokens.

Download SKILL.mdSave it as .claude/skills/cherry-electron-dev/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
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

  1. State the requested behavior and the evidence that will prove it.
  2. Read the relevant code and nearby README files.
  3. Verify and reuse the tracked instance through the runtime reference.
  4. Reproduce or inspect the current behavior before editing when practical.
  5. Capture the smallest useful evidence: UI state, DOM, console/network output, main-process logs, persisted state, or performance metrics.
  6. Trace the responsible code path and make only the requested change.
  7. Keep Electron running. Use HMR for renderer changes and verify in the same window.
  8. 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.

© CherryHQ, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/cherry-electron-dev of CherryHQ/cherry-studio.

  • SKILL.md
  • references/electron-instance.md
  • references/performance-debugging.md

Open the folder on GitHubat commit dd0767e

Compare with similar skills

Cherry Studio Electron Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cherry Studio Electron Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cherry Studio Electron Dev this skillCherryHQ/cherry-studio52k—~739Automated safety check: PassAGPL-3.0
AO Desktop App LauncherOrchestratorInc/agent-orchestrator13k—~2.4kAutomated safety check: PassApache-2.0
Electron DevTools Trace Analysiskeybase/client9.3k—~809Automated safety check: PassBSD-3-Clause
Dsh Web UI Releaseningbainb/deepseek-harness-desktop776—~1.4kAutomated safety check: WarnBSD-3-Clause
Cmux Debugging Guidemanaflow-ai/cmux28k1 repos~1.1kAutomated safety check: PassCustom licence
Electron Heap Snapshot Analysiskeybase/client9.3k—~875Automated safety check: PassBSD-3-Clause

Similar skills

  • AO Desktop App Launcher

    OrchestratorInc/agent-orchestrator

    Launches, restarts and troubleshoots the real AO Electron desktop app from a checkout, with isolated or real local data and checks for stale processes.

    13k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Electron DevTools Trace Analysis

    keybase/client

    Analyzes Chrome or Electron DevTools Performance trace exports with Python scripts to find where render time actually goes, without opening DevTools.

    9.3k GitHub stars~809 tokensUpdated today
    DevelopmentAuto-check passed

  • Dsh Web UI Release

    ningbainb/deepseek-harness-desktop

    Release and publish the dsh-web-ui monorepo (DSH Web GUI plugin family + skin collection) — bump all packages to one unified version, commit and tag, push the vX.Y.Z tag that triggers the GitHub…

    776 GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check: warnings

  • Cmux Debugging Guide

    manaflow-ai/cmux

    Covers debug logging, the Debug menu, profiling rules and runtime pitfalls for working on the cmux macOS terminal app.

    28k GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • Electron Heap Snapshot Analysis

    keybase/client

    Analyzes V8, Chrome and Electron .heapsnapshot files with Node scripts to find memory leaks, detached DOM nodes and the retainer paths that keep objects alive.

    9.3k GitHub stars~875 tokensUpdated today
    DevelopmentAuto-check passed

  • Issue Fix

    mono/SkiaSharp

    Fix bugs in SkiaSharp C bindings. An agent skill from mono/SkiaSharp.

    5.6k GitHub stars~5.1k tokensUpdated today
    DevelopmentAuto-check passed

More from CherryHQ/cherry-studio

All 30 skills in this repo

  • Office File Transform

    CherryHQ/cherry-studio

    Derives new files from a selected part of a spreadsheet, Word document, PDF or slide deck, such as a cell range, paragraph, page or slide, without ever modifying the source file.

    52k GitHub stars~4.7k tokensUpdated today
    Auto-check passed

  • GitHub Issue Creator

    CherryHQ/cherry-studio

    Creates GitHub issues for the current repository by choosing the matching issue template and following its format, with a permission check for engineering tasks.

    52k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Cherry Studio PR Review

    CherryHQ/cherry-studio

    Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.

    52k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Cherry Studio Regression Tests

    CherryHQ/cherry-studio

    Runs Cherry Studio's critical-path regression suite as deterministic Playwright E2E tests through a GitHub workflow on macOS and Windows runners.

    52k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Antigravity CLI Runner

    CherryHQ/cherry-studio

    Runs the Antigravity CLI headlessly with the agy command to analyze a repository or carry out a coding task, then checks its JSON result and the diff.

    52k GitHub stars~531 tokensUpdated today
    Auto-check passed

  • Kimi Code Delegation

    CherryHQ/cherry-studio

    Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.

    52k GitHub stars~504 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Cherry Studio Electron Dev

What does Cherry Studio Electron Dev do?

Develops, debugs and profiles Cherry Studio in a tracked Electron instance, reusing a verified running instance and capturing before and after evidence for each change. json, CDP target selection, launching, replacement and shutdown. The development loop states the expected behavior and its proof, reads the relevant code, verifies the tracked instance, reproduces the current behavior, captures the smallest useful evidence such as DOM, console and network output, main-process logs or metrics, makes only the requested change and repeats the same scenario.

When should I use Cherry Studio Electron Dev?

Cherry Studio Electron Dev fits situations like: implementing a UI or interaction change in Cherry Studio; investigating lag, jank or high CPU in the running app; checking for memory growth or leaks with the same scenario before and after a fix; analyzing slow startup of the Electron app.

How do I install Cherry Studio Electron Dev in Claude Code?

Run `npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev -a claude-code`. Or copy the skill folder (.agents/skills/cherry-electron-dev in CherryHQ/cherry-studio) into .claude/skills/cherry-electron-dev in your project. Claude Code loads it when a task matches its description.

How do I install Cherry Studio Electron Dev in Codex?

Run `npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev -a codex`. Or copy the skill folder (.agents/skills/cherry-electron-dev in CherryHQ/cherry-studio) into .agents/skills/cherry-electron-dev in your project. Codex loads it when a task matches its description.

Can I use Cherry Studio Electron Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CherryHQ/cherry-studio --skill cherry-electron-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cherry-electron-dev, .gemini/skills/cherry-electron-dev, .github/skills/cherry-electron-dev and .opencode/skills/cherry-electron-dev in your project.

What does Cherry Studio Electron Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Cherry Studio Electron Dev is instructions for the agent only. Our summary lists: A Cherry Studio checkout that can launch Electron; A tracked instance with a CDP port, as described in references/electron-instance.md.

Does Cherry Studio Electron Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cherry Studio Electron Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cherry Studio Electron Dev use?

Cherry Studio Electron Dev is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cherry Studio Electron Dev use?

About 739 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.7k tokens, read only when the agent opens those files.

What are the alternatives to Cherry Studio Electron Dev?

Skills that share tags, products or a category with Cherry Studio Electron Dev: AO Desktop App Launcher (OrchestratorInc/agent-orchestrator, 13k stars), Electron DevTools Trace Analysis (keybase/client, 9.3k stars), Dsh Web UI Release (ningbainb/deepseek-harness-desktop, 776 stars) and Cmux Debugging Guide (manaflow-ai/cmux, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cherry Studio Electron Dev?

CherryHQ (a GitHub organization) maintains it in CherryHQ/cherry-studio, which has 52,407 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 2026.

Source: CherryHQ/cherry-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.