CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visual-repair

Every six hours, look at the carnival screens owed a review in its ledger, in a real headless browser, against the visual design baseline, and repair the worst one in one small draft pull request. Use when running the visual repair maintenance loop. Inspects every run, even with other pull requests open, and defers a repair only when an open pull request changes the same or a shared file.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An exceptionally actionable, well-guarded operating manual: every step carries an executable command, explicit stop conditions, and validation feedback loops, with no filler. The only costs are minor duplication of the shared-file mapping and a single-file structure that could offload detail to a reference.

DimensionReasoningScore

Conciseness

The body is dense and entirely project-specific — it assumes competence and never explains concepts Claude already knows — but the shared-file conflict mapping ("index.html, src/main.ts, src/style.css, src/carnival/" plus imported-module and unplaceable-file rules) is stated in full both in the Guards plan section and again in Coverage, and a few interval paragraphs meander. Minor trims available, matching anchor 4.

4 / 5

Actionability

Fully executable guidance throughout: `node scripts/visual/ledger.mjs plan`, `VISUAL_REV=<plan head> scripts/visual/run-capture.sh <dir> <batch routes>`, `node scripts/visual/pixels.mjs <dir>/*.png`, `npm run format` and `npm run check`, `tessl action trigger visual-repair --request-id <stable id>`, plus exact branch (`tessl/visual-repair-<route>-<yyyymmddhhmmss>`), PR title, marker, screenshot-path and review-JSON formats. The common review-then-repair path is copy-paste ready.

5 / 5

Workflow Clarity

"Follow these in order. Any 'stop' ends the run with the ledger unchanged" gives explicit sequencing, and validation checkpoints with recovery loops appear at every phase: stop on Chromium failure, on cut-off GitHub lists, on refused fast-forward pushes; verify captures a second way with pixels.mjs; record findings before repairing; re-run format/check and re-capture, with "the repair is done only when the after screenshots clear the findings without new ones" and "two attempts at most".

5 / 5

Progressive Disclosure

Sections (The ledger, Guards, Coverage, Look, Repair, Run output) are well-organized and external references (`docs/visual-baseline/README.md`, `docs/pr-writing.md`, the project's scripts/visual/*) are one level deep and clearly signaled at point of use — no bundle files exist to nest. Not 5 because the entire ~180-line operating manual lives in SKILL.md with no split of the detailed plan-action and coverage rules into a reference file.

4 / 5

Total

18

/

20

Passed

Description

71%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 specific, well-bounded description with a clear what and an explicit Use-when clause and near-zero conflict risk. Its main weakness is trigger coverage: the single self-referential trigger phrase leaves natural variations unsaid.

Suggestions

Broaden the 'Use when' clause with concrete trigger phrases a user would naturally say, e.g. "Use when running the visual repair maintenance loop, checking screens against the visual baseline, or reviewing carnival screenshots".

Mention the monitor/record behaviors (e.g. "records findings in its ledger and monitors its own open repair pull request") so the what-coverage is comprehensive, not just review and repair.

DimensionReasoningScore

Specificity

Names several concrete actions — "look at the carnival screens owed a review in its ledger, in a real headless browser, against the visual design baseline", "repair the worst one in one small draft pull request", "inspects every run", "defers a repair" — with cadence ("Every six hours") making scope concrete. Not 5: recording findings and monitoring an open repair pull request are uncovered; not 3: well beyond 1-2 actions.

4 / 5

Completeness

Both parts are present: a clear what ("look at the carnival screens owed a review... and repair the worst one in one small draft pull request") and an explicit when ("Use when running the visual repair maintenance loop"). Not 5 because the when is a single narrow phrase rather than the multiple concrete trigger phrases the top anchor requires.

4 / 5

Trigger Term Quality

The only explicit trigger is "Use when running the visual repair maintenance loop", which is self-referential (the skill's own name), and natural variations a user might say — visual regression, screenshot review, checking the screens — are absent. Domain keywords (carnival screens, visual design baseline, headless browser) exist, but coverage of natural trigger phrases is thin, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

"carnival screens", "its ledger", "visual repair maintenance loop", "one small draft pull request" carve out a clear project-specific niche with distinct triggers; virtually no overlap with any other skill's description. Clearly matches the anchor-5 example of minimal conflict risk.

5 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 8 missing, 8 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

guypod/carnival-evolution-20261028

Path

tessl-factory/skills/visual-repair/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.