CtrlK
BlogDocsLog inGet started
Tessl Logo

visual-verdict

Visual Verdict deprecated skill

44

Quality

46%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

As a deprecation stub, the body is well-written: lean, unambiguous, and actionable in redirecting to the replacement skill. The only blemish is a leftover unfilled template token that adds minor noise.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude knows, but the leftover unfilled 'Task: {{ARGUMENTS}}' template token does not earn its place. It is not 3 because of that stray template cruft, and not 1 because the prose itself is efficient.

2 / 3

Actionability

'Do not invoke or route this skill. Use `$visual-ralph` directly' gives concrete, executable redirect guidance naming the exact replacement, matching 'fully executable/specific' guidance. It is not 2 because the instruction is complete for a deprecation stub rather than pseudocode or partial.

3 / 3

Workflow Clarity

As a simple single-purpose skill, the single action (do not invoke; use $visual-ralph) is unambiguous, so per the simple-skills note it scores 3. It is not 2 because no sequencing or validation gaps exist for a one-step redirect.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into a clear header plus a deprecation notice, satisfying the simple-skill exception. It is not 2 because there is no inline content that should be split out and no nested references.

3 / 3

Total

11

/

12

Passed

Description

7%

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 deprecation label with no functional capabilities, natural triggers, or usage guidance, making it unsuitable for routing. It scores at the floor across nearly every dimension.

Suggestions

Replace the description with a concrete statement of what the skill did and an explicit 'Use when...' trigger clause, or state plainly 'Deprecated — use $visual-ralph for visual verdict scoring.'

Add natural trigger terms a user would actually say so the skill is distinguishable during routing.

Keep third-person action voice (e.g., 'Scores visual verdicts...') instead of the generic 'deprecated skill' label.

DimensionReasoningScore

Specificity

The phrase 'Visual Verdict deprecated skill' names no concrete actions, only a label and status, matching the 'vague or no actions' anchor. It does not reach score 2 because it lists no domain actions whatsoever.

1 / 3

Completeness

The description answers neither 'what does this do' nor 'when to use it'; it only declares deprecation, matching the 'missing what OR when' anchor. It cannot reach 2 since it lacks any functional 'what' statement and has no 'Use when...' trigger guidance.

1 / 3

Trigger Term Quality

'Visual Verdict' is a skill name and 'deprecated skill' is a status, neither of which are natural keywords a user would say when needing this capability. It stays at 1 because there is no coverage of common user phrasings.

1 / 3

Distinctiveness Conflict Risk

It references a named concept ('Visual Verdict') making it somewhat specific, but the language is vague with no distinct triggers, fitting 'somewhat specific but could overlap.' It is not 1 because it is not as generic as 'Helps with documents', and not 3 because it provides no clear distinct triggers.

2 / 3

Total

5

/

12

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.