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)

64

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 ./skills/harness/fix-local-checks/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.

The body is a focused, well-sequenced workflow with explicit re-verification checkpoints and concrete guardrails. It is concise and actionable; the only blemish is mild repetition of the no-silence rules across multiple sections.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence ('A check passing is a proxy for the code being right, not proof of it'), but a few restated principles and repeated framing of the no-silence rule across sections could be tightened.

4 / 5

Actionability

Gives concrete executable guidance (run './scripts/local-checks.sh', commit with 'fix(local-checks): ...', enumerated suppression directives to avoid), with only minor gaps around exact triage commands; it is instruction-oriented rather than code-oriented, which fits this skill.

4 / 5

Workflow Clarity

A clear five-step sequence (read failures -> triage -> fix cause -> re-verify -> handle-can't-fix) with explicit validation checkpoint ('Re-run ./scripts/local-checks.sh') and feedback/stop loop for error recovery.

5 / 5

Progressive Disclosure

Well-organized sections with clear headers and no bundle files to navigate; appropriate for a single-file skill, though it is moderately long and the 'Hard nevers' list partly reiterates earlier 'You may NEVER silence a check' content rather than being split out.

4 / 5

Total

17

/

20

Passed

Description

75%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, distinct, and answers both what and when with explicit trigger phrases. It is held just below top marks by trigger-phrase phrasing and minor coverage gaps rather than by any real vagueness.

DimensionReasoningScore

Specificity

Names the concrete actions ('Reads the (remediation-rich) check failures, fixes the underlying cause, never silences a check, re-verifies, and commits') with several specific steps; minor coverage gaps keep it just below a comprehensive 5.

4 / 5

Completeness

Clearly states both what it does ('Patch the code so scripts/local-checks.sh passes') and when to use it (explicit 'Triggers -' list and 'after /implement-mainspec'); the 'when' is explicit but framed as triggers rather than a clean 'Use when...' clause, capping it just below 5.

4 / 5

Trigger Term Quality

Lists good natural trigger phrases ('fix lint', 'fix local checks', 'fix typecheck', 'make checks pass', 'post-implement polish') that users would plausibly say, though it leans slightly technical and is missing a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear narrow niche ('a narrow post-implement polish specialist', dispatcher-owned retry counter) with distinct triggers that are unlikely to fire for the wrong skill.

5 / 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.

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-factory-ai
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.