CtrlK
BlogDocsLog inGet started
Tessl Logo

doctor

Diagnose and fix oh-my-codex installation issues

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

68%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.

A highly actionable, well-structured diagnostic runbook with copy-paste bash and explicit severity criteria, weakened mainly by missing validation feedback loops around its destructive auto-fixes and some padded prose notes.

Suggestions

Add explicit validation checkpoints after destructive fixes (e.g. re-run Step 1 to confirm cache state, verify AGENTS.md marker present after write) with a fix-and-retry loop.

Trim the dense "Remember:"/companion-metadata sentences in Steps 1 and 6 to the minimum needed for diagnosis.

Consider moving the verbose auto-fix scripts into a reference file referenced one level deep to improve progressive disclosure toward 5.

DimensionReasoningScore

Conciseness

The body is mostly actionable, but dense "Remember:"/companion-metadata prose notes in Steps 1 and 6 are padded and could be trimmed without losing guidance, fitting the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

Each step ships copy-paste-ready bash (find/npm view/ls/grep/rm) with explicit per-step diagnosis criteria (INFO/WARN/CRITICAL) and concrete fix scripts, fully covering the common cases.

5 / 5

Workflow Clarity

Diagnostics are well sequenced, but destructive/batch fixes (global cache clear, rm -rf agents/commands/skills) lack validate-then-retry checkpoints; per the rubric this caps workflow_clarity at 3 despite the confirmation gate.

3 / 5

Progressive Disclosure

Sections are well organized (canonical root, Steps 1-6, Report Format, Auto-Fix, Post-Fix) but all content is inline with no bundle files or one-level references; over 50 lines so the simple-skill 5-exception does not apply, capping at 4.

4 / 5

Total

15

/

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 specific and distinctive but omits any explicit "Use when…" trigger guidance, which caps completeness and limits trigger-term coverage. Adding a trigger clause would raise the lower-scoring dimensions.

Suggestions

Append a trigger clause, e.g. "Use when oh-my-codex setup is broken, stale, or behaving unexpectedly after install/update".

Add natural user phrasings like "setup", "not working", or "broken install" alongside "installation issues".

Optionally enumerate concrete fix actions (cache cleanup, hook removal, AGENTS.md refresh) to lift specificity above 3.

DimensionReasoningScore

Specificity

"Diagnose and fix oh-my-codex installation issues" names the domain plus two concrete actions ("Diagnose", "fix"), matching the 1-2-actions anchor; it is not a single generic verb (so above 2) but does not list several specific actions (so below 4).

3 / 5

Completeness

It clearly states what the skill does (diagnose and fix installation issues) but provides no "Use when…" trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

"installation issues" is a relevant, somewhat natural phrase, but the description lacks common variations/synonyms users say (e.g. "setup", "broken", "not working"), fitting the some-keywords-but-missing-variants anchor.

3 / 5

Distinctiveness Conflict Risk

The narrow "oh-my-codex installation" niche is highly specific with minimal overlap risk against other skills, matching the clear-niche/minimal-conflict anchor.

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.