honeycomb-query-patterns
From the author
Load before building or reading a Honeycomb run_query on a trace, log or event dataset. Covers which operation to pick (percentiles and HEATMAP over AVG), relational fields (root., parent., any., none.), calculated fields, query math, and how to read results such as P99/P50 ratios, heatmap bands and TOTAL/OTHER rows. For datasets with dataset_type=metrics, use honeycomb-metrics-queries instead.
Install
npx skills add aws/tools-for-devops-agent --skill honeycomb-query-patterns -a claude-code
Installs to .claude/skills/honeycomb-query-patterns/ · 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-production-investigationaws/tools-for-devops-agentLoad 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.Finance★ 120
- frontend-patternsJasonxzWen/harness-hubLoad when a task needs React or Next.js frontend logic, component patterns, state, forms, routing, accessibility, or responsive behavior; use frontend-design for visual direction.Design★ 71
- 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
- hk-follow-breadcrumbdeepklarity/harness-kitConsults existing breadcrumb analysis docs before exploring the codebase. Use this skill whenever the user asks about how a flow works, where something happens in the code, how to debug or test a specific area, what files are involved in a feature, or needs to understand the path data takes through the system. Also trigger when the user mentions 'where does X happen', 'how does Y work', 'trace this', 'what files handle Z', 'how to test this flow', 'debug this area', or when you're about to spawn multiple exploration subagents to understand a cross-cutting flow. Even if the user doesn't explicitly ask — if the task requires understanding how multiple layers connect (frontend → backend → worker → CLI), check breadcrumbs first. This is cheaper and more accurate than re-discovering the same information through code search.Testing★ 103
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in