run-smoke-tests

Run Playwright smoke tests, debug failures, and verify fixes

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

The content is concise, actionable, and well-structured with executable commands and a clear iterative workflow including a retry loop, fully appropriate for a simple single-purpose testing skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, never explaining what Playwright or smoke tests are; every section (Trigger, Workflow, Example Commands, Guardrails, Output) earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands such as `npm run smoketest` and `npm run smoketest -- path/to/test.spec.ts`, matching the level-3 anchor for specific executable examples.	3 / 3
Workflow Clarity	The four-step sequence (build, run, inspect/isolate root cause, apply fix and rerun until stable) has an explicit error-recovery feedback loop and a root-cause checkpoint, satisfying the level-3 anchor for a simple iterative skill.	3 / 3
Progressive Disclosure	At under 50 lines with no bundle files and well-organized sections, it meets the rubric's allowance for simple skills to score 3 on progressive disclosure with clear organization alone.	3 / 3
	Total	12 / 12 Passed

Description

82%

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 and distinctive with good natural trigger terms, but it lacks an explicit "Use when..." clause stating when to invoke the skill, which caps completeness at 2.

Suggestions

Add an explicit usage trigger, e.g. "Use when you need end-to-end smoke verification of a Playwright suite before or after changes, or to debug a failing smoke test."

Include common phrasings users might say (e.g. "Playwright", "e2e tests", "smoke suite") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Run Playwright smoke tests, debug failures, and verify fixes" lists three concrete, distinct actions (run, debug, verify), matching the anchor for multiple specific concrete actions rather than the partial coverage of a 2.	3 / 3
Completeness	It clearly states what the skill does but omits any explicit "Use when..." trigger, so per the guidelines completeness is capped at 2 (what present, when missing/only implied).	2 / 3
Trigger Term Quality	Terms like "Playwright smoke tests", "smoke tests", "failures", and "fixes" are natural phrases a user would say when requesting this skill, giving good coverage as the level-3 anchor requires.	3 / 3
Distinctiveness Conflict Risk	"Playwright smoke tests" defines a clear, narrow niche with distinct triggers unlikely to overlap with unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: 0452e08

Reviewed: 14 days 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.