CtrlK
BlogDocsLog inGet started
Tessl Logo

visual-verdict

Visual Verdict deprecated skill

48

Quality

50%

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/visual-verdict/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 efficient, clear deprecation notice that redirects to `$visual-ralph` with minimal tokens and unambiguous guidance. It loses only a point on actionability for not specifying how the passed task arguments flow to the replacement.

DimensionReasoningScore

Conciseness

The body is a lean deprecation notice — 'Hard-deprecated. Do not invoke or route this skill. Use `$visual-ralph` directly' — with no padding or over-explanation; every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

It gives a concrete, executable redirect ('Use `$visual-ralph` directly') which is mostly executable guidance, but it stops short of spelling out how the supplied task arguments should be handled by the replacement, leaving a minor gap.

4 / 5

Workflow Clarity

For a single-purpose deprecation/redirect skill, the one action (do not use this; use `$visual-ralph`) is unambiguous, and the simple-skill exception applies since no destructive or batch operation requires validation checkpoints.

5 / 5

Progressive Disclosure

The body is under 50 lines and needs no external references to communicate its deprecation purpose; it is well-organized with a clear statement plus redirect, satisfying the simple-skill exception for a score of 5.

5 / 5

Total

19

/

20

Passed

Description

7%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 a bare deprecated label that fails to convey any capability or trigger guidance, scoring at the floor on specificity, trigger quality, and completeness. Its only redeeming trait is the distinct 'Visual Verdict' name that limits generic conflict risk.

Suggestions

If the skill must remain, replace the description with what it did and explicit 'Use when...' trigger phrases, even while marking it deprecated.

State concrete actions and natural synonyms so users (and routing) have real keywords to match against.

Make the distinctiveness explicit by contrasting the deprecated path against the replacement `$visual-ralph` workflow.

DimensionReasoningScore

Specificity

The description 'Visual Verdict deprecated skill' names only a label and describes no concrete actions whatsoever; it is pure abstract language with no capabilities stated, matching the score-1 anchor and falling below 'Processes PDF files' which at least implies an action.

1 / 5

Completeness

It states neither what the skill does nor when to use it; there is no 'Use when...' guidance and the 'what' is just a deprecated label, so both dimensions are missing per the score-1 anchor.

1 / 5

Trigger Term Quality

It contains no natural keywords a user would say when they need this skill — 'Visual Verdict deprecated skill' is technical labelling, not user-facing trigger language.

1 / 5

Distinctiveness Conflict Risk

'Visual Verdict' is a distinct product/workflow name rather than generic language, so it is somewhat distinguishable, yet the description gives no triggers that would prevent overlap with the replacement `$visual-ralph` workflow.

3 / 5

Total

6

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.