health · terrylica — Claude Code skill: diagnostics and installation
This Claude Code skill checks the health of Cal.com Commander. It inspects the CLI, service settings, bot and sync processes, launchd jobs, circuit breakers, and audit logs.
MIT 100 installs ★ 3 updated 2026-10-25
npx skills add terrylica/cc-skills --skill health -a claude-codeWhat health does
The skill runs a Bash-based check of Cal.com Commander subsystems. It looks for the CLI binary, reports environment variables for Cal.com, Telegram, GCP, Supabase, and 1Password, then queries the 1Password CLI.
It checks PID files for the bot and sync processes, registered launchd jobs, and circuit breaker files. For audit logs, it finds the newest .ndjson file and prints its latest entries. The launchd check calls launchctl, so that portion depends on the command being available.
After the run, the skill asks the agent to review failures and update its instructions when a reproducible issue or changed parameter is found.
What it helps with
- confirm that the Cal.com CLI binary is present
- inspect environment settings for connected services
- check whether the bot and sync processes are running
- review launchd jobs and circuit breaker files
- read recent entries from the audit log
Example prompts for the agent
- Check the health of Cal.com Commander.
- Run Cal.com diagnostics and check the calendar bot status.
- Inspect the Cal.com Commander settings and audit logs.
How to install health
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill health -a claude-code2Manually: put the files in place
~/.claude/skills/health/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/health/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill health -a codex2Manually: put the files in place
.agents/skills/health/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill health -a cursor2Manually: put the files in place
.cursor/skills/health/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install terrylica/cc-skills plugins/calcom-commander/skills/health2Manually: put the files in place
.github/skills/health/SKILL.md1Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill health -a gemini-cli2Platform CLI
gemini skills install https://github.com/terrylica/cc-skills --path plugins/calcom-commander/skills/healthManually: put the files in place
.devin/skills/health/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add terrylica/cc-skills --skill health -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about health
How do I install health in Claude Code?
Run npx skills add terrylica/cc-skills --skill health -a claude-code. The skill file is at ~/.claude/skills/health/SKILL.md.
What does health do?
It checks the Cal.com Commander CLI, service settings, bot and sync processes, launchd jobs, circuit breakers, and recent audit log entries.
What does health inspect in the audit logs?
It locates the newest .ndjson file in the audit directory and prints several recent lines.
Source text
SKILL.md · MIT
---
name: health
description: "Cal.com Commander health check across all subsystems. TRIGGERS - calcom health, calendar bot status, cal.com diagnostics, booking bot check."
allowed-tools: Bash
model: haiku
---
# Cal.com Commander Health Check
Run diagnostics across all subsystems.
> **Self-Evolving Skill**: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
## Check All Subsystems
```bash
echo "=== 1. Cal.com CLI Binary ==="
ls -la "$HOME/.claude/plugins/marketplaces/cc-skills/plugins/calcom-commander/scripts/calcom-cli/calcom" 2>/dev/null && echo "OK" || echo "MISSING — run: cd scripts/calcom-cli && bun install && bun run build"
echo ""
echo "=== 2. Environment Variables ==="
echo "CALCOM_OP_UUID: ${CALCOM_OP_UUID:+SET}"
echo "CALCOM_API_URL: ${CALCOM_API_URL:-NOT_SET}"
echo "TELEGRAM_BOT_TOKEN: ${TELEGRAM_BOT_TOKEN:+SET}"
echo "TELEGRAM_CHAT_ID: ${TELEGRAM_CHAT_ID:-NOT_SET}"
echo "HAIKU_MODEL: ${HAIKU_MODEL:-NOT_SET}"
echo "OP_SERVICE_ACCOUNT_TOKEN: ${OP_SERVICE_ACCOUNT_TOKEN:+SET}"
echo ""
echo "=== 3. GCP Configuration ==="
echo "CALCOM_GCP_PROJECT: ${CALCOM_GCP_PROJECT:-NOT_SET}"
echo "CALCOM_GCP_ACCOUNT: ${CALCOM_GCP_ACCOUNT:-NOT_SET}"
echo "CALCOM_GCP_REGION: ${CALCOM_GCP_REGION:-NOT_SET}"
echo ""
echo "=== 4. Supabase Configuration ==="
echo "SUPABASE_PROJECT_REF: ${SUPABASE_PROJECT_REF:-NOT_SET}"
echo "SUPABASE_DB_URL_REF: ${SUPABASE_DB_URL_REF:+SET}"
echo ""
echo "=== 5. 1Password CLI ==="
op account list 2>&1 | head -3
echo ""
echo "=== 6. Bot Process ==="
if [ -f /tmp/calcom-commander-bot.pid ]; then
PID=$(cat /tmp/calcom-commander-bot.pid)
if kill -0 "$PID" 2>/dev/null; then
echo "Running (PID $PID)"
else
echo "STALE PID file (process $PID not found)"
fi
else
echo "Not running"
fi
echo ""
echo "=== 7. Sync Process ==="
if [ -f /tmp/calcom-sync.pid ]; then
PID=$(cat /tmp/calcom-sync.pid)
if kill -0 "$PID" 2>/dev/null; then
echo "Running (PID $PID)"
else
echo "Not running (stale PID)"
fi
else
echo "Not running"
fi
echo ""
echo "=== 8. launchd Jobs ==="
launchctl list | grep calcom-commander 2>/dev/null || echo "No launchd jobs registered"
echo ""
echo "=== 9. Circuit Breakers ==="
for f in /tmp/calcom-sync-circuit.json /tmp/calcom-commander-agent-circuit.json; do
if [ -f "$f" ]; then
echo "$(basename $f): $(cat $f)"
else
echo "$(basename $f): CLOSED (healthy)"
fi
done
echo ""
echo "=== 10. Recent Audit Logs ==="
AUDIT_DIR="${AUDIT_DIR:-$HOME/.local/state/calcom-commander/audit}"
if [ -d "$AUDIT_DIR" ]; then
LATEST=$(ls -t "$AUDIT_DIR"/*.ndjson 2>/dev/null | head -1)
if [ -n "$LATEST" ]; then
echo "Latest: $(basename $LATEST)"
tail -5 "$LATEST" | while read -r line; do
echo " $line" | cut -c1-120
done
else
echo "No audit logs found"
fi
else
echo "Audit directory not found: $AUDIT_DIR"
fi
```
## Post-Execution Reflection
After this skill completes, check before closing:
1. **Did the command succeed?** — If not, fix the instruction or error table that caused the failure.
2. **Did parameters or output change?** — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
3. **Was a workaround needed?** — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.
© terrylica · MIT · terrylica/cc-skills
Similar skills
SKILL.md skills catalog →health by other authors comes first.