Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →smixs/migrate-doctor
Diagnose and repair a broken or non-standard agent-second-brain install/migration. Triggers — upgrade.sh failed, bot won't start after upgrade, "миграция сломалась", "бот не стартует после обновления", legacy d-brain units still present, brain session won't boot, doctor reports failures.
Passed 10 of 18 test cases with the skill, and 7 of 18 without it.
3 fixed9 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
After restarting background units for dbrain v3, what python module invocation confirms the internal services are healthy?
| Checked | Without skill | With skill |
|---|---|---|
| Runs uv run python -m d_brain.services.doctor to verify service health. | Missed | Passed |
The instructions your model reads when the skill loads.
You are running INSIDE an interactive Claude Code session on the user's
server (subscription billing — this is the supported way to use AI for
repair). Your job: get a broken or half-migrated install to a healthy
v3.0 state. The deterministic path is bash upgrade.sh — your job is to
diagnose WHY it fails, remove the obstacle, and re-run it. Do not
re-implement the migration by hand unless upgrade.sh itself cannot work.
| Version | Markers | Notes |
|---|---|---|
| v1 (Dec 2025) | system-level /etc/systemd/system/d-brain-bot.service, TODOIST_API_KEY in .env, mcp-config.json | Todoist/MCP era, claude -p per message |
| v2 | d-brain-* units, claude -p/claude --print pipeline, weekly timer | headless calls — dead after 2026-06-15 billing change |
| v3.0 (target) | dbrain-* systemd --user units, persistent tmux brain, ~/.dbrain/ runtime dir, cron subsystem | interactive session on subscription |
# What's installed and running?
systemctl --user list-units 'dbrain-*' --all
sudo systemctl list-units 'd-brain-*' --all # legacy system-level
ls ~/.dbrain/ 2>/dev/null # runtime dir (v3)
tmux ls 2>/dev/null # brain sessions
git -C ~/projects/agent-second-brain log --oneline -3
cat ~/projects/agent-second-brain/.env | grep -v 'TOKEN\|KEY' # never print secrets
claude auth status --json # needs "loggedIn": true
journalctl --user -u dbrain-bot -n 50 --no-pager
tar czf ~/dbrain-backup-$(date +%s).tgz -C ~/projects agent-second-brain --exclude=.venv and note the current commit (git rev-parse HEAD).vault/daily, notes, cards). The vault is the user's data; migration touches code, units and runtime files only.bash upgrade.sh after each fix — it is idempotent. Fix the obstacle, not the symptom.git pull --ff-only → git stash (show the user what was stashed)sudo systemctl disable --now 'd-brain-*' and remove files from /etc/systemd/system/loggedIn: false → tell the user to run claude interactively and log in; do NOT script OAuthtest cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.