CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-framework-architecture-audit

Use when a test automation framework has grown without structural review, before a big refactor, or when its written conventions may no longer match the code. Grades eight axes PASS, WARN or FAIL: page objects, base classes, fixtures, helpers, naming, waits and retries, convention drift and CI.

Quality

86%

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

78%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 strong, highly actionable audit skill: every axis has measurable thresholds, cited grounding, and an enforced output format with conventions made explicit. The main costs are recurring justification prose that inflates token budget and a couple of underspecified procedural details (inventory construction, A7 sampling).

Suggestions

Condense the per-axis convention-justification paragraphs to one or two lines each (the full reasoning already lives implicitly in the output's conventions section, which requires printing the cut and value); this would cut substantial tokens without losing the thresholds.

Add a short opening step describing how to build the inventory (which directories to walk, what counts as a test file vs a helper module) since the output template requires counts the procedure never gathers.

Specify the A7 sampling method (e.g. how many test bodies to sample and how to choose them) so the "share of sampled test bodies" measurement is reproducible across audits.

DimensionReasoningScore

Conciseness

The body is dense with load-bearing content (band tables, thresholds, output template), but each of the eight axes carries a multi-paragraph convention-justification (e.g. "The reasoning is blast radius, and it is arithmetic rather than taste", "That is not drift, it is fiction") plus boundary-setting prose that could be condensed without losing the cuts. It is mostly efficient but noticeably tightenable, which matches anchor 3 rather than 4.

3 / 5

Actionability

Every axis has exact band thresholds, concrete detection patterns (`page.waitForTimeout(...)`, `cy.wait(2000)`, `expect(await locator.isVisible()).toBe(true)` vs `await expect(locator).toBeVisible()`), and the skill closes with a copy-paste output template spelling out every field. As an instruction-only skill its guidance is fully concrete and covers the common runner cases.

5 / 5

Workflow Clarity

The sequence is clear (baseline preconditions → per-axis measurement → rollup rule → fix order → output template) with self-checking guards such as "state which pattern you assumed" and emitting `n/a` when no conventions doc exists. Minor gaps keep it at anchor 4: the inventory the output requires is never built by an explicit step, and A7's "share of sampled test bodies" leaves the sampling method unspecified.

4 / 5

Progressive Disclosure

A single clearly-signaled reference (`references/audit-detail.md`) is verified to exist, is one level deep with no nested references, and appropriately offloads the worked example and anti-pattern table. Section headers per axis plus the output template make the 460-line body easy to navigate.

5 / 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.

The description explicitly answers both what and when with concrete triggers, enumerates the full audit scope, and carves out a distinct niche. Trigger coverage is good but would benefit from a few more natural synonyms users say when reaching for a framework audit.

DimensionReasoningScore

Specificity

"Grades eight axes PASS, WARN or FAIL: page objects, base classes, fixtures, helpers, naming, waits and retries, convention drift and CI" enumerates every measured axis plus the grading output, and states the object being audited. This matches anchor 5's comprehensive coverage of concrete actions rather than anchor 4's 'minor gaps'.

5 / 5

Completeness

An explicit "Use when…" clause with three concrete trigger conditions answers 'when', and "Grades eight axes…" with the full axis list answers 'what'. Both are explicit with concrete triggers, matching anchor 5.

5 / 5

Trigger Term Quality

"test automation framework", "structural review", "big refactor", and "written conventions may no longer match the code" are natural trigger phrases users would say. It falls short of anchor 5 because common synonyms and framework names users actually mention (E2E tests, Playwright, pytest, test suite review) are absent.

4 / 5

Distinctiveness Conflict Risk

Scoping to the framework's internal structure (object models, inheritance depth, fixture scope) gives it a clear niche distinct from per-file test review. It stays at anchor 4 rather than 5 because a suite-level test audit is a closely adjacent trigger the description does not itself disambiguate.

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