Stats
Actions
Tags
From harbar
Diagnose a Harbar install — app running, hooks registered and executing, plugin up to date, Codex hooks trusted, notification permission. Run when sessions don't show up, notifications stopped appearing, or anything else seems off.
How this skill is triggered — by the user, by Claude, or both
Slash command
/harbar:doctorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the bundled diagnostic and help the user fix whatever it flags.
Run the bundled diagnostic and help the user fix whatever it flags.
$CLAUDE_PLUGIN_ROOT isn't always exported into a tool shell, so resolve the plugin root with a
fallback to the install cache:
ROOT="${CLAUDE_PLUGIN_ROOT:-$(ls -d ~/.claude/plugins/cache/harbar/harbar/*/ 2>/dev/null | sort -V | tail -1)}"
bash "${ROOT%/}/src/doctor.sh" --banner
Each line is ✅ (fine), ⚠️ (degraded, fix inline), or ❌ (broken, fix inline).
Then:
--banner flag fired one). If it did
not, the usual culprit is macOS notification permission for terminal-notifier, which Homebrew
updates silently reset: System Settings → Notifications → terminal-notifier → Allow
Notifications (style: Banners or Alerts). There is no programmatic check — asking is the test./plugin marketplace update harbar, /plugin install harbar@harbar,
then /harbar:update to rebuild the native side./hooks (you cannot do this for them).launchctl bootstrap line themselves.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub olexandryermilov/harbar --plugin harbar