CtrlK
BlogDocsLog inGet started
Tessl Logo

help

Help deprecated skill

48

Quality

50%

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

100%

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 tight, well-structured deprecation redirect that gives concrete replacement commands and an unambiguous single action. It is concise, actionable, and appropriately organized for a skill of this size.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a one-line status, a single concrete redirect, and no padding or explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

It names three concrete, copy-paste-ready replacements ('$omx-setup', 'omx setup', 'omx doctor') and maps them to setup/install/troubleshooting, giving fully specific executable guidance rather than vague direction.

3 / 3

Workflow Clarity

This is a single-action skill whose action is unambiguous (do not invoke; route to the named commands), and no destructive/batch operations are involved, so per the simple-skills note workflow clarity scores 3.

3 / 3

Progressive Disclosure

The content is well under 50 lines with a clear heading and needs no external references; per the simple-skills note this is well-organized enough to score 3 without bundle files.

3 / 3

Total

12

/

12

Passed

Description

0%

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, natural triggers, or what/when guidance, failing every dimension. Per the judging guidelines it is scored strictly on what is stated, so its intentionally deprecated nature earns no credit.

Suggestions

State the redirect explicitly in the description, e.g. 'Deprecated: do not invoke. Use $omx-setup, omx setup, or omx doctor for setup, install, and troubleshooting.'

Add a 'Use when...' style clause clarifying that this skill should never be routed to and where to go instead, so the what/when are explicit.

Include the concrete replacement trigger terms ($omx-setup, omx doctor) so users and routing have distinguishable, non-conflicting keywords.

DimensionReasoningScore

Specificity

The description 'Help deprecated skill' names no concrete actions at all, matching the vague/abstract anchor ('Helps with documents'); it conveys only a status, not capabilities.

1 / 3

Completeness

It answers neither 'what does this do' nor 'when should Claude use it'; there is no 'Use when...' clause and the what/when are both missing, capping completeness at the floor.

1 / 3

Trigger Term Quality

No natural keywords a user would say when needing this skill appear; 'deprecated skill' is a status label rather than a trigger phrase users naturally utter.

1 / 3

Distinctiveness Conflict Risk

'Help deprecated skill' is highly generic and would conflict with many help-oriented skills, matching the 'would conflict with many skills' anchor.

1 / 3

Total

4

/

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.