CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

honeycomb-tracing

Trace 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.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An excellent operational skill body: exceptionally actionable with exact commands, filters, span names, and seam paths; a clearly phased workflow with real validation checkpoints; and well-structured one-level-deep references verified against the actual bundle. The only slack is a handful of trimmable, mildly time-sensitive anecdotes.

DimensionReasoningScore

Conciseness

The body is dense with project-specific operational detail (span names, correlation hashing, permission caveats) and explains nothing Claude already knows, but a few spots could be trimmed — notably the time-sensitive "In recent investigations, HONEYCOMB_TEST_CONFIG_API_KEY…" anecdote and some doubly-nested caveats. Not 5 due to these minor instances of trimmable material; well above 3 since there is no conceptual padding.

4 / 5

Actionability

Guidance is fully concrete and executable: a copy-paste sha256 hash command with the trailing-newline caveat, exact filter attributes (`paperclip.task.run.run_id`, `service.name = paperclip`), the exact root filter `name in [task.execution_attempt, task.provider_session, task.run]`, and exact instrumentation seam file paths with function names. This covers the common cases with commands and specifics rather than abstraction.

5 / 5

Workflow Clarity

A clear phased sequence (choose data path → find trace → read timeline → design waterfall → add instrumentation → compare and report) with explicit validation steps ("Run focused tests for endpoint-off behavior, parentage/concurrent-run isolation, failure handling", "Use real exported evidence to claim that new spans appear") and error-recovery feedback ("Remove the name filter when setup failed", "when queries are unavailable, use the signed-in UI"). The destructive/batch cap does not apply since validation steps are present.

5 / 5

Progressive Disclosure

The body opens with a question-based routing table and keeps overview-level guidance inline, while pushing CI profiling, runtime setup, and trace design into three clearly signaled one-level-deep references (references/ci.md, references/runtime.md, references/trace-design.md) that all exist and match their cited anchors. Content is appropriately split and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

83%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: concrete, domain-anchored, and clearly distinguishable, with an explicit "Use to…" trigger clause covering its five capabilities. The only weakness is that triggers are capability phrases rather than user-situation phrasing, and a few natural synonyms (observability, OTel, slow runs) are absent.

DimensionReasoningScore

Specificity

"find traces, diagnose latency, design readable and foldable waterfalls, configure opt-in OpenTelemetry, or add missing spans" lists five concrete actions with concrete objects, comprehensively covering the skill's niche. Score 4 would apply only if there were coverage gaps, which there are not within this domain.

5 / 5

Completeness

The "what" is explicit ("Trace Paperclip runs, requests, and full CI suites in Honeycomb") and an explicit trigger clause exists ("Use to find traces, diagnose latency, …"). It falls short of a 5 because the triggers are phrased as purposes rather than user situations (e.g., "Use when investigating slow runs or missing spans"), and clears 3 because an explicit "Use to…" clause is present.

4 / 5

Trigger Term Quality

Natural domain terms are present ("Honeycomb", "trace", "CI suites", "latency", "waterfalls", "OpenTelemetry", "spans") and users would say them, but common variations like "observability", "OTel", or "slow runs/tasks" are missing. Not 5 because synonym coverage is incomplete; not 3 because several genuinely natural keywords appear.

4 / 5

Distinctiveness Conflict Risk

"Honeycomb", "Paperclip runs", "waterfalls", and "spans" carve out a clear niche with distinct triggers; minimal risk of firing for an unrelated skill. Only a generic latency-diagnosis phrase overlaps slightly with other debugging skills, but the Honeycomb/Paperclip framing disambiguates.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

paperclipai/paperclip

Path

.agents/skills/honeycomb-tracing/SKILL.md

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.