メニュー
Start, stop, or check status of the Side Quest observability event server. Use when asked to start the server, stop the server, check server status, or manage the observability dashboard lifecycle.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Fix Node.js certificate trust issues behind corporate SSL-inspecting proxies. Use when discussing: VPN, corporate VPN, corporate proxy, SSL inspection, MITM proxy, TLS interception, NODE_EXTRA_CA_CERTS, self-signed certificate error, UNABLE_TO_VERIFY_LEAF_SIGNATURE, certificate chain, proxy CA, corporate network, Claude Code on VPN, Gemini CLI on VPN, npm behind proxy, Node.js certificate error, CAFile.pem, proxy-on, proxy-off, HTTPS_PROXY, HTTP_PROXY, openssl s_client, certificate extraction, corporate root CA, forward trust CA, trust store gap.
Generate an engaging, deep-dive explanation document (FOR_[NAME].md) that explains a codebase or domain in plain language with analogies, lessons learned, and practical wisdom.
Add or remove inline plugins from the ccdev function in dotfiles .zshrc
Patterns for building CLIs that serve both humans and AI agents. Covers tri-modal output (JSON/JSONL/human), typed exit codes, structured error contracts, zero-dependency arg parsing, topic-based help, service discovery, field projection, and auto agent-mode detection. Reference implementation: @side-quest/observability CLI. Use when: building a CLI, adding a command, CLI output format, agent-friendly CLI, machine-readable output, JSON CLI contract, exit codes, --json flag, NDJSON streaming, how should my CLI work with agents, CLI design patterns.
Create and manage VS Code Bookmarks extension labeled bookmarks in .vscode/bookmarks.json. Use when the user wants to add navigation bookmarks to a codebase, trace data flows through code, mark important code locations, or set up labeled waypoints for code walkthroughs. Also use when user says "bookmark", "label this code", "mark this flow", or "add waypoints".
Decide whether a workflow should use CLI skills, MCP, or a hybrid approach. Use when planning agentic tooling, writing ADRs, or evaluating migrations between CLI and MCP.
| name | observability |
| description | Start, stop, or check status of the Side Quest observability event server. Use when asked to start the server, stop the server, check server status, or manage the observability dashboard lifecycle. |
| disable-model-invocation | true |
| argument-hint | [start|stop|status] |
| allowed-tools | Bash |
Manage the observability event server lifecycle. Mirrors the CLI subcommands.
Repo root: /Users/nathanvale/code/side-quest-observability Default port: 7483
Route based on $ARGUMENTS:
| Argument | Action |
|---|---|
start | Start the server |
stop | Stop the server |
status | Check server health |
| (empty) | Ask the user what they want to do |
curl -sf http://127.0.0.1:7483/health 2>/dev/null
If healthy, report the existing server and stop -- do not start a second instance.
bun run /Users/nathanvale/code/side-quest-observability/packages/server/src/cli/index.ts start --port 7483 &
sleep 1 && curl -sf http://127.0.0.1:7483/health
If the user specifies a port, pass --port <PORT> and adjust all URLs.
curl -sf http://127.0.0.1:7483/health 2>/dev/null
If not reachable, report that no server is running and stop.
bun run /Users/nathanvale/code/side-quest-observability/packages/server/src/cli/index.ts stop
curl -sf http://127.0.0.1:7483/health 2>/dev/null
curl -sf http://127.0.0.1:7483/health 2>/dev/null
If start fails with EADDRINUSE, check what's on the port:
lsof -i :7483
Report the conflicting process and ask the user how to proceed.
If the CLI stop command fails, check the PID file:
cat ~/.cache/side-quest-observability/events.pid
Ask the user before killing the process directly.