New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

LazyCodex Doctor

by code-yeongyu in code-yeongyu/oh-my-openagent

Audits a local LazyCodex and Codex CLI install against the latest upstream sources and reports PASS, WARN or FAIL per check without changing anything.

Custom licenceAuto-check passedAgent Workflows

Install LazyCodex Doctor

skills CLI
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install code-yeongyu/oh-my-openagent lcx-doctor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-doctor .claude/skills/lcx-doctor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lcx-doctor
GitHub stars
70k
Token cost
~2.6k tokens
SKILL.md length
897 words
Files
2
Skills in repo
45
Repo updated
First seen
Licence
Custom licence

At a glance

Audits a local LazyCodex and Codex CLI install against the latest upstream sources and reports PASS, WARN or FAIL per check without changing anything.

  • Works in 8 steps: Materialize the latest sources under… → Inventory the installed surface. Resolve… → Check config and wiring against the… → …
  • Codex behaves oddly after installing or updating LazyCodex
  • SKILL.md covers Required Workflow, Doctor Report Template, Follow-up Routing and Stop Conditions
  • Calls git, codex and gh; reaches github.com

What it does

A diagnose-only health check for setups that act strangely after an install, update or config change. It first checks out fresh copies of the LazyCodex and Codex sources into a scratch directory, re-syncing on every run and validating any cached checkout so a half-finished clone cannot skew results. It then inventories what is installed: the codex version and how the command resolves, the installed LazyCodex plugin manifest under the Codex home directory, the latest released versions, the operating system, the install method and the bin links.

The output is a report in which every verdict cites the command output or file that produced it. The skill writes only inside its source scratch directory and leaves your install, config and repositories untouched. It proposes remediations and applies one only if you ask for it afterward.

When your agent uses it

  • Codex behaves oddly after installing or updating LazyCodex
  • Checking whether a local LazyCodex install has drifted from the latest release
  • Auditing plugin and config state before filing a bug report
  • Confirming that the lazycodex and lazycodex-ai commands resolve correctly

Example prompts

  • “Do a health check on my LazyCodex install and compare it with the latest release.”
  • “Codex started misbehaving after I updated lazycodex-ai, so diagnose the install.”
  • “Audit my Codex plugins directory and tell me which parts are stale or broken.”

Requirements

  • Codex CLI with LazyCodex installed
  • Git and network access to fetch the latest sources
  • GitHub CLI for release lookups

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Materialize the latest sources under LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}" first. Every…
  2. Inventory the installed surface. Resolve CODEX_HOME (default ~/.codex), then collect
  3. Check config and wiring against the latest installer, not against assumptions. Read what the current installer under…
  4. Probe the real surface. Do not invoke lazycodex doctor; this skill is already running inside that doctor workflow, so calling it would…
  5. Compare for drift. Where installed manifest-declared bundled files differ from the same files at the installed version, or the latest…
  6. Check whether each FAIL is already known: gh issue list --repo code-yeongyu/lazycodex --search "" --state open (and openai/codex when the…
  7. If a probe fails and the cause is not explained by config or source comparison, invoke $omo:debugging for the investigation. If Codex…
  8. Emit the report.

What it can do on your machine

Read from SKILL.md and the folder at commit ae4ddd2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • codex
    • gh
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

LazyCodex Doctor loads about 2.6k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 897 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~98
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 897 words (~2,627 tokens).

“You are a LazyCodex install doctor. Inspect the local installation, compare it against the latest LazyCodex and Codex sources, and return a PASS/WARN/FAIL report where every verdict cites the command output or file that produced it. Diagnose only: the only…”

— opening of SKILL.md by code-yeongyu, Custom licence
name
lcx-doctor
metadata.short-description
Diagnose LazyCodex/Codex install health against latest sources

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in packages/omo-codex/plugin/components/lcx/skills/lcx-doctor of code-yeongyu/oh-my-openagent.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit ae4ddd2

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in code-yeongyu/oh-my-openagent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

LazyCodex Doctor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

LazyCodex Doctor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LazyCodex Doctor this skillcode-yeongyu/oh-my-openagent70k—~2.6kAutomated safety check: PassCustom licence
Readyprekuter/dryforge4131 repos~6.8kAutomated safety check: PassApache-2.0
Goprekuter/dryforge4131 repos~7.2kAutomated safety check: PassApache-2.0
Publish Plugins Version Bumpvinta/hal-9000138—~1kAutomated safety check: PassMIT
Setup First Passjoetawil7/first-pass92—~5.2kAutomated safety check: PassMIT
Rule Catalogathola/claude-night-market341—~1.6kAutomated safety check: PassMIT

Similar skills

  • Ready

    prekuter/dryforge

    Understand what you mean before anything is built. An agent skill from prekuter/dryforge.

    413 GitHub starsUsed in 1 repo~6.8k tokens
    Agent WorkflowsAuto-check passed

  • Go

    prekuter/dryforge

    Carry out the intent approved in ready, as meant, and prove it with checks that actually ran.

    413 GitHub starsUsed in 1 repo~7.2k tokens
    Agent WorkflowsAuto-check passed

  • Publish Plugins Version Bump

    vinta/hal-9000

    Finds which plugins in the repository changed, bumps only the ones not already bumped since origin/main, and checks that each plugin's two manifests stay in sync.

    138 GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Setup First Pass

    joetawil7/first-pass

    Set up first-pass for a main folder that holds many repos, or for one repo.

    92 GitHub stars~5.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Rule Catalog

    athola/claude-night-market

    Browse hookify rule catalog. An agent skill from athola/claude-night-market.

    341 GitHub stars~1.6k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Git Guardrails Claude Code

    fossasia/eventyay-interpretation

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.

    1.6k GitHub starsUsed in 12 repos~578 tokens
    AI & LLM EngineeringAuto-check passed

More from code-yeongyu/oh-my-openagent

All 45 skills in this repo

  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Browser Control with Omowright

    code-yeongyu/oh-my-openagent

    Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.

    70k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • LSP Setup

    code-yeongyu/oh-my-openagent

    Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.

    70k GitHub stars~1.4k tokensUpdated today
    Auto-check: notes

  • OpenCode QA Toolkit

    code-yeongyu/oh-my-openagent

    Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.

    70k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about LazyCodex Doctor

What does LazyCodex Doctor do?

Audits a local LazyCodex and Codex CLI install against the latest upstream sources and reports PASS, WARN or FAIL per check without changing anything. A diagnose-only health check for setups that act strangely after an install, update or config change. It first checks out fresh copies of the LazyCodex and Codex sources into a scratch directory, re-syncing on every run and validating any cached checkout so a half-finished clone cannot skew results.

When should I use LazyCodex Doctor?

LazyCodex Doctor fits situations like: Codex behaves oddly after installing or updating LazyCodex; checking whether a local LazyCodex install has drifted from the latest release; auditing plugin and config state before filing a bug report; confirming that the lazycodex and lazycodex-ai commands resolve correctly.

How do I install LazyCodex Doctor in Claude Code?

Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor -a claude-code`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-doctor in code-yeongyu/oh-my-openagent) into .claude/skills/lcx-doctor in your project. Claude Code loads it when a task matches its description.

How do I install LazyCodex Doctor in Codex?

Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor -a codex`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-doctor in code-yeongyu/oh-my-openagent) into .agents/skills/lcx-doctor in your project. Codex loads it when a task matches its description.

Can I use LazyCodex Doctor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-doctor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lcx-doctor, .gemini/skills/lcx-doctor, .github/skills/lcx-doctor and .opencode/skills/lcx-doctor in your project.

What does LazyCodex Doctor need to run?

Going by SKILL.md and its folder, LazyCodex Doctor needs the command-line tools its instructions call (git, codex, gh and npm). Our summary lists: Codex CLI with LazyCodex installed; Git and network access to fetch the latest sources; GitHub CLI for release lookups.

Does LazyCodex Doctor access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is LazyCodex Doctor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does LazyCodex Doctor use?

LazyCodex Doctor has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does LazyCodex Doctor use?

About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to LazyCodex Doctor?

Skills that share tags, products or a category with LazyCodex Doctor: Ready (prekuter/dryforge, 413 stars), Go (prekuter/dryforge, 413 stars), Publish Plugins Version Bump (vinta/hal-9000, 138 stars) and Setup First Pass (joetawil7/first-pass, 92 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LazyCodex Doctor?

code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,917 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 9, 2026.

Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.