CtrlK
BlogDocsLog inGet started
Tessl Logo

python-observability-patterns

Observability patterns for Python applications. Triggers on: logging, metrics, tracing, opentelemetry, prometheus, observability, monitoring, structlog, correlation id.

88

1.17x
Quality

Does it follow best practices?

Impact

100%

1.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code across logging, metrics, and tracing, and is well organized with a quick-reference table. It is held back by a missing bundle (referenced reference/asset files do not exist) and minor duplication of the middleware scaffolding.

Suggestions

Create the referenced bundle files (references/structured-logging.md, references/metrics.md, references/tracing.md, assets/logging-config.py) or remove the dangling references so progressive disclosure reflects the actual bundle.

De-duplicate the @app.middleware('http') scaffolding shared by the request-context and metrics sections, e.g. consolidate into one middleware or reference the first from the second.

Add a brief integration note tying the three pillars together (e.g. how request_id from structlog flows into trace span attributes) to reduce the slight redundancy and improve workflow cohesion.

DimensionReasoningScore

Conciseness

Content is mostly efficient and code-first with a brief one-line intro, but the FastAPI middleware pattern is repeated across the request-context and metrics sections with overlapping @app.middleware scaffolding that could be tightened.

2 / 3

Actionability

Each section provides fully executable, specific, copy-paste-ready code (structlog.configure, Prometheus Counter/Histogram/Gauge, OpenTelemetry TracerProvider) rather than pseudocode.

3 / 3

Workflow Clarity

These are independent single-pattern recipes rather than a multi-step destructive workflow, and each section's single action is unambiguous, satisfying the simple-skill allowance for a score of 3.

3 / 3

Progressive Disclosure

References and an asset are clearly signaled one level deep in dedicated sections, but the referenced bundle files (./references/*.md, ./assets/logging-config.py) do not exist in the skill bundle, so the disclosed structure is not actually present.

2 / 3

Total

10

/

12

Passed

Description

90%

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 with explicit trigger guidance and good natural keyword coverage, clearly scoping a distinct Python observability niche. It could be marginally stronger by listing more granular concrete actions, but it already clearly answers both 'what' and 'when'.

DimensionReasoningScore

Specificity

Names the domain ('Observability patterns for Python applications') and several concrete capabilities (logging, metrics, tracing) but does not enumerate multiple distinct actions as comprehensively as the score-3 anchor.

2 / 3

Completeness

It explicitly answers both 'what' (observability patterns: logging, metrics, tracing) and 'when' via an explicit 'Triggers on' clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

The 'Triggers on' clause lists natural, varied terms users would actually say (logging, metrics, tracing, opentelemetry, prometheus, observability, monitoring, structlog, correlation id), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

It targets a clear niche (Python observability) with distinct, specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NeverSight/skills_feed
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.