honeycomb-production-investigation
From the author
Load when an investigation needs Honeycomb telemetry to find a root cause: a latency spike, an error surge, a deployment regression, a failing dependency or an SLO burning budget. Gives the order of Honeycomb MCP tool calls (orient, broad query, BubbleUp, trace drill-down, verification) and how to carry each result into the next step.
Install
npx skills add aws/tools-for-devops-agent --skill honeycomb-production-investigation -a claude-code
Installs to .claude/skills/honeycomb-production-investigation/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- honeycomb-metrics-queriesaws/tools-for-devops-agentLoad before querying a Honeycomb OpenTelemetry metrics dataset (dataset_type=metrics): gauges, counters, histograms and sums, including infrastructure metrics such as CPU, memory, disk I/O and network. Metrics follow different rules from trace datasets: bare COUNT, RATE_SUM, RATE_AVG, RATE_MAX and CONCURRENCY are rejected, temporal aggregation is automatic, and each metric has its own attributes. Not for event datasets that only have metrics in their name.DevOps★ 120
- honeycomb-observability-fundamentalsaws/tools-for-devops-agentLoad when the operator asks a conceptual question about observability or Honeycomb: what observability is, why wide events, what high cardinality or dimensionality means, events vs metrics vs logs, observability vs monitoring, or the core analysis loop. Grounds recommendations in first principles. Not for running queries or investigating a live issue.DevOps★ 120
- honeycomb-slos-and-triggersaws/tools-for-devops-agentLoad before calling Honeycomb get_slos or get_triggers, or when an investigation must judge SLO compliance, error budget burn or trigger status. Explains what the numbers mean, how to spot a misconfigured SLI, when a burn rate justifies paging or freezing deploys, and how to design burn alert thresholds.DevOps★ 120
- honeycomb-verify-recent-traceaws/tools-for-devops-agentLoad when the operator asks to verify a recent test or deployment in Honeycomb, find the most recent trace, or show the trace a test produced. Finds the traces created since the test started and summarizes the most recent one.Testing★ 120
- honeycomb-tracingpaperclipai/paperclipTrace Paperclip runs, requests, and full CI suites in Honeycomb. Use to find traces, diagnose latency, design readable and foldable waterfalls, configure opt-in OpenTelemetry, or add missing spans.Design★ 108.9K
- debug-pipelineharness/harness-skillsDiagnose Harness pipeline executions via MCP. Analyzes any execution (failed or successful) to produce structured reports with stage/step breakdown, timing, bottlenecks, failure details, chained pipeline drill-down, and execution logs. Use when asked to debug a pipeline, investigate a failure, find out why a build failed, analyze pipeline errors, check execution logs, review execution performance, or find bottlenecks. Trigger phrases: debug pipeline, pipeline failed, why did my build fail, analyze failure, pipeline error, execution logs, fix pipeline, execution bottleneck, slow pipeline.Engineering★ 127
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in