CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-local-checks

Patch the code so `scripts/local-checks.sh` passes, after /implement-mainspec — a narrow post-implement polish specialist. Reads the (remediation-rich) check failures, fixes the underlying cause, never silences a check, re-verifies, and commits. Invoked headless by the dispatcher's two-strike local-checks gate; the dispatcher owns the retry counter. Triggers - fix-local-checks, fix lint, fix local checks, fix typecheck, make checks pass, post-implement polish (project)

70

Quality

86%

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 fix-local-checks in tdg-ninja/context-specs-factory-ai

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.

The body is an actionable, well-sequenced instruction skill with explicit validation and feedback loops, well-organized into clear sections. Its main weakness is redundancy across the repeated 'never silence' sections.

Suggestions

Consolidate the three overlapping 'never silence a check' sections (the cause/silence framing, the 'You may NEVER silence a check' list, and 'Hard nevers') into one authoritative list to cut repetition.

Tighten the intro paragraphs that restate the same 'fix the cause, not the check' thesis twice before the workflow begins.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (e.g. concrete triage categories, named suppression directives), but the 'never silence a check' theme is restated across three sections ('The one thing that matters', 'You may NEVER silence a check', 'Hard nevers') with overlapping lists that could be consolidated.

4 / 5

Actionability

Gives concrete executable guidance — `./scripts/local-checks.sh`, `claude -p "/fix-local-checks <feature>"`, a commit-message example `fix(local-checks): trim query whitespace` — with specific triage buckets; minor gaps are appropriate for an instruction-only skill.

4 / 5

Workflow Clarity

A clearly numbered 5-step sequence with an explicit re-verify checkpoint (step 4: re-run the gate before committing) and a feedback loop (step 5: honest partial progress + STUCK when unfixable), matching the validate→fix→retry pattern the rubric rewards.

5 / 5

Progressive Disclosure

Single well-organized file with clear section headers and no nested references; no bundle files are needed, though at ~100 lines it exceeds the simple-skill 50-line threshold that would justify a 5.

4 / 5

Total

17

/

20

Passed

Description

92%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 is specific, third-person, and clearly answers both what the skill does and when to invoke it, with a concrete trigger phrase list. It carves out a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Patch the code so `scripts/local-checks.sh` passes', 'Reads the ... check failures', 'fixes the underlying cause', 'never silences a check, re-verifies, and commits' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly states both the 'what' (patch code so the gate passes by fixing the underlying cause, re-verify, commit) and the 'when' via a concrete 'Triggers -' list, satisfying both halves explicitly.

5 / 5

Trigger Term Quality

Explicit trigger phrases like 'fix lint', 'fix local checks', 'fix typecheck', 'make checks pass' are natural things a user would say; coverage is good though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Scoped to a tight niche — 'after /implement-mainspec', 'narrow post-implement polish specialist', invoked by 'the dispatcher's two-strike local-checks gate' — with distinct triggers and minimal overlap risk.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
tdg-ninja/context-specs-claude-code
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.