Source profileQuality 69/100

CherryHQ/cherry-studio/.agents/skills/cherry-electron-dev/SKILL.md

cherry-electron-dev

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.

Source repository stars
49,062
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/cherry-electron-dev"
    Safe inspection promptEditorial

    Inspect the Agent Skill "cherry-electron-dev" from https://github.com/CherryHQ/cherry-studio/blob/dda7cc99d730c36bde685bec586dafe458722a4d/.agents/skills/cherry-electron-dev/SKILL.md at commit dda7cc99d730c36bde685bec586dafe458722a4d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Required runtime workflow

      Before reading or controlling Electron UI, read Electron Instance Management and use its persistent policy.

      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 Elect…
    2. 02

      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…

      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.
    3. 03

      Performance and DevTools

      For lag, jank, high CPU, memory growth, leaks, slow startup, or explicit DevTools use, read Performance Debugging.

      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…
    4. 04

      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.

      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.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score69/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars49,062SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    CherryHQ/cherry-studio
    Skill path
    .agents/skills/cherry-electron-dev/SKILL.md
    Commit
    dda7cc99d730c36bde685bec586dafe458722a4d
    License
    AGPL-3.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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.

    Alternatives

    Compare before choosing

    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    Computed 9631,966

    K-Dense-AI/scientific-agent-skills

    neuropixels-analysis

    Analyze Neuropixels extracellular recordings end-to-end with SpikeInterface. Covers loading SpikeGLX/Open Ephys/NWB data, preprocessing, drift/motion correction, Kilosort4 (and CPU) spike sorting, quality metrics, and unit curation (threshold-based, model-based UnitRefine, and AI-assisted visual review). Use when working with Neuropixels 1.0/2.0 recordings, spike sorting, or extracellular electrophysiology analysis.

    Computed 9531,966

    K-Dense-AI/scientific-agent-skills

    scientific-brainstorming

    Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs. Use for early-stage research brainstorming or prioritizing candidate directions; hand off empirical validation, study design, ethics or regulatory review, and clinical questions to appropriate experts or skills.

    Computed 9431,966

    K-Dense-AI/scientific-agent-skills

    citation-management

    Comprehensive citation management for academic research. Search Google Scholar and PubMed for papers, extract accurate metadata, validate citations, and generate properly formatted BibTeX entries. This skill should be used when you need to find papers, verify citation information, convert DOIs to BibTeX, or ensure reference accuracy in scientific writing.