CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-strategy-author

Use for any question or task about a test strategy or master test plan, including what one contains or teams that test inconsistently so nobody knows what was tested: scope, test types per layer, risk-based prioritization, tools, environments, exit criteria and ownership, plus a budgeted per-risk test plan with owners and effort, for stakeholder sign-off.

Quality

83%

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

73%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 is a well-sequenced, highly actionable authoring workflow with a genuine validation feedback loop (Step 1a) and a concrete template with worked examples. Its main weakness is token efficiency: quoted external definitions and duplicated reference listings add length without adding guidance. Placeholder template sections and unspecified sibling skills leave minor actionability gaps.

Suggestions

Trim the 'Sources behind the template sections' quotes and the Overview's ISTQB definition to one-line citations; condense the six link definitions duplicated between the Overview block and the References section into a single list.

Fill or remove placeholder template sections (e.g., '## 4. Tooling' is only '(Stack inventory per layer; references to specific skills)') so every emitted section has concrete instructions.

Briefly state what each referenced sibling skill provides (e.g., 'risk-matrix Step 4 maps risk classes to test types') or inline the minimal mapping so the skill is executable when those skills are unavailable.

DimensionReasoningScore

Conciseness

The body is mostly efficient tables, templates, and steps, but 'Sources behind the template sections' spends ~25 lines quoting ISTQB, Fowler, and W3C definitions ('A high-level description of the test levels...', 'Write tests with different granularity...') that Claude already knows, and the link-definition block after the Overview duplicates the References section — matching 'mostly efficient but includes some unnecessary explanation or could be tightened'. It is not 4 because these quote blocks and duplicated reference listings are more than minor trimmable instances.

3 / 5

Actionability

Highly actionable for an instruction-only skill: a complete copy-paste markdown template, specific effort estimates ('unit 0.5h, property-based 2h, ... load 1d, chaos 2d'), explicit guardrails ('never plan more than 20% over budget'), and a worked example plan, matching 'mostly executable guidance with minor gaps'. It is not 5 because some template sections are bare placeholders ('## 4. Tooling' is a one-line parenthetical) and execution leans on sibling skills ('risk-matrix', 'test-pyramid-balancer', 'prod-canary-validator') that are named but not specified.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Step 1 structure → Step 1a validation → Steps 2-5) with an explicit validation checkpoint and feedback loop ('Assert every in-scope feature... maps to a risk class...', 'record it as an open question... resolve it, then re-run this check'), matching the 5 anchor of clear sequence, explicit validation, and error-recovery loops. The destructive/batch cap does not apply since this is document authoring, not a destructive or batch operation.

5 / 5

Progressive Disclosure

No bundle files exist, so this scores on structure: sections are well-organized and navigable (Overview, When to use, Steps 1-5, Anti-patterns, Limitations, References) with one-level-deep external URL references, matching 'good structure; most content is appropriately placed; minor organization gaps'. It is not 5 because the 110-line inline template (Step 1) plus reference-pattern and planning material could plausibly be split into a reference file for a leaner overview; it is not 3 because nothing is buried and navigation is easy.

4 / 5

Total

16

/

20

Passed

Description

83%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 with an explicit 'Use for...' trigger clause, natural scenario phrasing, and a concrete list of deliverables. Both what and when are clearly answered. Minor improvements possible: add common synonyms ('test approach', 'QA strategy') and sharpen the action verbs.

DimensionReasoningScore

Specificity

Enumerates several concrete deliverables ('scope, test types per layer, risk-based prioritization, tools, environments, exit criteria and ownership', 'budgeted per-risk test plan with owners and effort') matching the 'several specific actions; minor gaps' anchor; it falls short of 5 because capabilities are listed as content areas rather than crisp actions, and exceeds 3 by covering far more than 1-2 actions.

4 / 5

Completeness

Both what and when are explicit: an explicit trigger clause ('Use for any question or task about a test strategy or master test plan, including... teams that test inconsistently so nobody knows what was tested') plus concrete deliverables ('budgeted per-risk test plan with owners and effort, for stakeholder sign-off'), matching the 5 anchor; it is not 4 because the when-clause includes concrete trigger scenarios rather than being merely serviceable.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('test strategy', 'master test plan', 'teams that test inconsistently so nobody knows what was tested', 'stakeholder sign-off'), matching 'good keyword coverage; a few natural terms missing' — variations like 'test approach', 'QA strategy', or 'test coverage' are absent, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

'Test strategy or master test plan' is a clear niche with distinct triggers, matching 'mostly distinct; minor overlap risk' — the mention of a 'per-risk test plan' slightly overlaps with closely related risk-matrix/per-feature planning skills, so it does not reach the minimal-conflict 5 anchor.

4 / 5

Total

17

/

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