Skip to content
Back to skills

Doctor

ASecurity

Diagnoses an unhealthy Kraft server and applies the reload, restart or update its health check calls for. Use when the server seems unhealthy or unresponsive, work items are not being picked up, or an upgrade or config change needs applying. A repo that will not connect is kraft:onboard; a stopped work item is kraft:triage.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 21, 2026
ai-agentsbash

Works with

  • terminal
  • mcp

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add itsOmidKarami/kraft --skill doctor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Doctor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Doctor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/itsomidkarami-doctor/badge)](https://www.skillsdirectory.com/skills/itsomidkarami-doctor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: doctor
description: "Diagnoses an unhealthy Kraft server and applies the reload, restart or update its health check calls for. Use when the server seems unhealthy or unresponsive, work items are not being picked up, or an upgrade or config change needs applying. A repo that will not connect is kraft:onboard; a stopped work item is kraft:triage."
---

Kraft's tools come from the `kraft` MCP server. If `kraft` is not on PATH, this
plugin has been installed without the program it drives: say so and point at
https://kraft-sdlc.dev/get-started/install rather than reporting a
connection error.

# When Kraft itself is unwell

This is the server's health, not one work item's or one repo's. A repo that
will not connect is `kraft:onboard`; a stopped item is `kraft:triage`.

## 1. Diagnose

```bash
kraft admin health     # exit 1 when degraded
kraft admin doctor     # every check at once; exit 1 on any
```

Run both and report every failing line verbatim. Paraphrasing loses the check
name, and the check name is what the fix is keyed on.

"Nothing is being picked up" is not always a health failure: Kraft files items
paused unless they were created with `--autostart`. If both checks pass, run
`kraft view list --status=paused` and hand what you find to `kraft:gates`.

## 2. Fix what the line names

| Situation | Action |
|---|---|
| Edited the template library, `policy.yaml` or `intake.yaml` | `kraft admin reload`: rereads from disk, no restart |
| Server not running | `kraft admin start`: `restart` refuses when there is nothing to restart |
| Server wedged or running old code | `kraft admin restart`: stops, then starts it the way it was running |
| Install is out of date | `kraft admin update [--restart]` |
| `mcp server` not `ok` | Install the Kraft plugin, or `kraft admin init` for a terminal-only setup; then doctor again |
| A repo row not `ok` | Do what its line names (often `kraft repo connect`), then doctor again |
| A `chain_templates`, `agent: <profile>`, `capabilities` or `setup <repo>` row not `ok` | That is config drift, not server health: hand it to `kraft:check` |

`reload` is safe to run. `restart` and `update` interrupt whatever the server is
running, so say that and ask first. `update` also replaces the installed
program.

## 3. Verify

Run `kraft admin doctor` again and report the result. A fix that was not
followed by a clean run is a guess. If a line still fails, stop and report it
rather than trying a further command.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.