Review a written document (markdown, design doc, runbook, README, etc.) for redundancy, inconsistency, clarity, and density. Apply the general rules first, then the type-specific addendum for the doc's genre. TRIGGER when: user asks to "review", "audit", "clean up", "tighten", "compress", or "check" a markdown / documentation file (including a proposal, pitch, or decision memo); user pastes a doc and asks for an editorial pass; user asks if a specific reviewer comment is "addressed"; about to DRAFT a design doc, proposal, planning doc, or RFC (apply Part C's authoring defaults, then self-review). DO NOT TRIGGER when: user wants substantive technical correctness review of a design, algorithm, or protocol (use adversarial-review), or review of a code diff or implementation (use code-review); writing a GitHub issue or PR body (use writing-issues-and-prs). Design docs and proposals may still trigger for structure, readability, and claim/ask calibration.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Use when asked to review code or a design at any granularity — a pull request, an architecture/design proposal, a module, a file, or a whole codebase/repo — "review this PR", "review this repo", "audit this module", "challenge this design", "is this architecture sound", "adversarial review"; especially anything touching trust boundaries, signing/key flows, consensus rules, upgrade/governance logic, protocol APIs, or crate/module boundaries being locked in. DO NOT use for quick working-diff hygiene (use code-review) or prose/document editing passes (use doc-review).
Inspect and switch the local Clash Verge/mihomo VPN via the bundled `vpnctl` CLI. TRIGGER when: user asks to check VPN status, see/switch proxy nodes, find the fastest node, fix slow/blocked connectivity, or control how Claude/Anthropic traffic is routed (e.g. "route Claude away from HK", "my VPN is slow", "switch to the fastest non-HK node", "what node am I on"). DO NOT TRIGGER when: user is configuring a VPN in code/infra (Terraform, WireGuard configs, cloud networking) unrelated to their local Clash Verge.
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.
Query Grafana Loki logs and Prometheus metrics for BTC Vault infrastructure. TRIGGER when: user mentions Grafana, logs, Loki, monitoring, observability, alerts, metrics, error investigation, or asks to check/debug/investigate daemon behavior in any environment (testnet, mainnet, devnet, etc.). DO NOT TRIGGER when: user is writing code that uses the word "log" in a programming context (e.g., log::info, tracing).
Use when the user asks for a weekly report, activity summary, or wants to review what was done in a GitHub org over a time period — searches issues and PRs, filters by author, groups by repo, and formats for Slack