CtrlK
BlogDocsLog inGet started
Tessl Logo

cherry-pr-test

Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.

69

Quality

85%

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

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

The body is an exemplary lean workflow: concrete executable commands, explicit safety/validation checkpoints, and a clean report template, with detail correctly pushed to a single external reference. Minor room remains to tighten the inline static-analysis checklist.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept explanations or padding — every line is actionable instruction, a concrete command, or a template; it fully assumes Claude's competence.

5 / 5

Actionability

Provides copy-paste-ready commands ('gh pr list ...', 'gh pr checkout <NUMBER>', 'pnpm typecheck', 'mkdir -p /tmp/pr-<NUMBER>') and a complete report template covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation and safety checkpoints ('Record the current branch for restoration', 'Stop and ask if checkout would overwrite them', 'Stop only an instance launched by this PR-test') and a restore-with-fallback feedback loop for the destructive checkout/cleanup steps.

5 / 5

Progressive Disclosure

Well-structured overview that externalizes detailed Electron-instance management to a single, clearly signaled one-level-deep reference ('../cherry-electron-dev/references/electron-instance.md'); the body itself is appropriately scoped, with only minor organization gaps around inlining of the static-analysis checklist.

4 / 5

Total

19

/

20

Passed

Description

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

The description is specific, concrete, and distinct, detailing the full PR-test workflow with real trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, leaving the trigger context only implied.

Suggestions

Append an explicit trigger clause, e.g. 'Use when asked to test a Cherry Studio pull request end-to-end before review.'

Add the synonym 'pull request' alongside 'PR' to broaden natural trigger coverage.

Optionally surface key preconditions (gh/pnpm/auth) as part of the 'when' guidance so users self-select correctly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch' — giving comprehensive coverage of the workflow.

5 / 5

Completeness

Clearly answers 'what' with a detailed workflow, but lacks any 'Use when...' or equivalent explicit trigger clause, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Cherry Studio PRs', 'PR', 'interactive UI tests', 'Electron', 'CDP', 'structured report') with synonym coverage (PR/PRs), but misses common phrasings like 'pull request'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Cherry Studio PR testing via an ephemeral, agent-owned Electron instance through CDP) with highly specific triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

15

/

16

Passed

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.