CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-tests-fail-without-fix

Verifies tests catch the bug. Auto-detects test type (UI tests, device tests, unit tests) and dispatches to the appropriate runner. Supports two modes - verify failure only (test creation) or full verification (test + fix validation).

Quality

78%

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/verify-tests-fail-without-fix/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 operational skill whose workflow and executable guidance are excellent, with risky operations explicitly guarded. Its main weakness is token efficiency: several sections restate the same information, and supplementary documentation that belongs in reference files is inlined in SKILL.md.

Suggestions

Remove the redundancy between 'What It Does', 'Expected Output', and Step 4 of the Workflow — keep one authoritative explanation of each mode's result semantics and link or point to the script's generated report for output details.

Move the output-file listing, directory-tree example, and troubleshooting table into a references/ file (e.g. references/troubleshooting.md), keeping only a short pointer in SKILL.md.

State the inverted pass/fail semantics once in the dedicated 'CRITICAL' section and reference it from Steps 3–4 rather than repeating the table and reminders.

DimensionReasoningScore

Conciseness

Mostly efficient and skill-specific, but noticeably redundant: 'What It Does' restates the workflow steps, the ASCII 'Expected Output' boxes duplicate Step 4's explanations, and the output-directory tree plus 'Output Files' table document the same artifacts; the inverted-semantics point is made three times.

3 / 5

Actionability

Fully executable, copy-paste-ready pwsh commands with exact script paths and parameters for both modes, explicit terminal markers to match (VERIFICATION PASSED/FAILED), a concrete troubleshooting table, and a complete optional-parameters section covering the common cases.

5 / 5

Workflow Clarity

Clear four-step sequence with explicit validation checkpoints (exact terminal markers, error/timeout routed to Blocked), instruction to wait for completion rather than act on partial output, and safe ownership of the risky worktree-revert operation with error-recovery guidance via the troubleshooting table.

5 / 5

Progressive Disclosure

The heavy script logic is properly externalized and invoked via a clear one-level-deep path that matches the actual bundle file (scripts/verify-tests-fail.ps1), and sections are well organized; however, everything else is inline — troubleshooting, output-file documentation, and the ~80-line directory-tree example could live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

66%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 solid, third-person description that names the domain, concrete actions, and both operating modes, but it lacks an explicit 'Use when...' trigger clause and a few natural trigger synonyms. Adding when-to-use guidance and disambiguation from adjacent test-running skills would lift it into the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when validating that new or changed tests reproduce a reported bug before a fix is applied, or when confirming a fix makes the failing tests pass.'

Include natural trigger variations users would actually say — 'tests fail without the fix', 'reproduce the bug', 'test-first/TDD', 'regression check' — to broaden keyword coverage.

State the without-fix/with-fix semantics in the description to sharpen the niche and reduce overlap with generic run-tests or write-tests skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Auto-detects test type (UI tests, device tests, unit tests)', 'dispatches to the appropriate runner', two named modes), but the runner dispatch is generic and specific runners are not named, leaving minor gaps in coverage.

4 / 5

Completeness

The 'what' is clear (verifies tests catch the bug, auto-detects type, dispatches to a runner), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the mode parentheticals only weakly imply when to use it, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would say in this domain ('tests catch the bug', 'UI tests, device tests, unit tests', 'test creation', 'fix validation'), but misses common variations such as 'reproduce the bug', 'test-first', or 'regression'.

4 / 5

Distinctiveness Conflict Risk

The bug-catching verification niche is mostly distinct from test-writing or code-review skills, but 'Verifies tests' carries minor overlap risk with general test-running skills since no explicit disambiguation is stated.

4 / 5

Total

15

/

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.

Repository

dotnet/maui

Path

.github/skills/verify-tests-fail-without-fix/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.