CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. Reuse a verified workspace instance and manage its lifetime according to the selected workflow.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction-style skill body: lean directives, a validated dev loop with before/after evidence checkpoints, and clean progressive disclosure to three real, one-level-deep references. The single relative weakness is that the body itself contains no executable commands, deferring all procedures to the reference files by design.

DimensionReasoningScore

Conciseness

Every line is a directive ("Keep Electron running. Use HMR for renderer changes", "Detach profiling sessions afterward; do not close the CDP browser"); there are no concept explanations, no padding, and the body even forbids duplicating reference procedures ("Do not reproduce those procedures here"), so every token earns its place.

5 / 5

Actionability

The guidance is concrete for an instruction-only skill — named policies (`persistent`/`ephemeral`), concrete paths (`.context/cherry-electron-dev/`, `instance.json`), and specific step directives — but all copy-paste executable procedures (launching, CDP binding, PR checkout) are delegated to the reference files, so the body alone is not fully executable; it sits between anchors 4 and 5.

4 / 5

Workflow Clarity

The 8-step development loop is clearly sequenced with explicit validation checkpoints ("Reproduce or inspect the current behavior before editing", "Repeat the same scenario and compare before/after evidence"), error-recovery guidance ("Restart only for a non-reloadable layer, crash, unreliable runtime state, or startup profiling"), and a routing checklist for workflow selection, satisfying the feedback-loop and checklist requirements of anchor 5.

5 / 5

Progressive Disclosure

The body is a lean overview that clearly signals three existing, one-level-deep reference files with when-to-read conditions ("For a bounded PR test, read [PR Testing]", "Before reading or controlling Electron UI, read [Electron Instance Management]", "For lag, jank, high CPU... read [Performance Debugging]"); all three bundle files were verified to exist, cross-links between them are same-level, and content is appropriately split with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and an explicit 'Use for' trigger clause tied to a specific project niche. The only gap is a few natural user-side trigger phrases (slow/laggy/crash/memory-leak style terms) that live in the body but not the description.

DimensionReasoningScore

Specificity

"Develop, fix, profile, and test PRs in a tracked Cherry Studio Electron instance" plus "DevTools inspection, performance analysis, and interactive PR verification with a test report" lists multiple concrete actions covering implementation, debugging, profiling, testing, and instance lifetime management ("Reuse a verified workspace instance and manage its lifetime"), which is comprehensive coverage of the skill's scope.

5 / 5

Completeness

It explicitly answers both: what ("Develop, fix, profile, and test PRs in a tracked Cherry Studio Electron instance") and when ("Use for implementation, UI and interaction work, runtime debugging, DevTools inspection, performance analysis, and interactive PR verification"), matching the anchor-5 pattern of a concrete what followed by an explicit 'Use for' trigger clause.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "implementation", "UI and interaction work", "runtime debugging", "DevTools inspection", "performance analysis", "PR verification" — but a few natural phrases users would say are missing (e.g. "slow", "laggy", "crash", "memory leak", "startup") and no file extensions, so it falls between anchor 4 and the fully comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"tracked Cherry Studio Electron instance" and "verified workspace instance" pin a clear niche that only this skill occupies; conflict risk with generic Electron or general PR-testing skills is minimal because the trigger terms are project-specific.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

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

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.