CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lcx-doctor

Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install audited and compared with the latest LazyCodex and Codex code.

Quality

91%

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

The canonical home for this skill is lcx-doctor in code-yeongyu/oh-my-openagent

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-sequenced diagnostic workflow with executable commands, explicit verdict criteria, and strong validation gates throughout. The main gap is structural: at ~120 lines with zero bundle files, the sync script and version-sensitive detail belong in scripts/references rather than inline in SKILL.md.

Suggestions

Move the ~45-line source-sync bash block into a `scripts/sync-sources.sh` bundle file and invoke it with one line, keeping SKILL.md as an overview of the workflow.

Extract the version-pinned Astra-readiness details (the 0.153.1 floor, tag rust-v0.153.1, commit 5cc1c94b8e, and the re-derivation git commands) into a `references/astra-readiness.md` file, which also isolates the time-sensitive version numbers from the evergreen workflow steps.

Tighten the long parenthetical asides in steps 2-4 (e.g. 'informational only, it doesn't change the verdict' and the recursion justification for not calling `lazycodex doctor`) into short bullet-level notes to cut redundant tokens.

DimensionReasoningScore

Conciseness

The body is dense and evidence-bound with no explanation of concepts Claude already knows, e.g. "Use GPT-5.5 style: outcome first, concise, evidence-bound" and direct commands like `codex --version`, `command -v codex`. Minor over-explanation and padding exist — the ~45-line inline sync script and long parenthetical prose in steps 2-3 (e.g. "(informational only, it doesn't change the verdict)") could be trimmed or moved — keeping it below the lean anchor at 5 but above 'mostly efficient with some unnecessary explanation' at 3.

4 / 5

Actionability

Guidance is copy-paste ready: a complete executable bash block for source syncing (clone, fetch, checkout), exact discovery commands (`find "${CODEX_HOME:-$HOME/.codex}/plugins" -path '*/.codex-plugin/plugin.json'`, `grep -c gpt-6-astra .../models_cache.json`, `gh issue list --search "<short symptom>"`), exact file paths, and a fill-in report template. Specific criteria cover the common cases (PASS/WARN/FAIL rules for Astra readiness), matching the fully-executable anchor.

5 / 5

Workflow Clarity

The 8-step Required Workflow is clearly sequenced with explicit validation checkpoints and feedback loops: checkout validation before reuse (`valid_source_checkout`), corrupt-cache quarantine and recovery, explicit verdict rules ("a clean exit with warnings is WARN, not PASS"), failure escalation to `$omo:debugging`, and a hard gate "declare healthy while any probe output was never captured" in the Do-not list. This matches the anchor with explicit validation steps and error-recovery loops; the operation is diagnostic/read-only, so the destructive-cap rule does not apply.

5 / 5

Progressive Disclosure

The skill is a monolithic single file with no bundle: no `references/`, `scripts/`, or `assets/` exist, and everything — including a ~45-line bash sync script and version-pinned details (0.153.1, commit 5cc1c94b8e) that would fit a reference file — is inlined under good section headers (Required Workflow, Doctor Report Template, Follow-up Routing, Stop Conditions). Structure is present and sections are well organized, but content that should be split out (the sync script into `scripts/`, version-specific Astra detail into a reference) is inline, matching anchor 3 rather than anchor 4's 'most content appropriately placed with clear references'.

3 / 5

Total

17

/

20

Passed

Description

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

A strong description with explicit what/when structure, natural trigger phrases including product-name synonyms, and a well-defined niche. The only minor weakness is that capability verbs (diagnose/audit/compare) could enumerate the concrete check categories for even fuller coverage.

DimensionReasoningScore

Specificity

The description names the domain ("LazyCodex and Codex CLI installation health") and several concrete actions — "Diagnose", "audited", "compared with the latest LazyCodex and Codex code" — but the verbs stay at the audit/compare level rather than enumerating the concrete sub-checks (versions, config wiring, bin links, drift), leaving minor coverage gaps. It sits above score 3 (only 1-2 actions) but below score 5's fully comprehensive action list.

4 / 5

Completeness

It explicitly answers both parts: what ("Diagnose LazyCodex and Codex CLI installation health against the latest sources") and when ("Use whenever the user asks for a doctor or health check... or wants the local install audited") with concrete trigger phrases. Not score 4 because the 'when' clause is fully explicit with multiple concrete triggers, not merely adequate.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and includes synonyms and natural user phrasing: "doctor or health check", "LazyCodex, lazycodex-ai, omo-codex", "behaves oddly after an install, update, or config change", "suspects a stale, drifted, or broken setup". These are exactly the phrases a user would naturally say, matching the anchor-5 example's breadth of synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — LazyCodex/Codex install diagnostics — with product-name-specific triggers ("lazycodex-ai, omo-codex") that no generic skill would match, minimizing conflict risk. It clearly fits the 'clear niche with distinct triggers' anchor rather than the 'minor overlap risk' anchor at 4.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/lcx-doctor/SKILL.md

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.