CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-strategy-author

Authors a test strategy document (a master test plan) for a project, release, or feature - covers scope, in/out, test types per layer (unit / integration / contract / E2E / perf / security / a11y), risk-based test prioritization that maps top risks to test investment (per `risk-matrix`), tooling stack, environments, exit criteria, and ownership. Includes a risk-based test-planning workflow that turns a feature scope plus the risk matrix into a budgeted per-risk test plan with owners, effort estimates, and an explicit risks-not-addressed section. Use when a team needs the release-readiness artifact stakeholders sign off on before significant test investment, or a risk-prioritized test plan for a feature or quarter.

72

Quality

90%

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 highly actionable, well-sequenced authoring skill with concrete templates, effort estimates, a worked example, and a real validation feedback loop before sign-off. Its main weakness is a heavy inlined template that could be split into a reference file rather than carried entirely in SKILL.md.

Suggestions

Move the full ~110-line strategy template (Step 1) into a references/ file (e.g. STRATEGY_TEMPLATE.md) and keep only a condensed skeleton + pointer in SKILL.md to improve progressive disclosure.

Trim the Step 4 product-type emphasis table, since its content largely overlaps Section 2 (risks) and Section 3 (layers) of the template.

Consider adding a short validation command or checklist artifact under scripts/ or references/ so the Step 1a validation is reusable rather than only described inline.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — it does not explain what testing or a test pyramid is — but the full ~110-line template is inlined at top level and a few tables (Step 4 product-type emphasis) overlap Section 2/3 content, so it is not fully lean.

4 / 5

Actionability

Provides a fully scaffolded section-by-section template, concrete per-test-type effort estimates (unit 0.5h, E2E 8h, etc.), a worked example plan with a risks-not-addressed table, measurable exit criteria, and explicit guardrails — copy-ready, executable guidance covering common cases.

5 / 5

Workflow Clarity

Steps are clearly sequenced (Step 1 author → 1a validate → 2 tailor → 3 cadence) with an explicit validation feedback loop in Step 1a (assert mappings, assert measurability, record open questions, re-run, sign off only when unblocked), matching the anchor-5 checklist/validation example.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references and a References list, but no bundle files exist and the large inline template is content that could arguably live in a separate reference file; structure is good but not the ideal split of overview vs. detailed material.

4 / 5

Total

18

/

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, specific, third-person description that covers what the skill authors and when to invoke it, with explicit stakeholder trigger language and clear differentiation from sibling skills. It is slightly long and uses formal vocabulary rather than the most common synonyms users might say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and contents (scope, in/out, enumerated test types per layer, risk-based prioritization, tooling, environments, exit criteria, ownership) plus a workflow producing a budgeted per-risk plan with owners, estimates, and a risks-not-addressed section — comprehensive coverage matching the anchor-5 example.

5 / 5

Completeness

Clearly answers both 'what' (authors the document and an included planning workflow with enumerated contents) and explicit 'when' via concrete 'Use when...' trigger clauses, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Natural stakeholder trigger phrases ('release-readiness artifact stakeholders sign off on', 'test investment', 'risk-prioritized test plan') are present and relevant, but the vocabulary is formal/specialized and misses some common synonyms a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

Clear niche (master test plan / release-readiness artifact) with explicit differentiation from the related `risk-matrix` skill; minor overlap risk with that closely related per-feature skill keeps it just below a 5.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents