CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-execution-checklist

Converts a regression suite (or test plan) into an executable manual checklist for cases when automation isn't viable - a release-day smoke checklist, a post-incident verification list, or a periodic compliance check. Outputs a per-TC checkbox list with the minimal preconditions, the action, and a one-line "what to look for" - short enough to fit on one page per major flow. Use when the team needs a focused human-runnable list (not full step-tables), e.g., for production smoke after deploy or for the on-call rotation's quick verification.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

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 body is a lean, highly actionable instruction skill: concrete one-line checklist templates with real example values, a sequenced six-step workflow with explicit validation/feedback checkpoints, and a well-organized single-file structure with clearly signaled sibling references. It avoids explaining basics Claude already knows and pairs the workflow with an anti-patterns table and limitations section.

DimensionReasoningScore

Conciseness

Lean throughout - assumes competence, uses tight tables and one-line templates rather than explaining what a checklist or smoke test is; every block (scope table, item template, anti-patterns) earns its tokens.

3 / 3

Actionability

Copy-paste-ready markdown templates with concrete values (qa-test-user@example.com, BOOK-001, WELCOME10) plus explicit item-count and time budgets per group - fully executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

Clear six-step sequence with explicit validation checkpoints: 3+-line items get split/moved (Step 2), >50% budget overrun triggers trimming (Step 4), and empty groups flag coverage gaps (Step 3); the anti-patterns table closes the loop with fixes.

3 / 3

Progressive Disclosure

A single, well-organized SKILL.md with clear sections (Overview, When to use, Steps 1-6, Output, Anti-patterns, Limitations, References) and one-level-deep sibling-skill references that are clearly signaled - appropriate for a single-purpose skill with no bundle files.

3 / 3

Total

12

/

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.

The description is third-person, specific, and tightly scoped: it states concrete outputs, an explicit Use-when clause, and distinguishes itself from the full step-table sibling skill. Trigger terms map naturally to real user phrasings across smoke, on-call, compliance, and bug-bash scenarios.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - "Converts a regression suite... into an executable manual checklist" and "Outputs a per-TC checkbox list with the minimal preconditions, the action, and a one-line 'what to look for'" - matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what (convert a regression suite/test plan into a checklist) and when ("Use when the team needs a focused human-runnable list... e.g., for production smoke after deploy or for the on-call rotation's quick verification").

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered: "release-day smoke checklist", "post-incident verification list", "periodic compliance check", "production smoke after deploy", "on-call rotation's quick verification".

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche (human-runnable checklist, explicitly "not full step-tables") that distinguishes it from sibling skills like manual-test-script-author, with distinct triggers unlikely to misfire.

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