CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

python-observability

Python observability patterns including structured logging, metrics, and distributed tracing. Use when adding logging, implementing metrics collection, setting up tracing, or debugging production systems.

Quality

81%

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

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 well-organized, actionable pattern catalog with executable code for logging, metrics, and tracing. Its main costs are token inefficiency — re-explaining basics Claude already knows and duplicating concepts between sections — and a monolithic ~400-line body that would benefit from splitting advanced patterns into reference files.

Suggestions

Remove the 'Core Concepts' section (it duplicates the pattern introductions) and the DEBUG/INFO/WARNING/ERROR table in Pattern 3 — Claude already knows standard log-level semantics; keep only the field examples.

Split the advanced patterns (Prometheus golden signals, OpenTelemetry tracing) into references/ files (e.g., METRICS.md, TRACING.md) and keep one-line pointers in SKILL.md to reduce the always-loaded token footprint.

Tighten the code examples so they are copy-paste ready: define or remove the undefined elapsed/Request/Response variables in Pattern 2, and actually apply service_name to the OTel TracerProvider via a Resource in Pattern 8.

DimensionReasoningScore

Conciseness

The body is mostly efficient pattern-and-code, but includes content Claude already knows: a Core Concepts section that re-summarizes what the patterns then cover, a log-level table explaining what DEBUG/INFO/WARNING/ERROR mean, and filler like 'Machine-readable logs enable powerful queries and alerts'. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Most patterns give concrete, executable code (structlog configuration, Prometheus collectors, FastAPI correlation middleware, OTel spans), matching anchor 4. It is not 5 because some examples have gaps that block copy-paste use: Pattern 2 references undefined variables (elapsed, Request, Response) and configure_tracing takes service_name but never applies it to the TracerProvider/resource.

4 / 5

Workflow Clarity

The content progresses coherently (Quick Start → fundamental patterns → advanced patterns → best-practices summary) with each pattern a self-contained, unambiguous instruction, matching anchor 4's 'clear sequence with most checkpoints present'. No validation checkpoints exist, but none are required since the skill involves no destructive or batch operations, so the cap does not apply; a 5 would need explicit validation steps or error-recovery loops that a pattern catalog doesn't have.

4 / 5

Progressive Disclosure

This is a ~400-line single file with no bundle files; substantial advanced material (full OTel setup, Prometheus instrumentation details) that would fit naturally in references/ is inlined. Section headers are clear, which keeps it above 2, but it matches anchor 3 ('content that should be separate is inline') rather than 4, since the length and topic breadth argue for splitting rather than 'most content appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

88%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: third-person, concrete about capabilities, and with an explicit 'Use when...' clause covering the main use cases. The only weaknesses are a few missing natural synonyms (monitoring, telemetry, instrumentation) and a slightly broad 'debugging production systems' trigger that could overlap with adjacent skills.

DimensionReasoningScore

Specificity

The description names multiple specific concrete actions — 'structured logging, metrics, and distributed tracing' plus 'adding logging, implementing metrics collection, setting up tracing, or debugging production systems' — with comprehensive coverage of the observability domain. It matches the anchor 5 example (multiple specific actions, comprehensive coverage) and is not a 4, which would require noticeable coverage gaps.

5 / 5

Completeness

It explicitly answers 'what' ('Python observability patterns including structured logging, metrics, and distributed tracing') and 'when' ('Use when adding logging, implementing metrics collection, setting up tracing, or debugging production systems') with concrete trigger phrases, exactly matching the anchor 5 example. A 4 would require the 'when' clause to be less explicit or specific.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'adding logging', 'setting up tracing', and 'debugging production systems' are well covered, matching anchor 4's 'good keyword coverage; a few natural terms missing'. It falls short of 5 because common synonyms a user would naturally say — 'monitoring', 'telemetry', 'instrumentation', or named tools like Prometheus/OpenTelemetry that the body covers — are absent.

4 / 5

Distinctiveness Conflict Risk

The Python-observability niche (structured logging + metrics + tracing together) is mostly distinct with clear triggers. It falls short of 5 because 'debugging production systems' is a broad phrase that could overlap with general debugging or incident-response skills, matching anchor 4's 'minor overlap risk with closely related skills'.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Dicklesworthstone/pi_agent_rust

Path

tests/ext_conformance/artifacts/agents-wshobson/python-development/skills/python-observability/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.