CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/framework-choice-advisor

Pure reference catalog for picking a test automation framework - covers Playwright / Cypress / Selenium / WebdriverIO / Appium / Espresso / XCUITest / RestAssured / Karate / k6 / Locust with side-by-side tradeoffs on speed, cross-browser, mobile, parallelisation, language support, ecosystem maturity, CI integration; a decision tree for matching project NFRs to framework choice; and reference directory / fixture / CI layouts for the chosen stack. This is the **upstream selection step**: it decides which tool to adopt, not how to configure a tool already chosen, and not how to rebalance the unit / integration / E2E mix of an existing suite. Use when starting a new test-automation suite from scratch, before installing any tool.

75

Quality

94%

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

85%

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-support reference: clear sequenced workflow, concrete decision rules and CI flags, and a properly split one-level-deep reference file. Its main weakness is conciseness - time-sensitive 2026 rankings are scattered through the body rather than isolated in a dated section, and some prose/Notes could be trimmed.

Suggestions

Move time-sensitive markers ('2026-recommendation tree', 'fastest-growing 2024-26', 'stale in 18 months') into a single dated/versioned section so the matrix body stays evergreen and conciseness is not penalized.

Tighten the Overview prose and the tradeoff-table Notes columns - the tables already carry the dense information, so the surrounding sentences largely restate it.

Cite each research source once (the Luo 2014 flake-stat and the Capgemini WQR appear in Overview, Step 2, Anti-patterns, and Limitations) instead of repeating the same links and figures across sections.

DimensionReasoningScore

Conciseness

The tradeoff-matrix tables are dense and information-rich and it avoids explaining basics Claude knows, but it is padded with time-sensitive markers scattered outside any 'deprecated/old patterns' section - '2026-recommendation tree', 'fastest-growing 2024-26', 'stale in 18 months' - which the guidelines say should penalize conciseness. It sits above the score-1 verbose-concept anchor but below the lean score-3 bar because several Notes columns and the Overview prose could be tightened.

2 / 3

Actionability

For a decision-support (instruction-only) skill the guidance is concrete and directly applicable: a 6-axis 1-5 NFR scoring rubric, explicit decision-tree mappings ('Multi-browser required + multi-language team -> Playwright'), and copy-paste-ready CI flags ('--shard=X/Y', "trace: 'on-first-retry'"). The rubric's instruction-skill note says absence of code is not penalized when guidance is actionable, so this clears the score-3 bar over the pseudocode/vague score-2 anchor.

3 / 3

Workflow Clarity

A clear Step 1 -> Step 6 sequence (frame NFRs, tradeoff matrix, other layers, layouts, CI, when to defer) plus an anti-patterns checklist table and a 'When to defer the decision' escape clause. This is not a destructive/batch operation so the missing-validation cap at 2 does not apply, and it meets the score-3 'clear sequence ... checklists for complex processes' anchor rather than the score-2 'sequence present but checkpoints missing'.

3 / 3

Progressive Disclosure

The body holds the decision content and splits the deep directory-layout detail into a single one-level-deep, clearly-signaled reference file referenced as [references/directory-layouts.md](references/directory-layouts.md), which exists in the bundle. Matches the score-3 'clear overview with well-signaled one-level-deep references' anchor, not the score-2 'content that should be separate is inline'.

3 / 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 strong, third-person description that pairs a concrete capability list with an explicit Use-when trigger and explicit boundary-setting against adjacent skills. It is comprehensive and distinctive, though somewhat long.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities - enumerates 11 specific frameworks (Playwright/Cypress/Selenium/...) and explicit tradeoff axes (speed, cross-browser, mobile, parallelisation), plus a decision tree and reference layouts. This matches the 'lists multiple specific concrete actions' anchor, not the score-2 'names domain and some actions' which would omit the comparison axes.

3 / 3

Completeness

Explicitly answers both what ('covers ... side-by-side tradeoffs ... a decision tree ... reference directory / fixture / CI layouts') and when via an explicit 'Use when starting a new test-automation suite from scratch, before installing any tool' clause. Meets the score-3 anchor requiring both what AND when with explicit triggers; not capped at 2 because the Use-when clause is present.

3 / 3

Trigger Term Quality

Includes natural terms a user would say - 'picking a test automation framework', 'starting a new test-automation suite from scratch', 'before installing any tool' - covering common phrasings rather than only technical jargon. It is not the score-2 case ('Works with PDF files') because it supplies several user-natural trigger phrasings, not a single generic one.

3 / 3

Distinctiveness Conflict Risk

States a clear niche - 'the upstream selection step: it decides which tool to adopt, not how to configure a tool already chosen, and not how to rebalance the unit / integration / E2E mix' - explicitly negating adjacent skills, so it is unlikely to trigger for the wrong skill. This is the score-3 'clear niche with distinct triggers', not the score-2 'could still overlap'.

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