菜单
Query and debug OpenTelemetry data (traces, logs, metrics) in ClickHouse (HyperDX/ClickStack) via the sideclaw MCP `otel` tool. Use when investigating application errors, slow or missing traces, log anomalies, service health, or any observability question in local dev or VPS production (local + prod both supported).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Read and write the second brain — a git-backed Obsidian vault at ~/SourceRoot/brain (PARA structure + a top-level wiki/ knowledge tree). Use whenever the user mentions "brain", "second brain", "knowledge base", "note", "remember", "look up", "find note", "capture", "wiki", or "okf". Also use for any request to save, retrieve, or organize personal knowledge that belongs in the brain rather than in a repo-specific doc.
Write, draft, and polish prose through a human-owned 7-step pipeline. Use whenever the user says "distill", "write article", "draft", "summarize into", "create content", "synthesize", or "publish". Also use for any task where the output is a piece of long-form writing — the pipeline keeps prose quality out of coding sessions.
RETIRED — manage the (now decommissioned) per-machine mlx-audio TTS/STT stack; TTS/STT moved to the cloud audio-gateway (VPS)
Operate the Mac mini remote dev host — connecting from the MacBook over mosh or herdr --remote, running and reattaching many Claude Code agents, herdr workspaces/panes and its socket API, claude --bg durable daemons, the Uptime Kuma readiness heartbeat, and the failure modes specific to a headless always-on Mac. Use when the user mentions herdr, mosh, the mini, "remote dev", "dev host", detaching or reattaching agents, "did my agent survive", sessions dying on lid-close, or asks how to reach a dev server running on the mini.
Manage the personal image stack — public CDN uploads/transform URLs and the private image-share layer. Use whenever an image needs a URL (public or private) for an article, blog post, vault note, README, OpenGraph tag, or a one-off share; or when the user says "upload this image", "share this image", "private image", "publish image", "host this screenshot", "get me a CDN link", "resize this", mentions "image-share", or asks where an image lives.
Bidirectionally sync ALL git repos across two machines — this MacBook and the always-on Mac mini — over SSH, using GitHub/GitLab as the transport. Commits and pushes uncommitted work on both sides, then rebases/fast-forwards each so they converge, with per-repo subagents resolving rebases and merge conflicts. This is a MULTI-repo, TWO-machine operation — distinct from /commit, /ship, or /git-cleanup, which act on a single repo. Use whenever the user wants to sync their machines/repos, "catch up" the laptop to the Mac mini or push laptop work back, is about to travel or just got back, has uncommitted work scattered across many repos, or wants to reconcile branches that diverged between the two machines. Trigger even on a bare "sync", "sync my machines", or "get my repos up to date".
| name | otel |
| description | Query and debug OpenTelemetry data (traces, logs, metrics) in ClickHouse (HyperDX/ClickStack) via the sideclaw MCP `otel` tool. Use when investigating application errors, slow or missing traces, log anomalies, service health, or any observability question in local dev or VPS production (local + prod both supported). |
Call mcp__sideclaw__otel with:
investigation — what to look into (error message, service, trace id, anomaly, time range).environment — local or prod.cwd (optional) — defaults to $HOME. OTEL access is host-level, so this rarely matters.The worker runs read-only on claude-sonnet-5[1m], currently on Max per
SIDECLAW_WORKER_BACKEND=max (IU unified endpoint fallback when unset — non-EU
routing, so treat prod log content accordingly), and queries ClickHouse through
~/.claude/skills/otel/scripts/query.py. Only the structured result (status,
environment, timeRange, findings, recommendations) returns to the caller —
the raw query output stays in the worker.
Inspect status first: errors = active error spans/logs, degraded = elevated
latency or warnings, healthy = data flowing normally.
Reliability: a query can take 1–6 min under load. The tool's 8-min timeout absorbs most of it; on a hard timeout, retry.
Maintenance: the ClickHouse query script (scripts/query.py) is the canonical
access path and lives here in dotfiles, not in sideclaw — add presets / schema
changes there. The sideclaw worker invokes it by absolute $HOME path.