observability-fundamentals

First principles behind observability — wide events, high cardinality, the core analysis loop, events vs metrics vs logs, and how instrumentation connects to debugging outcomes. Grounds recommendations in first principles rather than tool-specific how-to. Trigger phrases: "what is observability", "why observability", "why Honeycomb", "events vs metrics vs logs", "events vs metrics", "events vs logs", "metrics vs logs", "why wide events", "what is high cardinality", "core analysis loop", "observability vs monitoring", "what is dimensionality", "explain observability", or any conceptual question about observability or why Honeycomb's approach differs from traditional monitoring.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured conceptual skill: lean body, clear sequenced analysis loop, and clean one-level-deep references to a real bundle file. The main weakness is body-level actionability — it is descriptive rather than executable and defers concrete examples entirely to the reference.

Suggestions

Add 1–2 short in-body executable snippets (e.g. a minimal span with attributes, or a sample BubbleUp-style query) so the skill is actionable without forcing a reference read.

Tighten the "Instrumentation as a Development Practice" section, which restates general engineering practice Claude already knows, to improve token efficiency.

Add an explicit validation/checkpoint cue in the analysis loop (e.g. how to confirm a hypothesis is ruled out before looping) to push workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and well-organized (definitions, compact comparison tables, focused Honeycomb-specific framing) with only minor over-explanation, e.g. the "Instrumentation is not a one-time setup task" paragraph edges toward material Claude already knows. Not a 5 due to those few trimmable sentences.	4 / 5
Actionability	As an instruction-only conceptual skill it offers some concrete guidance (the Define→Visualize→Investigate→Evaluate loop and the who/what/where attribute categories), but the body itself is mostly descriptive framing rather than executable steps, and it delegates code examples entirely to the reference file. It lands between anchor 3 (some concrete guidance, missing key details) and 4.	3 / 5
Workflow Clarity	The Core Analysis Loop is a clearly numbered sequence (Define→Visualize→Investigate→Evaluate) with an explicit feedback loop ("Then loop — each answer raises new questions" and the with/without-suspected-cause query in Evaluate). It is not a destructive/batch operation so the validation cap does not apply; minor checkpoint gaps keep it just below 5.	4 / 5
Progressive Disclosure	The body is a clear overview with well-signaled one-level-deep references to the real bundle file references/events-vs-metrics-vs-logs.md and clearly labeled cross-references to sibling skills/agent. Content is appropriately split (code examples pushed to the reference) and navigation is easy.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 strong description: it covers what the skill does, when to use it via explicit trigger phrases, and is clearly distinguished from sibling tool-specific skills. The only minor gap is that its "actions" are conceptual framing rather than discrete task verbs.

Dimension	Reasoning	Score
Specificity	The description names several concrete domain subjects ("wide events, high cardinality, the core analysis loop, events vs metrics vs logs") and concrete actions ("grounds recommendations", "answer conceptual questions"). It stops just short of the comprehensive multi-action list of a 5 because its actions are conceptual framing rather than discrete task operations.	4 / 5
Completeness	It clearly answers "what" (first principles behind observability) and explicitly answers "when" with concrete trigger phrases plus a catch-all clause for conceptual observability questions, matching the anchor exactly.	5 / 5
Trigger Term Quality	An explicit "Trigger phrases:" list includes natural user phrasings with synonyms and variations ("what is observability", "events vs metrics vs logs", "observability vs monitoring", "why Honeycomb", "explain observability"), matching the comprehensive coverage anchor.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche (observability first principles / Honeycomb's approach) and explicitly steers away from tool-specific SDK skills ("rather than tool-specific how-to"), with distinct triggers and minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: honeycombio/agent-skill
Path: honeycomb/skills/observability-fundamentals/SKILL.md
Commit: 41214b7

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.