CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-python-agent-observability

Use when writing Python code with `axllm` for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/python/skills/ax-python-agent-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body is organized and avoids explaining concepts Claude already knows, with real code examples for the core and observer patterns. It is held back by a heavy inline API-surface dump, an incomplete core example, missing validation checkpoints, and references to bundle files that are not present.

Suggestions

Make the core example self-contained by defining or importing `llm` (e.g. show the client/llm construction) so the snippet runs as written.

Move the large API-surface symbol list into a referenced API.md file and keep SKILL.md to a concise overview, which would improve both conciseness and progressive disclosure.

Add an explicit verification/checkpoint step around process-wide observer registration and teardown (e.g. how to confirm the observer is active and how to clear it on shutdown).

DimensionReasoningScore

Conciseness

Mostly efficient with bullets and short code, but the "Relevant API Surface" section is a dense token-heavy dump of dozens of symbols, and several observer bullets could be tightened; it is not the leanest possible form.

2 / 3

Actionability

Provides concrete executable code for the core pattern and usage observer, but the core example uses an undefined `llm` variable and the large API-surface list is reference, not runnable guidance — key details are missing.

2 / 3

Workflow Clarity

Sections (When To Use, Core Pattern, Guardrails) give an implicit order, and Guardrails offers ordering advice, but there are no explicit validation or verification checkpoints for the risky process-wide observer registration.

2 / 3

Progressive Disclosure

The body is well-sectioned and signals references (API.md, axir-api.json, examples/, usage-observer.py), but no bundle files exist, so the signaled references point to nothing, and the dense API surface that could live in a separate file is inline instead.

2 / 3

Total

8

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, an explicit "Use when" trigger, and a comprehensive list of concrete capabilities tied to a specific generated package. It clearly communicates both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities: "agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging" — a comprehensive list of specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what (the enumerated observability capabilities) and when (the "Use when writing Python code with `axllm` for..." trigger clause).

3 / 3

Trigger Term Quality

Uses natural terms users would say — "writing Python code", "agent tracing", "usage accounting", "production debugging", "replay" — with good coverage of how a user would describe these needs.

3 / 3

Distinctiveness Conflict Risk

The `axllm` package and observability focus create a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
ax-llm/ax
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.