CtrlK
BlogDocsLog inGet started
Tessl Logo

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

62

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/visual-ralph/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 well-sequenced, actionable orchestration guide with strong validation checkpoints, but it is slightly verbose in places and is monolithic rather than progressively disclosed across reference files.

Suggestions

Tighten explanatory asides (e.g., the imagegen-helper rationale and repeated pixel-diff clarifications) to respect the token budget.

Extract stable, reusable material such as the handoff template and verdict shape into a single one-level-deep reference file to enable progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, but includes explanatory padding that could be tightened — e.g. the rationale paragraph about why the imagegen continuation helper exists and repeated re-explanation that pixel diff is only secondary evidence.

2 / 3

Actionability

Provides concrete, actionable guidance: an executable `omx imagegen continuation` command block, an exact `$ralph` handoff template that is copy-paste ready, and a defined verdict shape (score, verdict, differences[], suggestions[]).

3 / 3

Workflow Clarity

The 7-step workflow is clearly sequenced with explicit validation checkpoints — a hard user-approval gate (step 3), a Visual Ralph verdict loop with a 'score < 90' retry threshold (step 5), and a completion checklist with concrete pass criteria.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so all content lives inline in a single ~161-line SKILL.md; sections are well-organized, but content such as the handoff template or verdict shape is not split into one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

67%

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 and occupies a clear niche, but it relies on internal jargon for triggers and lacks an explicit 'Use when...' clause, leaving the activation condition implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when building or restyling frontend UI, cloning a live URL, or matching a generated reference image').

Reduce internal jargon in the trigger language so a user could naturally say the keywords that activate the skill.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'orchestration for frontend UI', 'using $ralph', 'built-in visual verdict', 'pixel-diff evidence', and 'leaves a reproducible design system' — rather than vague language.

3 / 3

Completeness

Clearly answers what the skill does, but the 'when to use it' guidance is only implied — there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Includes some relevant user-facing keywords like 'frontend UI', 'references', and 'live URL', but leans heavily on internal jargon ('Visual Ralph orchestration', '$ralph', 'visual verdict') that a user would not naturally say.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (frontend UI visual orchestration via $ralph) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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.