CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/smoke-suite-gate

Build-an-X workflow for a critical-path smoke suite that runs in <5 minutes - picks the 5-15 highest-business-value journeys (login, hero flow, checkout, payment, primary read), implements as fast E2E or API tests, gates per-deploy, retries on transient failures with quarantine. Use as the canary-precursor or per-deploy verification gate; the team's "if this fails, the build can't proceed" floor.

77

Quality

97%

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

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

A lean, highly actionable smoke-suite skill with executable examples and a clear sequenced workflow including retry/quarantine feedback loops. Its main gap is progressive disclosure: everything lives inline in one long SKILL.md with no bundle files to offload detail into.

Suggestions

Move the full GitHub Actions workflow (Step 6) and the example Playwright spec (Step 2) into ./references/ files, keeping SKILL.md as an overview that links to them — this adds genuine one-level-deep progressive disclosure and shortens the body.

Add a short 'Quick start' summary near the top pointing to the most-used section, so the ~200-line body is navigable without scanning all six steps.

Relocate the product-type journey examples table (Step 1) into a reference file referenced from the main flow, keeping only the selection criteria inline.

DimensionReasoningScore

Conciseness

Mostly tables, concrete code, and specific budgets with minimal prose; assumes Claude knows testing basics and reserves text for non-obvious gotchas (e.g., test-mode payment ≈95% like prod).

3 / 3

Actionability

Provides copy-paste-ready executable Playwright TypeScript spec and a full GitHub Actions workflow, plus exact commands ('npx playwright test e2e/smoke/ --retries=2') and numeric budgets (30-60s/test, <5 min total).

3 / 3

Workflow Clarity

Steps 1-6 are explicitly sequenced with a validation feedback loop in Step 4 (fail → 2 retries → quarantine → investigate) and a hard 'timeout-minutes: 10' checkpoint capping the deploy gate.

3 / 3

Progressive Disclosure

Well-sectioned and references are clearly signaled, but the entire skill is a single ~200-line inline file with no offloaded reference files, and the full CI workflow and example spec could live one level deeper.

2 / 3

Total

11

/

12

Passed

Description

100%

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 specific, third-person description that states concrete capabilities and explicit usage triggers with strong natural keywords and a distinct niche. It is dense rather than padded, though it runs long for a single sentence.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'picks the 5-15 highest-business-value journeys', 'implements as fast E2E or API tests', 'gates per-deploy', 'retries on transient failures with quarantine' — matching the multi-action anchor.

3 / 3

Completeness

Answers both what (build a critical-path smoke suite <5 min) and when via the explicit 'Use as the canary-precursor or per-deploy verification gate' clause; not capped at 2 since trigger guidance is present.

3 / 3

Trigger Term Quality

Natural terms a QA/CI user would say are well covered: 'smoke suite', 'critical-path', 'canary-precursor', 'per-deploy verification gate', and journey names like 'checkout, payment'.

3 / 3

Distinctiveness Conflict Risk

Clear niche (fast per-deploy smoke gate with retry/quarantine) with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents