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

89%

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

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 workflow: tightly sequenced, evidence-bound, with explicit validation, error-recovery loops, and safety guardrails, and almost entirely executable commands. The main improvements are closing two concrete gaps (the runtime-probe command, a drift-diff command) and trimming or offloading the Astra provenance detail.

Suggestions

Give the exact command for the runtime probe (step 4) — e.g. the specific non-interactive `codex exec` invocation to run with the configured default model — since it is currently described only as "a trivial non-interactive Codex invocation".

Add a concrete comparison command to step 5 (e.g. a `diff -r` or checksum loop between the installed payload and the same files at the installed version) so drift detection is executable rather than directed.

Move the Astra provenance research (the `git log -S gpt-6-astra` and `tag --contains 5cc1c94b8e` reproduction commands and the rust-v0.153.1/backport detail) into a small references/ file, keeping only the 0.153.1 floor and verdict rule inline.

DimensionReasoningScore

Conciseness

The body is imperative throughout with no teaching of known concepts and fetches latest versions dynamically ("gh release view --repo openai/codex"), but the Astra readiness step embeds provenance-reproduction commands ("git -C <codex-clone> log --format='%h %d' -S gpt-6-astra", "tag --contains 5cc1c94b8e") that are not needed for the diagnosis itself, and the CODEX_HOME default is stated twice. This is efficient-with-minor-trimmable-material rather than lean where every token earns its place.

4 / 5

Actionability

Mostly copy-paste-ready: the full sync_latest_source bash script with fallbacks, "codex --version", "find ... -path '*/.codex-plugin/plugin.json'", "grep -c gpt-6-astra", "gh issue list --search", and "npm install -g @openai/codex@latest", plus explicit PASS/WARN/FAIL thresholds. Minor gaps keep it below the top anchor: the runtime probe is described only as "a trivial non-interactive Codex invocation" with no actual command, and the drift-comparison step gives no concrete diff command.

4 / 5

Workflow Clarity

Eight coherently sequenced steps (sources → inventory → config → probes → drift → known issues → escalation → report) with explicit validation checkpoints ("valid_source_checkout" gating, corrupt-cache quarantine, re-sync on every run, "a clean exit with warnings is WARN, not PASS", "Capture stderr verbatim", explicit Astra PASS/WARN verdict rules), error-recovery feedback loops (gh-to-git clone fallback, default-branch fallbacks), and a "Do not" checklist. Every verdict must cite evidence.

5 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single self-contained document with clear sections (Required Workflow, Doctor Report Template, Follow-up Routing, Stop Conditions) that is easy to navigate. It is above the simple-skill threshold (~124 lines), and the Astra provenance block and the sync script are candidates for a references/ file, which keeps it at good-structure rather than the top anchor.

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: third-person, concrete about what it does (diagnose, audit, compare against latest sources) and exhaustive about when to trigger it, including product-name synonyms and natural user phrasings. The only weakness is modest breadth in the action list — it omits the report and remediation outputs the skill actually produces.

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" — which is several specific actions with only minor gaps (the PASS/WARN/FAIL report and remediation outputs are not mentioned). It is above anchor 3 because the actions go beyond minimal and cover the doctoring niche comprehensively, but below anchor 5 because it does not enumerate multiple distinct capabilities.

4 / 5

Completeness

"Diagnose LazyCodex and Codex CLI installation health against the latest sources" explicitly answers what, and "Use whenever the user asks for a doctor or health check, says LazyCodex... or wants the local install audited" explicitly answers when with concrete trigger phrases. Both halves are present and explicit, matching the top anchor.

5 / 5

Trigger Term Quality

Triggers include "doctor or health check", the product name variants "LazyCodex, lazycodex-ai, omo-codex", "behaves oddly after an install, update, or config change", and "stale, drifted, or broken setup" — natural phrasings and synonyms users would actually say. This matches the comprehensive-synonyms anchor; no common natural variation is missing.

5 / 5

Distinctiveness Conflict Risk

Product-name triggers ("LazyCodex", "lazycodex-ai", "omo-codex", "Codex") carve a clear install-health niche with minimal conflict risk, and the potentially broad "Codex behaves oddly" is qualified by "after an install, update, or config change". Fits the clear-niche anchor; no neighboring anchor matches better.

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/components/lcx/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.