CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-organized, lean instruction skill that uses progressive disclosure effectively via two clearly signaled, verified references. Actionability and workflow validation are solid but slightly rely on the references and generic lint/test guidance rather than fully inline executable steps.

Suggestions

Inline one or two concrete validation commands (e.g., the lint/test invocation or the exact instance-verification check) instead of deferring entirely to 'follow current user and repository instructions' to tighten workflow validation.

Add an explicit pass/fail gate in the Development loop between making the change and the before/after comparison, so the verification checkpoint is unambiguous rather than implicit.

DimensionReasoningScore

Conciseness

The body is lean and overview-shaped — it assumes Claude knows Electron, never explains basic concepts, and delegates detail to references — so every token earns its place rather than the trimmable over-explanation of a 4.

5 / 5

Actionability

Provides concrete guidance (store artifacts under '.context/cherry-electron-dev/', use the reference's 'persistent' policy, capture named evidence types) but as an instruction-only skill delegates executable specifics to references, leaving minor gaps versus fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The 8-step Development loop is clearly sequenced with an evidence-based feedback loop (step 1 defines proof, step 8 compares before/after), but lint/test validation is delegated generically ('follow current user and repository instructions'), leaving a minor validation gap below the explicit-gate 5.

4 / 5

Progressive Disclosure

A clear overview signals two real one-level-deep references (electron-instance.md, performance-debugging.md, both present) with markdown links and appropriately splits instance-management and performance detail into separate files, matching easy-navigation structure.

5 / 5

Total

18

/

20

Passed

Description

88%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, specific description that explicitly pairs a concrete 'what' with an explicit 'Use for ...' trigger list and natural developer keywords. The only mild weakness is overlap risk with the related cherry-pr-test skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Develop, fix, and profile', 'bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis' — giving comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Clearly answers 'what' ('Develop, fix, and profile Cherry Studio in a tracked Electron instance') and 'when' via an explicit 'Use for ...' clause listing concrete trigger phrases, matching the anchor that requires both with concrete triggers.

5 / 5

Trigger Term Quality

Strong natural terms a user would say ('bug fixing', 'lag or jank', 'leak checks', 'DevTools', 'startup-performance') with synonym coverage, but no file-extension-style terms and a few natural variants missing, fitting 'good keyword coverage' rather than the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The Cherry Studio Electron niche with dev/profile-specific triggers is mostly distinct with minimal conflict risk, but the sibling cherry-pr-test skill creates minor overlap risk for generic 'work on Cherry Studio' requests, fitting 'mostly distinct; minor overlap' rather than the minimal-risk 5.

4 / 5

Total

18

/

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