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

92%

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

88%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.

A well-structured decision-workflow skill: sequenced steps with per-step decision outputs, executable code and commands, verified one-level-deep references, and a strong anti-patterns checklist. Its main cost is length — the inline parallelism deep-dive could live in the references directory.

DimensionReasoningScore

Conciseness

The body is dense and directive — every section ends in a concrete 'Decision output' and prose is heuristic rather than tutorial ('A framework in a language the team does not write rots: nobody fixes flake they cannot read'). Minor over-explanation remains: the ~100-line parallel-workers deep-dive with two full inline code snippets could be tightened or delegated to the existing references/fixture-mechanics.md, which keeps it below the lean 5 anchor but above the 3 anchor's 'some unnecessary explanation'.

4 / 5

Actionability

Guidance is fully executable throughout: a copy-paste-ready pytest FileLock/worker-database fixture, a Playwright worker-scoped auth fixture (placeholders explicitly flagged as such), exact commands ('npx playwright test --shard=1/4', 'gh run rerun <run-id> --failed'), concrete config values ('trace: on-first-retry'), directory trees, and per-step decision tables.

5 / 5

Workflow Clarity

Seven steps are explicitly sequenced with a 'Decision output' checkpoint after each, and validation checkpoints are present ('before recording it, check every row has test retry 0 and distinct content'; isolation recorded per resource 'before the worker count goes above 1'). The anti-patterns table doubles as an error-avoidance checklist and the worked example ends in an ordered build sequence.

5 / 5

Progressive Disclosure

Both bundle references (references/fixture-mechanics.md, references/worked-example.md) exist, are clearly signaled inline at the point of need, and are one level deep — they link only to external docs, not to further files. Minor gap: the parallelism mechanics and two full code snippets stayed inline in SKILL.md rather than joining fixture-mechanics.md, so the split is not quite optimal.

4 / 5

Total

18

/

20

Passed

Description

92%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: it states a concrete multi-step capability, an explicit 'Use when' trigger covering both the greenfield and re-architecture cases, and a distinct niche. The only gap is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description enumerates the full workflow concretely — 'Walks seven steps from inventorying the app to runner, layout, fixtures, object model, data and mocks, reporting, CI and conventions' — and names the concrete output: 'a written blueprint with a build order'. Coverage of the capability is comprehensive rather than gappy, matching the top anchor.

5 / 5

Completeness

It explicitly answers both questions: an explicit 'Use when designing... or re-architecting' trigger clause, and a clear 'what' — seven named steps producing 'a written blueprint with a build order'. This matches the anchor requiring both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'designing a test automation framework from scratch' and 're-architecting one that grew organically' are phrases users would naturally say, giving good keyword coverage. A few natural synonyms ('test suite', 'harness', 'test architecture') are missing, so it falls short of the comprehensive-synonyms anchor at 5 but sits clearly above the 3 anchor's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The framing 'designing a test automation framework from scratch or re-architecting one that grew organically' carves a distinct design/blueprint niche that does not overlap with scaffolding, runner choice, or test-writing skills. Triggers are specific and unlikely to fire the wrong skill.

5 / 5

Total

19

/

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