From tierzero
Query production telemetry through TierZero to inform debugging, incident investigation, feature design, and code review. Runs in background proactively.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tierzero:tierzeroThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Query production telemetry data through TierZero's API to inform debugging, incident investigation, feature design, and code review.
Query production telemetry data through TierZero's API to inform debugging, incident investigation, feature design, and code review.
TRIGGER when: debugging production issues, investigating incidents or alerts, designing new features, refactoring existing code, reviewing PRs, or any task where understanding real production behavior (traffic patterns, error rates, latency, usage) would inform better decisions. Run in background proactively — don't wait to be asked.
DO NOT TRIGGER when: writing pure unit tests, updating documentation, or tasks with zero production relevance.
TIERZERO_PAT_TOKEN environment variable must be setcurl and jq must be availablePaths below are relative to this skill directory.
Run the query script in the background using the Bash tool:
scripts/tierzero_ask.sh '<QUERY>'
Always set run_in_background: true so the user is not blocked while waiting for results.
The following command prefixes are used by this skill:
scripts/tierzero_ask.sh/tasks to check statusTIERZERO_PAT_TOKEN is not set, the script will exit with an error message directing the user to https://app.tierzero.ai/settings/tokensnpx claudepluginhub tierzeroai/tierzero-claude-code --plugin tierzeroInstruments running services with Lightrun to answer live production questions about variable values, execution durations, hit counts, and value distributions.
Instruments code with logging, metrics, traces, and alerting so production behavior is visible and diagnosable. Use when shipping features, diagnosing slow incidents, or reviewing PRs with I/O or cross-service calls.
Guides structured Honeycomb workflows for production issue investigations: orient with context/SLOs/triggers, broad queries/service maps, BubbleUp differentiators, trace analysis to find root causes like latency spikes or error surges.