CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-strategy-author

Use when a project, release or feature needs a test strategy or master test plan that stakeholders sign off: 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.

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.

The body is a tight, highly actionable authoring guide: a complete document template with concrete numbers, explicit validation before sign-off, and a budgeted per-risk planning procedure with guardrails and an audit-trail example. Its only weaknesses are minor padding in the Overview/References and the lack of any file-level split for the two large embedded artifacts.

DimensionReasoningScore

Conciseness

The body is dense and tabular with no explanations of concepts Claude already knows, but the Overview's motivational justification ("Without it, test investment is gut-feel...") and a References section restating skills already cited inline are minor padding that could be trimmed, fitting the 'efficient with minor trims' anchor.

4 / 5

Actionability

Guidance is fully executable for a document-authoring skill: a copy-paste 11-section template with concrete coverage numbers, named tools and owners, specific effort estimates ("unit 0.5h, property-based 2h ... load 1d"), and a worked example test plan with a filled-in per-risk table.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced and Step 1a is an explicit validation gate with a feedback loop — "record it as an open question ... resolve it, then re-run this check" and "Collect the Approval sign-offs only once no Section 11 item still blocks release" — plus planning guardrails in Step 5, matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content is deliberately inline and well-sectioned with clear headers; however the 110-line strategy template and the Step 5 planning procedure are two sizable artifacts that could be split into separately referenced files, keeping it below the ideal split-level anchor.

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 description: it pairs an explicit 'Use when' trigger with a fully itemized list of the artifact's components, covering both the strategy document and the budgeted per-risk test plan. The only gaps are a few missing natural synonyms and slight reliance on the body to disambiguate from lighter-weight test-planning skills.

DimensionReasoningScore

Specificity

The description enumerates the complete deliverable set concretely — "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" — with no meaningful coverage gap, matching the comprehensive anchor rather than the 'minor gaps' level 4.

5 / 5

Completeness

It explicitly answers 'when' with a concrete "Use when a project, release or feature needs a test strategy or master test plan that stakeholders sign off" clause and explicitly answers 'what' by itemizing every component of the artifact produced; level 4 would require a vaguer or less explicit 'when'.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("test strategy", "master test plan", "stakeholders sign off", "a project, release or feature needs"), but common synonyms like "QA strategy", "testing approach", or "release readiness" are missing, placing it just below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The stakeholder sign-off framing and "master test plan" terminology carve a clear niche distinct from generic testing skills, though it could still slightly overlap with a sibling per-feature test-planning skill (which the body, not the description, disambiguates).

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