CtrlK
BlogDocsLog inGet started
Tessl Logo

production-investigation

Structured workflows for investigating production issues in Honeycomb — the sequence of tool calls (context priming, broad query, BubbleUp, trace analysis, verification) and how to chain results between steps to reach root causes. Trigger phrases: "investigate production issue", "debug latency spike", "find root cause", "use BubbleUp", "analyze traces", "debug an outage", "why is my API slow", "errors are increasing", "health check", "SLO burning", or any request to investigate or debug production problems.

97

4.34x
Quality

100%

Does it follow best practices?

Impact

87%

4.34x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality instruction skill body: concrete tool-call sequencing, explicit verification and error-recovery steps, and well-organized one-level-deep references to verified bundle files. It adds only domain-specific knowledge Claude would not already have.

DimensionReasoningScore

Conciseness

Lean and information-dense with no concept-explanation fluff Claude already knows; the exception-handling paragraphs convey novel Honeycomb-specific knowledge (two query surfaces, LogRecordProcessor compatibility) that earns its tokens, matching the score-3 anchor.

3 / 3

Actionability

Provides concrete executable guidance — named MCP tools (`get_trace(show_events=true)`, `run_bubbleup`) and specific query filters (`error=true`, `event.name=exception`, `exception.type exists`) — matching the score-3 anchor rather than the vague or pseudocode anchors.

3 / 3

Workflow Clarity

Clear six-step sequence (Orient → Characterize → BubbleUp → Drill → Verify → Record) with an explicit validation checkpoint in Step 5 (query with and without the suspected cause as a control) plus error-recovery feedback loops in "When Results Are Empty or Unclear", matching the score-3 anchor exactly.

3 / 3

Progressive Disclosure

The body is an overview that points to three confirmed real reference files (investigation-playbooks.md, bubbleup-guide.md, trace-exploration.md) one level deep and clearly signaled in a "Reference Files" section, matching the score-3 anchor; not reduced to 2 because references are appropriately split and navigable.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-crafted description that clearly states the skill's purpose, lists concrete investigation phases, and provides an explicit trigger-phrase block covering both what and when. It is Honeycomb-specific enough to avoid conflict with generic debugging skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "context priming, broad query, BubbleUp, trace analysis, verification" and "chain results between steps to reach root causes" — matching the score-3 anchor for multiple specific concrete actions rather than the vague score-1 or partial score-2 anchors.

3 / 3

Completeness

Explicitly answers both what ("Structured workflows for investigating production issues in Honeycomb") and when (trigger phrases plus "or any request to investigate or debug production problems"), satisfying the score-3 anchor; voice is third person so no specificity penalty applies.

3 / 3

Trigger Term Quality

Provides broad coverage of natural phrases users would actually say — "debug latency spike", "why is my API slow", "errors are increasing", "SLO burning", "debug an outage" — matching the score-3 anchor; not reduced to 2 because common variations are well represented.

3 / 3

Distinctiveness Conflict Risk

Anchored to a clear Honeycomb niche with distinctive triggers ("use BubbleUp", "SLO burning") unlikely to fire for unrelated skills; not scored 2 because the domain-specific triggers prevent the overlap seen in the score-2 example.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
honeycombio/agent-skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.