run-smoke-tests

Run Playwright smoke tests, debug failures, and verify fixes

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./cursor-team-kit/skills/run-smoke-tests/SKILL.md

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.

The content is lean, well-structured, and actionable with concrete commands and a feedback loop; minor gaps in trace-inspection specifics and an explicit isolation checkpoint keep it from full marks.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence; sections are short, no basic concepts are explained, and every line earns its place.	5 / 5
Actionability	It provides concrete executable commands (npm run smoketest, smoketest -- path, smoketest-no-compile), but lacks copy-paste examples for trace inspection and the fix/rerun steps are high-level.	4 / 5
Workflow Clarity	The numbered workflow has a clear sequence with a rerun-until-stable feedback loop, but the inspection/isolation step has no explicit validation checkpoint before applying a fix.	4 / 5
Progressive Disclosure	For a simple sub-50-line skill with no bundle files, the well-organized sections (Trigger, Workflow, Example Commands, Guardrails, Output) fully satisfy progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

56%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 concise and names concrete actions, but lacks an explicit trigger clause and has only moderate keyword coverage, capping completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you need end-to-end smoke verification before or after changes.'

Broaden trigger terms with synonyms users say: 'e2e tests', 'end-to-end tests', 'flaky tests', 'regression checks'.

Consider mentioning reporting/output of results to round out the capability list.

Dimension	Reasoning	Score
Specificity	'Run Playwright smoke tests, debug failures, and verify fixes' names the domain and three concrete actions (run, debug, verify), with only minor coverage gaps such as no mention of reporting.	4 / 5
Completeness	It clearly states what the skill does, but there is no explicit 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes 'smoke tests', 'Playwright', 'failures', and 'fixes' which are natural terms, but misses common variations and synonyms like 'e2e', 'end-to-end', 'flaky', or 'regression'.	3 / 5
Distinctiveness Conflict Risk	The Playwright + smoke-test niche is fairly distinct, though it could overlap with broader test-runner or debugging skills.	4 / 5
	Total	14 / 20 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
Path: cursor-team-kit/skills/run-smoke-tests/SKILL.md
Commit: 51a96e0

Reviewed: 2 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.