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.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, highly actionable diagnosis skill with executable code, explicit validation checkpoints, and clear routing. Conciseness is slightly reduced by rationale prose, and progressive disclosure is good though the single-file body carries a lot of inlined detail.

Suggestions

Trim explanatory rationale clauses (e.g. 'so a cached checkout cannot go stale') to tighten conciseness without losing the command logic.

Consider moving the large source-sync bash block and the report template into a referenced script/reference file so the SKILL.md body stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, but a few rationale clauses ('so a cached checkout cannot go stale', 'so an incomplete .git directory cannot poison diagnosis') add explanatory padding that could be trimmed.

4 / 5

Actionability

Fully executable: complete bash functions, exact file paths, concrete `gh`/`git`/`codex` commands, and a copy-paste-ready report template covering the common diagnosis cases.

5 / 5

Workflow Clarity

Clear 8-step sequence with explicit validation checkpoints (valid_source_checkout, recover_corrupt_source_checkout, 'clean exit with warnings is WARN, not PASS', 'Capture stderr verbatim') and feedback loops; the skill is explicitly diagnose-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Required Workflow, Report Template, Follow-up Routing, Stop Conditions) with no nested references, but the body inlines a substantial amount of dense procedural detail that, with bundle files, could be split out for easier navigation.

4 / 5

Total

18

/

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, third-person description that clearly states what the skill does and gives rich, natural trigger phrases including product synonyms. The only minor weakness is that the named actions overlap somewhat rather than covering distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'Diagnose ... installation health', 'compare ... against the latest sources', 'audited and compared' — but compare/audit/compared overlap rather than enumerating distinct actions, leaving minor coverage gaps.

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 ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including product-name synonyms users would actually say — 'doctor or health check', 'LazyCodex', 'lazycodex-ai', 'omo-codex', 'Codex behaves oddly', 'stale, drifted, or broken setup'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (LazyCodex/Codex install doctoring) with distinct, product-specific triggers that are unlikely to fire for unrelated skills.

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.

Validation14 / 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/lazycodex
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.