CtrlK
BlogDocsLog inGet started
Tessl Logo

help

Help deprecated skill

48

Quality

51%

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

Quality

Content

86%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 appropriately lean deprecation notice that concretely redirects to three named alternatives and assumes Claude's competence without over-explaining. Its only weakness is that it offers a redirect rather than actionable task guidance, which is expected for a deprecated skill.

DimensionReasoningScore

Conciseness

The body is a single terse paragraph naming the replacement commands with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor where every token earns its place.

5 / 5

Actionability

It gives concrete, executable redirection targets ('$omx-setup', 'omx setup', 'omx doctor'), which is mostly executable guidance; it stops short of 5 only because the guidance is a redirect rather than copy-paste task code covering common cases.

4 / 5

Workflow Clarity

As a simple single-purpose skill the instruction is unambiguous (do not invoke; use the named alternatives), giving a clear sequence-free directive; it is not a 5 because there is no explicit validation or recovery step, though none is strictly required for a redirect.

4 / 5

Progressive Disclosure

The skill is well under 50 lines with no need for external references, and the brief content is organized under a clear heading; per the simple-skill exception this warrants the top score for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

17%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 minimal and vague, naming only that this is a deprecated help skill without concrete capabilities, natural trigger terms, or a usage condition. It reads as a placeholder rather than a usable trigger description.

Suggestions

Add a concrete 'Use when...' clause (or equivalent trigger guidance) so it is clear when, if ever, this skill should surface.

Replace the generic word 'Help' with the specific capability or topic the skill originally covered to reduce overlap with other help skills.

State the deprecation status explicitly in the description (e.g., 'Deprecated: use ... instead') so the description alone communicates the redirect.

DimensionReasoningScore

Specificity

"Help deprecated skill" names the domain (a deprecated help skill) but provides no concrete actions, matching the anchor that names a domain with minimal or generic actions; it does not reach 3 because no specific capabilities are listed.

2 / 5

Completeness

It offers only a vague "what" ("Help deprecated skill") and entirely lacks a "when"/"Use when..." clause, which per the guidelines caps completeness well below the midline; it is not a 1 only because a recognizable domain is named.

2 / 5

Trigger Term Quality

The phrase contains no natural keywords a user would say to trigger this skill, only the generic word "Help"; it fails to provide any natural trigger language, matching the lowest anchor.

1 / 5

Distinctiveness Conflict Risk

The generic term "Help" is very broad and would overlap with many help-oriented skills; it is not a 1 because it is narrowed slightly by the "deprecated" qualifier, but conflict risk remains high.

2 / 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.