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; user pastes a doc and asks for an editorial pass; user asks if a specific reviewer comment is "addressed". DO NOT TRIGGER when: user wants substantive technical correctness review of an algorithm, protocol, or implementation (use code-review or domain reasoning instead); user is drafting fresh prose from scratch (this skill is for review passes, not generation). Design docs may still trigger for structure, readability, and spec/runbook alignment.
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.
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