enhanced-telemetry

Comprehensive Claude Code telemetry via 10 hooks capturing sessions, conversations, tools, subagents, context, permissions, and repository analytics. Use when analyzing detailed usage patterns beyond default OTEL.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/enhanced-telemetry/SKILL.md

Quality

Content

63%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 detailed, mostly actionable telemetry skill with strong configuration and query examples, weakened by triple-redundant category listings, a missing core script, and inlined reference material that should be split out.

Suggestions

Collapse the redundant 'What It Captures', hook table, and event-schema intros into a single source of truth to remove repeated category listings.

Ship the referenced enhanced-telemetry.py hook script (e.g., in scripts/) so the configuration is actually usable end-to-end.

Move the bulk event schemas and LogQL query catalog into separate reference files linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The 'What It Captures' bullet lists, the '10 Hooks Instrumented' table, and the 'Event Schemas' section restate the same categories three times, adding redundant tokens that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready settings.json, executable LogQL queries, and bash test commands, but the core enhanced-telemetry.py hook script is referenced yet absent from the bundle, leaving a meaningful gap.	4 / 5
Workflow Clarity	The Troubleshooting section is a sequenced diagnostic with explicit validation checkpoints (curl checks), but the primary install/configure flow is not presented as a numbered, validated sequence.	4 / 5
Progressive Disclosure	No bundle files exist and the document is a long monolithic SKILL.md; bulk event-schema and LogQL reference material is inlined that would be better split into separate reference files, though section headers are clear.	3 / 5
	Total	14 / 20 Passed

Description

75%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 solid, third-person description that covers both capability and trigger guidance with concrete telemetry categories. It could be sharpened by adding more distinct action verbs and richer, more specific trigger phrasing.

Suggestions

Replace the single verb 'capturing' with distinct actions (e.g., 'logs, aggregates, and visualizes') to lift specificity toward 5.

Expand the 'Use when' clause with more concrete user-facing triggers (e.g., 'when debugging hook coverage', 'when comparing session tool usage').

Add common synonyms/extensions (e.g., 'observability', 'metrics', 'OTEL') to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capture targets ('sessions, conversations, tools, subagents, context, permissions, and repository analytics') via 10 hooks, but relies on a single action verb ('capturing') rather than multiple distinct actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what (10 hooks capturing the listed analytics) and when ('Use when analyzing detailed usage patterns beyond default OTEL'), but the single 'when' clause is somewhat abstract and could be more specific.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('telemetry', 'usage patterns', 'analyzing') plus the explicit 'Use when' clause, though a few common synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Claude Code telemetry niche with distinct triggers, with only minor overlap risk against closely related observability skills.	4 / 5
	Total	16 / 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: fernandezbaptiste/Skrillz
Path: skills/enhanced-telemetry/SKILL.md
Commit: 93ed392

Reviewed: 2 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.