CtrlK
BlogDocsLog inGet started
Tessl Logo

ralph-init

Ralph Init deprecated skill

58

Quality

66%

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/ralph-init/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a well-crafted deprecation redirect: terse, concrete, and unambiguous about what to do instead and when. It fully satisfies the rubric's provisions for simple, single-purpose skills across conciseness, actionability, workflow clarity, and structure.

DimensionReasoningScore

Conciseness

The three-line body is maximally lean—"Hard-deprecated. Do not invoke or route this skill. Use `$ralph` directly after PRD/test-spec planning is complete."—with no padding or concepts Claude already knows, matching the score-3 anchor where every token earns its place.

3 / 3

Actionability

It gives a concrete, executable directive—use `$ralph`—with the precondition (after PRD/test-spec planning) stated, which is fully actionable guidance rather than vague direction, matching the score-3 anchor.

3 / 3

Workflow Clarity

This is a single unambiguous action (do not invoke; use `$ralph` after planning) in a sub-50-line single-purpose skill, which the rubric's simple-skill note allows to score 3 when the action is clear and well-organized.

3 / 3

Progressive Disclosure

The body is under 50 lines with a clear heading and short prose and no need for external references, which the rubric allows to score 3 for simple skills with well-organized sections; no bundle files exist to verify further.

3 / 3

Total

12

/

12

Passed

Description

32%

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 deprecation stub rather than a capability description: it names the skill's domain but states no actions, gives no usage trigger, and signals non-use. It is appropriately distinct by name yet fails the completeness and specificity expected of an active skill description.

Suggestions

Even for a deprecated skill, state a concrete capability in the description (e.g., what Ralph Init did) so the entry is self-explanatory.

Add an explicit trigger clause or, for a deprecation, a clear 'Do not use; use $ralph instead' directive in the description so the 'when' is explicit.

Replace the generic 'deprecated skill' tail with a distinguishing phrase that separates it from other skills beyond the proper-noun name.

DimensionReasoningScore

Specificity

The description "Ralph Init deprecated skill" names a concrete domain ("Ralph Init") but lists no actions or capabilities whatsoever, fitting the score-2 anchor of naming a domain without being comprehensive rather than the fully-vague score-1 anchor.

2 / 3

Completeness

It does not describe any capability (the "what" is merely "deprecated skill") and provides no "when to use" trigger guidance—in fact it directs against use—matching the score-1 anchor where both what and when are missing or very weak.

1 / 3

Trigger Term Quality

"Ralph Init" is a natural proper-noun keyword a user would actually say, but no common variations or trigger phrasing are present, matching the score-2 anchor of having some relevant keywords while missing variations.

2 / 3

Distinctiveness Conflict Risk

The distinct proper-noun "Ralph Init" gives it a recognizable niche unlikely to collide, but the generic "deprecated skill" tail and absence of trigger guidance keep it at score-2 rather than a fully-distinct score-3.

2 / 3

Total

7

/

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.