CtrlK
BlogDocsLog inGet started
Tessl Logo

ralph-init

Ralph Init deprecated skill

45

Quality

47%

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

82%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 content is an appropriately lean deprecation notice: concise, with a concrete redirect command and a clear condition for when to use the replacement. It scores well across all content dimensions given its deliberately minimal purpose.

DimensionReasoningScore

Conciseness

The three-line body ("Hard-deprecated. Do not invoke or route this skill. Use `$ralph` directly after PRD/test-spec planning is complete.") is lean and assumes Claude's competence with no padding, matching the score-5 anchor; every token earns its place.

5 / 5

Actionability

It gives a concrete, executable redirect ("Use `$ralph` directly after PRD/test-spec planning is complete") with a specific command and condition, fitting the score-4 anchor of mostly executable guidance with minor gaps; it is not score 5 because no examples cover edge cases.

4 / 5

Workflow Clarity

The single directive is unambiguous and condition-gated (after planning -> use $ralph), aligning with the score-4 anchor of a clear sequence with most checkpoints present; the simple-skill exception does not push it to 5 because this is a deprecation redirect rather than an executable task workflow.

4 / 5

Progressive Disclosure

The body is short, well-organized with a clear header, and appropriately points to the replacement (`$ralph`) with no bundle files present, matching the score-4 anchor of good structure with minor gaps; it is not score 5 because there is only a single section and no navigational references to organize.

4 / 5

Total

17

/

20

Passed

Description

12%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 deprecation label with no concrete actions, no natural trigger terms, and no use-when guidance, scoring poorly on completeness and trigger quality. It is only saved from the lowest distinctiveness score by naming a specific skill.

Suggestions

Add a concrete statement of what the skill was and an explicit redirect trigger, e.g. "Deprecated: formerly initialized Ralph. Use $ralph after PRD/test-spec planning instead."

Include a 'Use when...' style clause (or equivalent) so Claude knows when, if ever, this skill is relevant.

Replace the generic word 'skill' with a specific capability noun to raise specificity above the domain-only anchor.

DimensionReasoningScore

Specificity

The phrase "Ralph Init deprecated skill" names a specific domain (Ralph Init) but provides zero concrete actions, fitting the score-2 anchor of naming the domain with minimal/generic actions; it is not score 1 because a concrete named domain is present.

2 / 5

Completeness

The description gives only an extremely vague "what" ("deprecated skill") and no "when" guidance, matching the score-1 anchor; the missing 'Use when...' clause and absence of any concrete capability keep it from score 2.

1 / 5

Trigger Term Quality

"deprecated skill" offers no natural keywords a user would say to invoke this, matching the score-1 anchor of no natural keywords / only technical jargon; it does not reach score 2 because not even one generic user-facing trigger phrase appears.

1 / 5

Distinctiveness Conflict Risk

"Ralph Init" names a specific niche so it is somewhat distinguishable, but the bare description provides no distinct triggers, fitting the score-3 anchor of somewhat specific yet still overlapping; it is not score 4 because no clear trigger phrases establish a firm niche.

3 / 5

Total

7

/

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.