CtrlK
BlogDocsLog inGet started
Tessl Logo

doctor

Diagnose and fix oh-my-codex installation issues

60

Quality

70%

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 ./plugins/oh-my-codex/skills/doctor/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 body is a strong, executable task card with clear sequencing and built-in safety gates for its destructive remediation steps. Minor gains are available from removing a small redundancy and optionally externalizing the larger bash blocks.

DimensionReasoningScore

Conciseness

The body is lean bash with tight classification notes (INFO/WARN/CRITICAL) and no padding of concepts Claude already knows, fitting the score-4 anchor of efficient with minor trim opportunities. It is not a 5 because the AGENTS.md refresh step is restated near the end, a small redundancy.

4 / 5

Actionability

It provides copy-paste-ready, fully executable bash commands across diagnostics, cache inspection, hooks, remediation, and cache pruning, covering the common cases, matching the score-5 anchor. It is not a 4 because the guidance is complete and directly runnable rather than having gaps.

5 / 5

Workflow Clarity

The sequence (run diagnostics with flags, classify severities, emit the report contract, remediate gated on user confirmation and OMX-ownership, then rerun `omx doctor` with before/after evidence) is clear with validation checkpoints. It is not a 5 because remediation is presented as options rather than a strict numbered feedback loop and some safeguards (backups) are optional.

4 / 5

Progressive Disclosure

Content is well-organized into named sections (Run diagnostics, Report contract, Remediation, Exit conditions) with one-level references (templates/AGENTS.md, a WebFetch URL) clearly signaled, fitting the score-4 anchor. It is not a 5 because the diagnostic bash blocks are substantial inline content that, at ~114 lines, could be split into scripts/ for a cleaner overview.

4 / 5

Total

17

/

20

Passed

Description

57%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 clear and highly distinct but stops short of completeness: it states what the skill does without any 'when to use it' guidance. Adding an explicit trigger clause would lift its weakest dimension.

Suggestions

Append a "Use when..." clause, e.g. "Use when oh-my-codex is not installing, is missing from Codex, or plugins/hooks are not discovered."

Add natural trigger synonyms users might say, such as "install problems", "setup failure", or "Codex can't find OMX".

Expand the action list beyond diagnose/fix to concrete outcomes like "inspect plugin cache, verify hooks, repair ownership" for fuller specificity.

DimensionReasoningScore

Specificity

"Diagnose and fix oh-my-codex installation issues" names the domain and two concrete actions (diagnose, fix), matching the score-3 anchor of domain plus 1-2 actions without comprehensive coverage. It is not a 4 because only two generic verbs are listed with no further specific actions.

3 / 5

Completeness

It clearly states what the skill does ("Diagnose and fix oh-my-codex installation issues") but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric. It is not a 2 because the 'what' is clear rather than vague.

3 / 5

Trigger Term Quality

"oh-my-codex", "installation", and "issues" provide some relevant keywords, but common natural variations (e.g. "install problems", "setup", "broken", "won't load") are absent, fitting the score-3 anchor. It does not reach 4 because keyword coverage is thin rather than merely missing a few terms.

3 / 5

Distinctiveness Conflict Risk

The product-specific niche "oh-my-codex installation" gives a clear, distinct trigger with minimal overlap risk against other skills, matching the score-5 anchor. It is not below 5 because no other common skill would naturally compete for this trigger.

5 / 5

Total

14

/

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.