cherry-regression-test

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A tight, highly actionable skill body with an explicit sequenced workflow, validation checkpoints, and concrete executable commands throughout. Progressive disclosure is good but not maximal given the length and the amount of inline configuration detail.

Suggestions

Consider moving the full repository variable/secret list into a short reference file (e.g., references/config.md) and keeping only the security-handling rules inline to improve progressive disclosure.

Add a one-line note that the referenced READMEs (tests/e2e/regression/README.md, scripts/e2e/regression/README.md) are the authoritative source for scenario organization and the controller contract, so the pointer is unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean and operational throughout — an 8-step CI contract, a config list, and executable commands with no padding or explanation of concepts Claude already knows, matching the anchor 5 'every token earns its place' example.	5 / 5
Actionability	Provides copy-paste-ready, fully executable commands for focused execution and framework verification (pnpm exec tsx run-phase, pnpm test:e2e:regression --list, vitest/typecheck/lint) covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The CI contract gives a clear 8-step sequence with checkpoints ('Continues after a failed phase', 'enforces the verdict'), and the verification section provides explicit validate-then-check commands with a feedback loop, matching anchor 5.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep repo references (tests/e2e/regression/README.md, scripts/e2e/regression/README.md) clearly signaled; not a 5 because some inline content (e.g., the full secrets list and focused-execution detail) could be split into reference files for a body of this length.	4 / 5
	Total	19 / 20 Passed

Description

82%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 with concrete what/when structure and natural trigger phrases anchored to a clearly distinct niche. The only weakness is the specificity dimension, which lists a single workflow action rather than enumerating multiple concrete actions.

Suggestions

Optionally enumerate the concrete actions the skill performs (e.g., resolve a trusted branch, launch an owned Electron process, run regression phases, enforce the verdict) to lift the specificity dimension toward anchor 5.

Add one or two common synonyms for trigger terms (e.g., 'E2E tests', 'smoke tests') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Cherry Studio regression) and a concrete action (running tasks through a repository-owned Playwright E2E workflow) but lists only one primary action rather than multiple concrete actions, matching anchor 3; not a 4 because no broader action list is given.	3 / 5
Completeness	Explicitly states both what ('Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow') and when ('Use for full regression, release acceptance, development-branch system validation...') with concrete triggers, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say — 'full regression', 'release acceptance', 'system validation', 'cherry-regression-test task' — with good keyword coverage; not a 5 because a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Cherry Studio regression via repository-owned Playwright on macOS/Windows runners — with distinct triggers and minimal overlap risk with other skills, matching anchor 5.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: CherryHQ/cherry-studio
Path: .agents/skills/cherry-regression-test/SKILL.md
Commit: bdd4113

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.