Menu
Check watercooler system health — MCP server, baseline graph (T1), git auth, GitHub rate limit, and daemons. Use when syncs break or anything in the watercooler stack behaves unexpectedly.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
This skill should be used to keep CLAUDE.md, AGENTS.md, and the skill files themselves compact, current, and internally consistent. It runs in three phases: Phase 1 performs a one-time structural refactor of CLAUDE.md using a Karpathy-inspired behavioral scaffold and derives AGENTS.md from it by stripping Claude Code-specific sections. Phase 2 extracts durable project conventions from Watercooler Decision entries since the last update and patches a bounded generated section. Phase 3 audits the local skill surface against the live MCP tool surface and the in-process alias registry (`TOOL_ALIASES` in `aliases.py`), surfacing skill files that reference retired or renamed tools. Use when CLAUDE.md has grown verbose or stale, when AGENTS.md has drifted from CLAUDE.md, when significant project decisions have accumulated since the last refresh, or after a watercooler-cloud tool-surface consolidation lands.
Find discussions and entries related to a specific topic or entry. Use to discover connected context across threads.
Recall project context or answer questions about history and decisions. Use before starting work, when investigating unfamiliar code, or asking "What was decided about X?" / "Why did we choose Y?"
Search threads with filters. Supports filters like role:planner, type:Decision, after:2024-01, thread:topic-name, status:OPEN
List and navigate watercooler threads. Use to see active discussions, find specific threads, or get an overview of project threads.
Bootstrap Watercooler memory for a repository by inspecting local code, docs, CI, git history, and existing Watercooler threads, then writing a small set of durable, provenance-backed seed threads that future agents can query and extend. Use when entering a repo for the first time, seeding a repo with Watercooler context, or refreshing foundational repository context.
| name | watercooler-health |
| description | Check watercooler system health — MCP server, baseline graph (T1), git auth, GitHub rate limit, and daemons. Use when syncs break or anything in the watercooler stack behaves unexpectedly. |
| allowed-tools | ["ToolSearch","mcp__watercooler__watercooler_health","mcp__watercooler__watercooler_baseline_graph"] |
Run a full health check across all watercooler subsystems.
Load diagnostic tools in parallel:
ToolSearch: select:mcp__watercooler__watercooler_health
ToolSearch: select:mcp__watercooler__watercooler_baseline_graph
Run checks in parallel:
mcp__watercooler__watercooler_health(code_path="<repo root>")
mcp__watercooler__watercooler_health(code_path="<repo root>", detail="identity")
mcp__watercooler__watercooler_baseline_graph(scope="sync", code_path="<repo root>")
The detail="identity" call returns the resolved agent identity and a
write-readiness assessment (threads-dir writability + agent_func
guidance) — this is the folded-in former whoami check.
Report status — organize output into these sections:
Server Health (from watercooler_health):
watercooler_health(detail="identity")): resolved
identity and whether the threads dir is writableGraph Services (from watercooler_health):
Backend Services (from watercooler_health):
Daemons (from watercooler_health):
Thread Storage (from watercooler_health):
Git Authentication (from watercooler_health):
GitHub (from watercooler_health):
T1 — Baseline Graph (from baseline_graph, scope="sync"):
Suggest fixes for common issues:
T1 issues:
watercooler_baseline_graph (scope="sync") and reconcile stale entriesGit / GitHub issues:
eval "$(ssh-agent -s)" && ssh-addgh auth login -h github.com --web/watercooler-health — Full system health check