CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-fixing

Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken"), or completes implementation and wants tests passing.

Quality

82%

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

The canonical home for this skill is test-fixing in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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.

A well-structured, actionable test-fixing workflow with explicit validation loops at both the per-group and final-suite level, which is exactly what a batch-fixing skill needs. The main weakness is redundancy: the 'When to Use' and 'Best Practices' sections largely duplicate the description and the systematic-approach steps.

Suggestions

Merge or delete the 'Best Practices' section — every bullet ('Fix one group at a time', 'Run focused tests after each fix', "Use `git diff` to understand recent changes", 'Don't move to next group until current passes') already appears in the 'Systematic Fixing Process' steps.

Trim the 'When to Use' list, which repeats the frontmatter description verbatim; keep only the one addition it makes ('Mentions CI/CD failures due to tests').

Add a one-line note to substitute the project's actual test runner (e.g., npm test, go test) instead of assuming `make test` and `uv run pytest`, since the commands are otherwise copy-paste ready.

DimensionReasoningScore

Conciseness

The core workflow sections are lean lists, but the 'Best Practices' section ('Fix one group at a time', 'Run focused tests after each fix', "Use `git diff` to understand recent changes", 'Don't move to next group until current passes') restates rules already given in 'Systematic Fixing Process', and 'When to Use' duplicates the frontmatter description verbatim. Mostly efficient but could be tightened — more than minor trimming needed, so not a 4; not padded explanation of known concepts, so not a 2.

3 / 5

Actionability

Concrete copy-paste commands are given (`make test`, `git diff`, `uv run pytest tests/path/to/test_file.py -v`, `uv run pytest -k "pattern" -v`) plus specific error types (ImportError, AttributeError, AssertionError) and a worked example workflow. Minor gap: the guidance hardcodes a make/uv/pytest toolchain with no note to adapt to other runners, so not fully a 5; well beyond high-level hints, so not a 3.

4 / 5

Workflow Clarity

A clear five-phase sequence with explicit validation checkpoints and a feedback loop: 'Run subset of tests for this group', 'Ensure group passes before moving on', and final verification 'Run complete test suite: `make test`' / 'Verify no regressions', plus a prioritization strategy (infrastructure → API changes → logic). This is a batch operation and validation IS present at both per-group and final level, so the batch cap does not apply and it matches the top anchor rather than the 4.

5 / 5

Progressive Disclosure

No bundle files exist and the body is self-contained with well-organized sections; nothing clearly belongs in a separate file. However, at ~113 lines it exceeds the under-50-line simple-skill exception for a 5, and the redundant 'Best Practices'/'Example Workflow' material is a minor organization gap — fits 'good structure, most content appropriately placed' rather than 'clear overview with well-signaled references'.

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 that clearly states what the skill does and when to use it, with concrete quoted trigger phrases users would naturally say. Minor room for improvement: adding CI/build-failure trigger variants and fixing the grammar slip 'Use when explicitly asks' (missing 'the user').

DimensionReasoningScore

Specificity

'Systematically identify and fix all failing tests using smart grouping strategies' names the domain plus several concrete actions (identify failures, group them, fix them), comparable to 'Extracts text from PDF files, fills forms, converts pages to images'. Not a 5 because coverage has gaps (no mention of prioritization or verification of the suite), and not a 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ('Systematically identify and fix all failing tests using smart grouping strategies') and when ('Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken")...') with concrete quoted trigger phrases — a direct match to the top anchor's example pattern, not merely the 4's 'when could be more explicit'.

5 / 5

Trigger Term Quality

Quoted natural phrases users would actually say: 'fix these tests', 'make tests pass', 'tests are failing', 'test suite is broken'. Not a 5 because common variations like CI/build failure phrases are absent and the final trigger ('completes implementation and wants tests passing') describes a state rather than a phrase a user would say; clearly above the 3 anchor's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

Test fixing is a clear niche with distinct triggers, but 'reports test failures' / 'tests are failing' could plausibly also match a closely related debugging or CI-triage skill — minor overlap risk with closely related skills, the 4 anchor. Not a 5 because the overlap is conceivable; not a 3 because the quoted triggers are specific to this skill's purpose.

4 / 5

Total

17

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/test-fixing/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.