# System Skilled Doctor

> Doctor commands that put Skilled into a project repo and keep it current there, including a vendored copy's own overlays.

- Skill: `michelkerkmeester/system-skilled-doctor` (Agent Skill, multi-file: 31 files)
- Install (CLI): `npx get-skill add michelkerkmeester/system-skilled-doctor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/michelkerkmeester/system-skilled-doctor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: MichelKerkmeester (https://skillmd.com/u/michelkerkmeester)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/michelkerkmeester/system-skilled-doctor

---


<!-- Keywords: put skilled into my project, skilled in my project repo, keep skilled current in my project, vendored skilled copy, vendored skilled overlays, keep my changes to vendored skilled, re-pin vendored skilled, link a local skilled checkout into a project, overlay layout path, relayout, overlay audit, strict overlay writes, unowned vendored files, unowned vendored change, overlay sources, no overlay owns, overlay root files drifted upstream, overlay rebase, drifted from the pinned upstream commit, changed the root files an overlay owns, overlay no longer adds a json item, stage an overlay re-pin, staged overlay re-pin, take over an overlay lock, overlay lock whose owner has ended -->
<!-- Owns: /doctor:install, /doctor:symlink, /doctor:update, /doctor:agents-md, /doctor:runtime-mirrors, /doctor:env, /doctor:setup, /doctor:helper, /doctor:speckit, /doctor:mcp, /doctor:overlay. Does NOT own: /doctor:sk-code and /doctor:ci (sk-code), /doctor:git (sk-git), /doctor:sk-skill (sk-doc), /doctor:skill-advisor (system-skill-advisor), /doctor:deep-loop (system-deep-loop). -->

# System Skilled Doctor

Owns the doctor commands that put Skilled into a project and keep it current there.

---

## 1. WHEN TO USE

### Activation Triggers

Use this skill when:

- Someone wants Skilled in their own project repository, as a first install, a linked checkout, an update to a newer release or a vendored copy.
- A project's runtime folders, environment switches, `AGENTS.md` sections, trigger index or Code Mode registration need checking against what Skilled ships.
- A project that vendors Skilled needs its own changes, its overlays, applied or checked after the copy changed.
- A problem is described and the right doctor command is not known yet.

**Keyword Triggers**:
- "put Skilled into my project", "install Skilled", "link the Skilled checkout"
- "update Skilled", "runtime mirrors", "environment switches", "doctor setup"
- "which doctor command", "AGENTS.md sections", "trigger index fresh", "Code Mode install"
- "vendored Skilled", "Skilled overlays", "overlay status", "apply the overlays"

### When NOT to Use

Do not use this skill for:

- A skill's own battery or quality config. `/doctor:sk-code` and `/doctor:ci` belong to `sk-code`, `/doctor:git` to `sk-git`, `/doctor:sk-skill` to `sk-doc`, `/doctor:skill-advisor` to `system-skill-advisor` and `/doctor:deep-loop` to `system-deep-loop`.
- Writing or validating spec folders, which is `system-spec-kit`'s work. That skill still owns the scripts these commands call, such as the trigger-index lookup and `ENV-REFERENCE.md`.

---

## 2. SMART ROUTING

A request that names one of the owned commands, or describes installing, linking, updating or checking Skilled in a project, selects this skill.

The owned-command table in [`README.md`](./README.md) loads first. It names what each command does, so the request can be matched to one command and that command run. A request about a vendored copy's overlays also loads [`references/overlays.md`](./references/overlays.md), which says what each sync state means and what resolves it.

A request about one skill's own checks looks related but belongs to that skill's doctor command, listed under When NOT to Use. The router refuses it rather than loading this table.

The machine router and its resource map live in [`ROUTER.md`](./ROUTER.md), which calls `discover_markdown_resources()` and `_guard_in_skill()` and returns `UNKNOWN_FALLBACK` on no match. Read it before loading a skill-local resource.

---

## 3. HOW IT WORKS

### Workflow

1. Match the request to one owned command, using the README table. When nothing matches clearly, run `/doctor:helper` with the problem in the user's words.
2. Run that command. Each one is a router in `.skilled/commands/doctor/` that owns its own workflow YAML and presentation asset, so this skill adds no second copy of either.
3. Read the command's result and its exit status before reporting it. A command that writes shows its plan and waits for approval first.

### Output Contract

The chosen doctor command's own result: a check report, or a plan that changes nothing until the user approves it.

### Verification

The command's own checks, read with their exit status. For a change to this skill's ownership, run `node --test .skilled/commands/doctor/scripts/tests/*.test.cjs` and the command-bridge drift guard.

---

## 4. RULES

### ✅ ALWAYS

- Run the doctor command itself, rather than repeating its steps by hand.
- Read a command's output and exit status before reporting what it found.
- Let a writing command show its plan and wait for the user's approval.

### ❌ NEVER

- Move a command file out of `.skilled/commands/doctor/`. The bridge deriver and the runtime mirrors read that folder, and so does `_routes.yaml`.
- Claim a check passed from its exit status alone.
- Answer another skill's doctor question from this skill.

### ⚠️ ESCALATE IF

- No owned command fits and `/doctor:helper` ranks nothing.
- A command refuses or fails in a way its own output does not explain.
- A request would change a project file the command's plan did not list.

---

## 5. SUCCESS CRITERIA

The task is complete when:

- The fitting doctor command ran and its result was read.
- Any write it made was approved first and matches its printed plan.
- Anything left unresolved is reported with the command's own words.

---

## 6. INTEGRATION POINTS

### Inputs

- A project repository with the Skilled checkout or release it uses.
- The user's description of what to set up or check.

### Outputs

- Doctor reports and approved plans.
- The changes those plans apply.

### Related Workflows

- `system-spec-kit` owns the trigger index, its retrieval recipes, the runtime-mirror generators and `ENV-REFERENCE.md`, which three of the owned commands check.
- `mcp-code-mode` owns Code Mode itself. `/doctor:mcp` installs and debugs it in a project.

---

## 7. REFERENCES AND RELATED RESOURCES

### Core References

- [`README.md`](./README.md): the owned-command table.
- [`references/overlays.md`](./references/overlays.md): the overlay sync states and the overlay folder setting, what the engine refuses and how to re-pin.
- `.skilled/commands/doctor/`: each command's router with its workflow YAML and presentation asset.

### Loading Notes

- Load the README table first, then the one command it points to.
- Load the overlay reference only for a vendored copy's overlays.

