CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-engineered diagnostic skill body: complete executable scaffolding for source syncing, explicit verdict criteria, evidence-bound reporting, escalation and stop conditions. The weaknesses are localized — one verbose Astra paragraph, a few directional rather than scripted probes, and an inline bash block that a scripts/ bundle file would offload.

Suggestions

Move the version-floor provenance detail (backport commit 5cc1c94b8e, the 'git log -S gpt-6-astra' reproduction commands) into a reference file or trim it, keeping only the operational rule: codex >= 0.153.1 and gpt-6-astra present-or-absent in models_cache.json.

Give exact commands for the remaining directional steps: a TOML parse check for config.toml and a concrete non-interactive Codex invocation for the runtime probe.

Extract the source-sync bash block into a scripts/sync-sources.sh bundle file (parameterized by LAZYCODEX_SOURCE_ROOT) so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with earned tokens — exact commands, paths, and PASS/WARN/FAIL thresholds — and explains nothing Claude already knows. It misses 5 mainly because step 2's Astra paragraph carries provenance detail Claude doesn't need at diagnosis time ('backport commit 5cc1c94b8e', full 'git log -S gpt-6-astra' reproduction instructions) that could be trimmed or moved to a reference, and embedded version floors like 0.153.1 are time-sensitive facts not placed in a deprecated/old-patterns section.

4 / 5

Actionability

Mostly executable: a copy-paste-ready bash block for source syncing, and exact probes ('codex --version', 'find ... -path "*/.codex-plugin/plugin.json"', 'grep -c gpt-6-astra .../models_cache.json', 'gh issue list ... --search'). Not 5 because several steps leave the command unspecified — 'config.toml exists and parses' gives no parse command, 'a trivial non-interactive Codex invocation that loads the plugin' names no invocation, and step 3's installer-vs-local comparison is directional rather than scripted.

4 / 5

Workflow Clarity

The 8-step sequence is explicit with validation checkpoints and feedback loops throughout: cached checkouts are validated and quarantined before reuse, corrupt clones trigger re-clone, verdict thresholds are pinned (PASS/WARN/FAIL with the exact 0.153.1 floor), 'a clean exit with warnings is WARN, not PASS', known issues are matched before re-diagnosing, unexplained probe failures escalate to '$omo:debugging', and the Stop Conditions forbid declaring healthy without captured evidence.

5 / 5

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ bundle) with well-labeled sections — Required Workflow, Doctor Report Template, Follow-up Routing, Stop Conditions — so nothing is buried or nested. Not 5 because the ~45-line inline source-sync bash script and the Astra version-floor details are content that could live in scripts/ or a reference file to keep SKILL.md an overview, though at 120 lines the file remains fully navigable.

4 / 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: it states a concrete purpose in third person, then gives an explicit 'Use whenever' clause packed with natural trigger phrases including product aliases and symptom language. The only minor gap is that the individual diagnostic checks are summarized under 'diagnose/audit/compare' rather than listed.

DimensionReasoningScore

Specificity

Concrete actions are named — 'Diagnose LazyCodex and Codex CLI installation health against the latest sources' and 'audited and compared with the latest LazyCodex and Codex code' — plus what the diagnosis covers (install, update, config change, stale/drifted/broken setup). It stays below 5 because the specific diagnostic acts (version comparison, config/plugin wiring checks, drift detection) are only implied by 'diagnose' and 'audited', not enumerated like the anchor-5 example.

4 / 5

Completeness

Explicitly answers both: 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'. This matches the anchor-5 example's structure of what-statement followed by 'Use when' with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and product aliases: 'doctor or health check', 'LazyCodex', 'lazycodex-ai', 'omo-codex', 'Codex behaves oddly', 'stale, drifted, or broken setup', 'install, update, or config change'. Not below 5 because users would plausibly say nearly every one of these phrases when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: product-specific names (LazyCodex, lazycodex-ai, omo-codex, Codex CLI) plus a narrow diagnostic role. It would not trigger for general Codex usage questions since the triggers are all health/install-oriented, so it sits comfortably at the anchor-5 example's level.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
code-yeongyu/oh-my-openagent
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.