메뉴
Run the health monitor and report results. Auto-run when: session-context shows health is degraded or failed, after infrastructure changes (docker, systemd), when a service appears unreachable, or user asks about system health. Invoke proactively without asking.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | status |
| description | Run the health monitor and report results. Auto-run when: session-context shows health is degraded or failed, after infrastructure changes (docker, systemd), when a service appears unreachable, or user asks about system health. Invoke proactively without asking. |
Run the health monitor and report results. Unset LITELLM_API_KEY so the check falls through to pass (avoids stale shell env overriding the correct key):
cd ~/projects/hapax-council && env -u LITELLM_API_KEY uv run python -m agents.health_monitor 2>&1 | grep -v -e "LITELLM_API_KEY is not set" -e "warnings.warn("
Report the score, then list FAILED and DEGRADED items grouped by severity.
If --fix can handle it, suggest: uv run python -m agents.health_monitor --fix --yes
For items --fix cannot resolve, investigate using the patterns below.
The most common cause is an env var overriding pass with a bad value. Check in order:
grep LITELLM ~/.config/fish/fish_variables. If the value is missing the sk- prefix, remove it: fish -c "set -Ue LITELLM_API_KEY"direnv status in hapax-council. If .envrc is not loaded, the env may have a stale value from session init.pass show litellm/master-key should return sk-... (67 chars). If not, the key itself needs updating.curl -s -o /dev/null -w "%{http_code}" http://localhost:4000/health should return 200 (even without auth).Restart the stale services:
systemctl --user start gdrive-sync.service gmail-sync.service youtube-sync.service
If gdrive-sync fails with Invalid Value on pageToken, the sync state is corrupted. Reset the token in ~/.cache/gdrive-sync/state.json — set start_page_token to empty string, then restart the service.
systemctl --user reset-failed profile-update.service && systemctl --user start profile-update.service
Check journal if it keeps failing: journalctl --user -eu profile-update.service --no-pager -n 30
The check compares agent manifest systemd_unit values against active timers. If an agent's timer exists but under a different name, fix the manifest in agents/manifests/<agent>.yaml to match the actual unit name. Verify with:
systemctl --user list-timers --no-pager | grep <keyword>
This follows from stale gdrive sync — fix the sync agent (above) and the connectivity warning clears.
systemctl --user reset-failed <service> && systemctl --user start <service>
If the service has a MemoryMax drop-in and is OOM-killed, check journalctl --user -eu <service> for oom-kill entries.
Background CI monitor for a PR. Auto-run when: PostToolUse detects a PR was just created (suggests it with PR number), user asks to watch CI, or after pushing to a branch with an open PR. Takes PR number as argument. Invoke proactively without asking.
Audit installed flatpak apps and find native alternatives. Auto-run when: storage-audit reveals large flatpak usage, operator mentions app performance issues related to sandboxing, or user asks about flatpaks. Invoke proactively without asking.
Audit branches across all repos and clean up. Auto-run when: session-context reports >3 non-main branches across repos, no-stale-branches hook blocks a branch create, after merging PRs, or user asks about branch cleanup. Invoke proactively without asking.
Scan for and resolve merge conflict markers. Auto-run when: conflict-marker-scan PostToolUse hook fires a warning, git merge/rebase/cherry-pick output shows CONFLICT (PostToolUse suggests it), or user asks to fix conflicts. Invoke proactively without asking.
Trace consent provenance. Auto-run when: work touches files containing personal data (profiles/, agents processing person names), after adding new data sources or storage, or user asks about consent or data protection. Invoke proactively without asking.
Full service triage. Auto-run when: a service is unreachable (connection refused, timeout), systemctl shows a failed unit (PostToolUse suggests it), session-context reports failed units, or user mentions something is broken/down/crashed. Takes optional service name as argument. Invoke proactively without asking.