メニュー
Manages the wicked-brain background server. Most callers should use `wicked-brain-call` directly — it auto-starts the server. This skill is for explicit lifecycle management: start, stop, status, or recovery from a stuck process.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Universal code intelligence via LSP. Queries language servers for definitions, references, symbols, call hierarchies, hover info, and diagnostics. Auto-installs language servers when missing. Use when: "where is X defined", "who uses X", "what type is X", "list symbols in", "find symbol", "who calls X", "code diagnostics", "lsp health".
Synthesize wiki articles from brain chunks. Dispatches a compile subagent that identifies concept clusters in chunks and writes structured wiki articles with backlinks and source attribution. Use when: "compile the brain", "write wiki articles", "synthesize knowledge", "brain compile".
This skill should be used when the user says "configure brain CLI", "update CLAUDE.md from brain", "write brain orientation", or "regenerate brain config". Reads brain state and writes contextual instructions into the active CLI's agent config file. Run after onboarding, major ingests, or consolidation.
Multi-pass brain consolidation - archive noise, promote patterns, merge duplicates, build synonym map. Use when: brain needs maintenance, after significant ingestion, or reviewing consolidation_hint entries in log.jsonl.
Inspect, replay, or drop dead-lettered events from wicked-brain's bus subscriber. The auto-memorize subscriber consumes `wicked.garden.fact.extracted` and dead-letters events that exhaust their retry budget. Without this skill, those events sit untouched forever — a fixable handler bug silently loses every fact. Use when: "show DLQ", "replay dead letters", "what events failed", "drop dead letter", "memory subscriber DLQ", "stuck fact events".
Fill gaps in brain knowledge. Dispatches an enhance subagent that identifies thin areas and writes inferred chunks to expand coverage. Use when: "enhance the brain", "fill gaps", "brain enhance", "what's missing in the brain".
| name | wicked-brain-server |
| description | Manages the wicked-brain background server. Most callers should use `wicked-brain-call` directly — it auto-starts the server. This skill is for explicit lifecycle management: start, stop, status, or recovery from a stuck process. |
Manage the wicked-brain background server lifecycle explicitly. Most skills
do not need this — npx wicked-brain-call <action> will spawn the server
on first call (lock-guarded against races) and reuse it thereafter.
This skill uses npx wicked-brain-call for all server interaction. The CLI
works on macOS, Linux, and Windows; it discovers the brain, auto-starts the
server, and writes a per-call audit record under {brain}/calls/.
For the brain path default:
~/.wicked-brain/projects/{cwd_basename}%USERPROFILE%\.wicked-brain\projects\{cwd_basename}Brain discovery + server lifecycle are handled by wicked-brain-call. Pass
--brain <path> to override the auto-detected brain, or set
WICKED_BRAIN_PATH. The CLI starts the server on first call (no manual
init required) and writes an audit record to {brain}/calls/ per call.
wicked-brain-call
handles this for you on every call)npx wicked-brain-call --status [--brain {brain_path}]
npx wicked-brain-call --start [--brain {brain_path}]
npx wicked-brain-call --stop [--brain {brain_path}]
--status reports whether a live server is answering on the configured port,
the bound port, and the brain id. --start spawns the server (idempotent —
no-op if already running). --stop signals the recorded PID and clears the
PID file.
If the user reports "the brain server seems wedged":
npx wicked-brain-call --status --brain {brain_path} to confirm.npx wicked-brain-call --stop --brain {brain_path} to terminate.npx wicked-brain-call --start --brain {brain_path} to relaunch.npx wicked-brain-call health --brain {brain_path} to verify.All skills should call the server through wicked-brain-call:
npx wicked-brain-call <action> # no params
npx wicked-brain-call <action> --param key=value [--param ...] # simple params
npx wicked-brain-call <action> '{"k":"v","nested":[1,2]}' # complex JSON
echo '{"k":"v"}' | npx wicked-brain-call <action> - # stdin (kubectl-style)
Exit codes: 0 = ok, 1 = API returned an error, 2 = infra failure
(server unreachable or could not be spawned).