BD 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.
The skill promises to trace Paperclip runs in Honeycomb: find traces, diagnose latency, configure OpenTelemetry. Four files in the folder, but two references point to nothing—documentation or examples are missing. Quality score 79/100, process score 45—the tool works, but the structure needs work.
No model runs, no sandbox testing. No critical issues found, but broken references signal incompleteness. Compatible with all major platforms including Claude and Cursor. Install if you're already using Honeycomb and don't mind hunting down missing files yourself.
Trace Paperclip runs, requests, and full CI suites in Honeycomb.
As a process D 45/100 · Unfinished process — References files that are not bundled: ../../../doc/observability.md, ../fix-slow-queries/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../doc/observability.md - warning
missing-refreference to a missing file: ../fix-slow-queries/SKILL.md - note
edit-residuethe text marks something as outdated (lines 85): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 45/100
- 0Tools and files. 2 referenced file(s) missing: ../../../doc/observability.md, ../fix-slow-queries/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3010 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 197: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.