agentleFS
Sign inStart free
RichardGeorgeDavisRichardGeorgeDavis/Codex-Workspace/.agents/skills/agent-tooling-doctor/SKILL.md

agent-tooling-doctor

Skill2 starsChanged 56 days agoMITView on GitHub

Diagnose Codex, OMX, OpenCode, and repo-level agent setup inside the workspace

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the task is about Codex/OpenCode/OMX readiness, repo-local agent config, or conflicting setup layers.

    line 8
  2. Very specific:

    Check for repo AGENTS.md, .codex/skills/, optional .agents/skills/, .workspace/agent-stack.json, .opencode/, and .omx/.

    line 13
  3. Distinctive:

    Prefer tracked repo guidance over hidden or user-only overrides when both exist.

    line 14
  4. Very specific:

    If a reviewed upstream snapshot in tools/ref/ suggests a useful improvement, extract it into the workspace baseline instead of depending on …

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Tooling Doctor

Use this skill when the task is about Codex/OpenCode/OMX readiness, repo-local agent config, or conflicting setup layers.

Default checks

  1. Run tools/scripts/doctor-agent-tooling.sh.
  2. Check for repo AGENTS.md, .codex/skills/, optional .agents/skills/, .workspace/agent-stack.json, .opencode/, and .omx/.
  3. Prefer tracked repo guidance over hidden or user-only overrides when both exist.
  4. If a reviewed upstream snapshot in tools/ref/ suggests a useful improvement, extract it into the workspace baseline instead of depending on the snapshot itself.

Workspace-native tools

tools/scripts/doctor-agent-tooling.sh
tools/scripts/init-agents-tree.sh --help
tools/scripts/sync-codex-skills.sh --all
tools/scripts/sync-reference-snapshots.sh --list

Expected tracked layout

  • repo rules: AGENTS.md
  • Codex skills: .codex/skills/
  • compatibility mirror: .agents/skills/
  • tool-neutral agent hints: .workspace/agent-stack.json
  • OpenCode project config: .opencode/

Avoid

  • vendoring full upstream harnesses into the workspace baseline
  • letting local-only runtime state become the canonical project contract

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free