Validate that the current VM has the right `agent-skills` installed for the repo you’re working in.
Validate that the current VM has the right agent-skills installed for the repo you’re working in.
This is a soft doctor: it reports issues and suggested fixes, but should not block work.
Use when:
~/.agent/skills is stale on a VMThe doctor performs two classes of checks:
Verifies the shared skills plane at ~/.agent/skills is properly installed:
~/.agent/skills exists (as symlink or directory)~/agent-skills)AGENTS.md exists in the skills planedist/universal-baseline.md)skill-profiles/ based on your repo’s origin remote URL.~/.agent/skills (or AGENT_SKILLS_DIR).The skills plane follows a one shared plane per VM model:
~/.agent/skills -> ~/agent-skills (symlink)
Multiple IDE/client surfaces (claude-code, opencode, gemini-cli, etc.) consume this shared plane
through their own bootstrap/config rails (e.g., ~/.claude/CLAUDE.md -> ~/.agent/skills/AGENTS.md).
This doctor checks the shared plane locally. For fleet-wide skills alignment, see
dx-fleet check --mode weekly which includes:
skills_plane_alignment - Fleet-wide skills plane healthide_bootstrap_alignment - IDE bootstrap/config rail alignment# From inside a repo (prime-radiant-ai, affordabot, llm-common)
~/.agent/skills/skills-doctor/check.sh
Optional overrides:
export AGENT_SKILLS_DIR=”$HOME/.agent/skills”
export SKILLS_DOCTOR_PROFILE=”prime-radiant-ai” # or affordabot, llm-common
~/.agent/skills/skills-doctor/check.sh
For JSON output (useful in fleet checks):
~/.agent/skills/health/skills-doctor/check.sh --json
0: All checks pass1: Missing skills or skills-plane issues detected2: Warnings only (recommended skills missing)