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

68%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, code-heavy reference with a clean overview/advanced split into references/details.md and mostly executable examples. Its main weakness is workflow clarity: it reads as a pattern catalog without an implementation order or concrete verification loop, and a few code snippets contain undefined variables.

Suggestions

Add a short recommended implementation order (configure logging -> correlation-ID middleware -> golden-signal metrics -> tracing) ending with an explicit verification step (e.g., confirm JSON log output renders and /metrics responds) to give the pattern catalog a workflow backbone.

Fix the incomplete snippets: define `elapsed` in Pattern 2's completion log and bind `e` in Pattern 3's ERROR example so every code block is copy-paste ready.

Enumerate the advanced-pattern topics in the details.md pointer (Prometheus golden signals, bounded cardinality, timing context manager, OpenTelemetry tracing) so navigation to the reference is fully self-describing.

DimensionReasoningScore

Conciseness

Prose is tight and code-dominant ("Keep metric label values bounded. Unbounded labels (like user IDs) explode storage costs."), but the Quick Start structlog config duplicates Pattern 1's fuller configuration, and the DEBUG/INFO/WARNING/ERROR table explains log-level basics Claude already knows. These are minor instances of over-explanation that could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Most code is executable and copy-paste ready (Quick Start, Pattern 1 configuration, Pattern 4 FastAPI middleware and httpx propagation), but Pattern 2 references an undefined `elapsed` variable and Pattern 3's ERROR example uses an undefined `e`. Concrete guidance with minor gaps matches anchor 4; not 5 due to those incomplete snippets.

4 / 5

Workflow Clarity

The body is a pattern catalog with no implementation sequence (e.g., configure logging -> add correlation middleware -> instrument metrics -> add tracing) and validation appears only as a vague bullet ("Test your observability - Verify logs and metrics in integration tests") with no checkpoints or feedback loop. Steps/structure are present but checkpoints are missing or implicit, matching anchor 3; not 4 because there is no real sequenced workflow, not 2 because the overall organization (When to Use -> Concepts -> Quick Start -> Patterns -> Best Practices) is coherent.

3 / 5

Progressive Disclosure

A single one-level-deep, clearly signaled, verified reference ("Detailed sections (starting with `## Advanced Patterns`) live in `references/details.md`. Read that file when the navigation summary above is insufficient.") with advanced patterns appropriately split out of the overview. Not 5 because the pointer does not enumerate the advanced topics (Prometheus golden signals, bounded cardinality examples, timing context manager, OpenTelemetry tracing), leaving Core Concepts topics without explicit pointers; not 3 since the reference is prominent and the split is sensible.

4 / 5

Total

15

/

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 that follows the ideal what-plus-when structure: it names the domain and its three pillars, then gives four explicit trigger phrases. The only gaps are missing common synonyms (monitoring, telemetry, instrumentation) and slight breadth in 'debugging production systems'.

DimensionReasoningScore

Specificity

Names the domain and three concrete capability areas ("structured logging, metrics, and distributed tracing"), matching the 'several specific actions with minor gaps' anchor. Not 5 because capabilities are listed as areas rather than a comprehensive set of concrete actions; not 3 because it clearly exceeds 1-2 actions.

4 / 5

Completeness

Explicitly answers both 'what' ("Python observability patterns including structured logging, metrics, and distributed tracing") and 'when' with four concrete trigger phrases in a 'Use when...' clause. Matches the anchor-5 good example structure; the 'when' is explicit and specific, so not 4.

5 / 5

Trigger Term Quality

"adding logging", "implementing metrics collection", "setting up tracing", and "debugging production systems" are natural phrases a user would say. Not 5 because common synonyms like "monitoring", "telemetry", "instrumentation", or tool names like "Prometheus" are missing; not 3 because multiple natural trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

"Python observability" is a clear niche with distinct triggers (structured logging, tracing, metrics collection). Minor overlap risk from the broad "debugging production systems" phrase, so not 5; the core triggers are niche-specific, so not 3.

4 / 5

Total

17

/

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

wshobson/agents

Path

plugins/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.