← ClaudeAtlas

doctorlisted

Cuebird self-diagnostics. Use when reminders fail to create, the user doubts phone delivery, asks whether Cuebird works, or wants to check for plugin updates.
itsmynamee/cuebird · ★ 0 · AI & Automation · score 72
Install: claude install-skill itsmynamee/cuebird
# Cuebird: doctor Below, `$CUEBIRD` denotes the resolved absolute path to the CLI — it is notation, not a shell variable: each bash command you run is its own fresh shell, so substitute the literal path directly into every command below (or, if you do assign a shell variable, only rely on it within one single bash invocation, never across separate tool calls). Resolve `$CUEBIRD` using these methods, in order — never guess beyond them: 1. If your skill invocation provides a "Base directory for this skill" (or equivalent), use it directly: `CUEBIRD=<that-base>/../../scripts/cuebird.sh` 2. Otherwise, if the environment variable `CLAUDE_PLUGIN_ROOT` is set in your Bash environment, use `"$CLAUDE_PLUGIN_ROOT/scripts/cuebird.sh"`. 3. Only if both of the above fail, locate the installed plugin under `~/.claude/plugins`: `ls -d ~/.claude/plugins/*/cuebird*/scripts/cuebird.sh 2>/dev/null | head -1` The plugin root (for check 7's `plugin.json`) is `$CUEBIRD`'s grandparent directory — derive it instead of re-resolving separately: `PLUGIN_ROOT="$(cd "$(dirname "$(dirname "$CUEBIRD")")" && pwd)"`, then `plugin.json` lives at `"$PLUGIN_ROOT/.claude-plugin/plugin.json"`. None of the commands below interpolate user-supplied free text (unlike skills/remind, skills/reminders, skills/resume) — every value is a fixed path or CLI output you read back, not compose — so the single-quoting rule those skills require does not apply here. Run the seven checks below IN ORDER, then pr