honeycomb-verify-recent-trace
From the author
Load 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.
Install
npx skills add aws/tools-for-devops-agent --skill honeycomb-verify-recent-trace -a claude-code
Installs to .claude/skills/honeycomb-verify-recent-trace/ · 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-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
- 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
- verifycodeaholicguy/ai-devkitAI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.Testing★ 1.7K
- tracking-verifyjtrackingai/analytics-tracking-automationUse when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.Testing★ 145
- 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
- brigade-workescoffier-labs/brigadeUse at the start of any work session and whenever you verify a change in a Brigade Stack-wired repo or workspace - routes work through Brigade Stack so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade Stack installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.Testing★ 81
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in