hyperdxlisted

Query and read logs and traces from HyperDX using Lucene syntax via the bundled hdx_query.sh CLI. Use this skill whenever the user asks to search logs, fetch errors, debug a service, investigate incidents, check log output, inspect traces, or look up anything in HyperDX — even if they don't say "HyperDX" explicitly. Trigger on phrases like "check the logs", "show me errors from", "what's happening with service X", "look up logs for", "any 500s recently", "show me the traces", or "what does HyperDX say about". Always use this skill when log querying or incident investigation is involved. IMPORTANT: always query logs by running the bundled hdx_query.sh script — never attempt to query HyperDX via curl, the API directly, or any other method.
LunarCommand/claude-skills · ★ 1 · Code & Development · score 67

Install: claude install-skill LunarCommand/claude-skills

# HyperDX Log Querying > **MANDATORY**: Always use `hdx_query.sh` to query logs and traces. Do not use > curl, raw API calls, or any other method — even if it seems simpler. If the > script fails, fix the script — do not work around it. **Three failures are environment, not bugs — do not edit the script for these:** | What you see | What it means | | --- | --- | | `Missing required command: <x>` (exit 127) | A dependency is absent. Tell the user to install it. The script is fine. | | `command not found: hdx_query.sh` | The skill's `bin/` is not on `PATH` — the plugin is disabled, or the session started before it was installed. Ask the user to enable it and run `/reload-plugins`, or restart. Do not substitute an absolute path. | | A permission prompt on every call | The allowlist is not installed. That is setup, not failure — see Permissions below. | Anything else that fails is a real defect: fix the script rather than working around it. `hdx_query.sh` ships in this skill's `bin/` directory, which is on the Bash tool's `PATH` whenever the skill is installed. **Invoke it by bare name** — never by an absolute path. The bare form is the only spelling that works on both install routes, and it is what the permission rule matches. The script supports two modes: **cloud** (HyperDX REST API) and **local** (ClickHouse via docker exec into a local HyperDX container). --- ## Per-Project Configuration (.agent.env) Each project should have the following in its `.agent.env` file at