CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-framework-blueprint

Use when designing a test automation framework from scratch or re-architecting one that grew organically. Walks seven steps from inventorying the app to runner, layout, fixtures, object model, data and mocks, reporting, CI and conventions, and outputs a written blueprint with a build order.

Quality

87%

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

81%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 body delivers highly actionable, well-sequenced design guidance with executable snippets and explicit per-step checkpoints, and its two reference files are real, relevant, and clearly signaled. Its main weakness is token efficiency: the parallel-workers mechanics in Step 3 should live in a reference file rather than inline.

Suggestions

Move the pytest-xdist and Playwright parallel-worker mechanics (prose + both code snippets) from Step 3 into references/fixture-mechanics.md or a dedicated reference, keeping only the isolation decision rule and the decision-output row in SKILL.md.

Trim the repeated citation-justifying asides (e.g. inline quotes from the Playwright docs explaining auto-waiting and web-first assertions) down to the rule plus a single link.

Add a few natural trigger synonyms (e.g. 'test suite', 'harness', 'test architecture') to the description to broaden keyword coverage.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious decision guidance, but the ~90-line parallel-workers subsection in Step 3 (xdist prose plus a 26-line pytest snippet and a 20-line Playwright snippet) inlines deep mechanics that belong beside references/fixture-mechanics.md, and several doc-citation justifying asides could be trimmed. This is more than the 'minor instances' of the 4 anchor, fitting the 'could be tightened' 3 anchor.

3 / 5

Actionability

Fully executable guidance throughout: a concrete directory tree, fixture-scope decision table, copy-paste-ready pytest FileLock and Playwright worker-auth snippets (placeholders explicitly flagged), per-step 'Decision output' specifications, and a worked CI matrix. Specific examples cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The seven steps are clearly sequenced with each step ending in an explicit decision-output checkpoint, Step 6 includes a validation check ('check every row has test retry 0 and distinct content'), and Step 7 assembles the outputs into an enforced conventions doc. This matches the 5 anchor's explicit checkpoints and checklists; it is not a destructive/batch operation so no cap applies.

5 / 5

Progressive Disclosure

Good structure with a clear overview, well-signaled one-level-deep references ([references/fixture-mechanics.md], [references/worked-example.md] - both real files), and easy navigation via consistent section headers. It falls short of the 5 anchor because the parallel-workers deep dive inlined in Step 3 is content that should be split into the references bundle.

4 / 5

Total

17

/

20

Passed

Description

88%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 description: explicit use-when triggers, a complete enumeration of the seven-step process, and concrete output artifacts. The only gaps are a few missing natural synonyms and no self-differentiation from adjacent skills in the same ecosystem.

DimensionReasoningScore

Specificity

The description enumerates all seven concrete steps ("inventorying the app to runner, layout, fixtures, object model, data and mocks, reporting, CI and conventions") plus two concrete deliverables ("a written blueprint with a build order"), giving comprehensive coverage of what the skill does. It exceeds the 4 anchor because there are no meaningful gaps in the action list.

5 / 5

Completeness

It explicitly answers both questions: an explicit "Use when" clause with two concrete trigger scenarios, and a clear statement of what it does ("Walks seven steps... and outputs a written blueprint with a build order"). This matches the 5 anchor with concrete trigger phrases for both what and when.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("designing a test automation framework from scratch", "re-architecting one that grew organically") and map well to what a user would say. It falls short of the 5 anchor because common variations like "test suite", "harness", "SDET", or "test architecture" are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (end-to-end framework design producing a blueprint) and triggers are distinct from generic testing skills. It stays at 4 rather than 5 because the description does not differentiate itself from the closely related runner-choice and scaffolding skills it sits between, leaving some overlap risk with those.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page