CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-discipline

Design assertions that prove the actual contract and fail on realistic regressions

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/test-discipline/SKILL.md

The canonical home for this skill is test-discipline in bradygaster/squad

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exemplary lean, instruction-only skill: every pattern is a specific, non-obvious discipline with concrete examples and paired anti-patterns, and validation is baked into the guidance itself. The only meaningful gap is the absence of a worked assertion example showing good vs. bad practice.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero padding: no basic-concept explanations, and every line ("A passing status-only test is not evidence that the intended artifact or contract is correct") adds non-obvious value; nothing to trim for the 4-anchor.

5 / 5

Actionability

Concrete, executable directives ("Mutation-test critical gates by changing the real source or emitted artifact and proving the assertion turns red", "Exercise every caller path") plus two concrete example scenarios; it falls short of 5 only because no worked example shows an actual good-vs-bad assertion. For an instruction-only skill, the absence of code itself is not penalized.

4 / 5

Workflow Clarity

Validation is the skill's core subject (mutation-test gates, red/green feedback, reproduce working-tree failures locally), and sections are clearly organized; however the Patterns form a parallel checklist rather than an unambiguous single action or sequenced workflow, so the simple-skill 5 exception does not fully apply. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is organized into clear Context/Patterns/Examples/Anti-Patterns sections — exactly the case the guideline scores 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 states a clear, concrete capability in third person with no fluff, but it is a single what-statement: it entirely lacks a "Use when..." trigger clause and the natural keywords (tests, unit tests, regression testing) users would say when they need it. Adding explicit trigger guidance would lift the two lowest dimensions.

Suggestions

Add a trigger clause, e.g. "Use when writing or updating tests for an API, public interface, or generated artifact, or when a passing test still lets a regression through."

Include natural user phrasings such as "tests", "unit tests", "regression testing", and "test coverage" so the skill matches how users actually ask for it.

Consider naming one or two more concrete actions (e.g. "mutation-test critical gates, exercise every caller path") to broaden capability coverage without adding fluff.

DimensionReasoningScore

Specificity

Names the test-assertion domain with two concrete actions — "prove the actual contract" and "fail on realistic regressions" — but does not list several specific actions as the 4-anchor requires; it is far more concrete than the generic 2-anchor.

3 / 5

Completeness

The "what" is clear (design assertions that prove contracts and catch regressions), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; the "what" is too clear and specific for the 2-anchor.

3 / 5

Trigger Term Quality

"assertions" and "regressions" are terms developers naturally use, but common variations like "tests", "unit tests", or "test coverage" are missing, matching the some-relevant-keywords anchor rather than the good-coverage one.

3 / 5

Distinctiveness Conflict Risk

It carves a distinct niche (rigorous assertion design vs. status-only tests) with only minor overlap risk against other testing/quality skills; without explicit trigger phrases it does not reach the minimal-conflict 5-anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

microsoft/waza

Path

.github/skills/test-discipline/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.