Audit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode, a rewrite mode, and an edit-in-place mode, with optional voice and context profiles.
lcx-doctor
lcx-doctor is an open-source docs skill for Codex, published by code-yeongyu. Its author describes it as: “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 instal…”. The project has 68k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-doctor`.
What lcx-doctor does
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 writes you make are under `LAZYCODEX_SOURCE_ROOT` or `${TMPDIR:-/tmp}/lazycodex-sources`. Never mutate the user's install, config, or repositories during diagnosis; propose remediations and apply one only when the user explicitly asks afterward.
Installation
Add lcx-doctor to your agent with:
git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-doctorAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for lcx-doctor is organised into these sections:
- Required Workflow
- Doctor Report Template
- Follow-up Routing
- Stop Conditions
When to use it
Reach for lcx-doctor when you want docs help from Codex without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Ships in code-yeongyu/oh-my-openagent, an established project with 68,032 GitHub stars
- Declares compatibility with Codex
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does lcx-doctor do?
- 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.
- How do I install lcx-doctor?
- Run git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-doctor in your agent, then reload your skills. Review the source at https://github.com/code-yeongyu/oh-my-openagent before installing.
- Is lcx-doctor free to use?
- lcx-doctor is publicly available on GitHub, but code-yeongyu has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
- Which agents does lcx-doctor work with?
- lcx-doctor declares compatibility with Codex. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.
- Where does lcx-doctor come from?
- lcx-doctor ships inside code-yeongyu/oh-my-openagent, a repository that contains 46 catalogued skills in total. The repository's 68,032 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Docs →
Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation. Scans docs/features, docs/issues, and docs/architecture; prefers multi-agent review when available; removes completed issue docs when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Use plan.md as the only separate tracker when needed, default to implementation-first validation, and ask before optional GitHub issue sync unless the developer explicitly requested sync.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks