CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

65%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 lean, information-dense reference-style skill that assumes competence and delivers package-specific facts Claude cannot know, with mostly executable code patterns and concrete example pointers. Its weaknesses are the absence of any explicit workflow sequence or validation checkpoints, and the monolithic single-file structure that inlines a long API symbol dump instead of splitting it into a referenced file.

Suggestions

Move the 'Relevant API Surface' symbol dump into a separate reference file (e.g., references/api-surface.md) and link to it from SKILL.md, keeping only the handful of symbols needed for the core patterns inline.

Add a short ordered workflow for the main use cases (e.g., 1. find the closest example in examples/, 2. adapt it, 3. verify with a no-key run) so the implicit sequence becomes explicit with a validation checkpoint.

Make the code examples self-contained by showing how `llm` and `usage_queue` are obtained (e.g., a one-line AxAI construction and queue creation) so the patterns are copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is dense and list-based, assumes Claude's competence (e.g., 'Real network support: yes', 'Runtime profiles: `javascript-quickjs`, `python-pyodide`'), and never explains concepts Claude already knows. Minor trimmable content exists — the opening paragraph restates the description and the 'Relevant API Surface' symbol dump runs long — matching anchor 4 ('efficient; minor instances that could be trimmed') rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Provides real-syntax code examples ('from axllm import agent; helper = agent("question:string -> answer:string")' and 'set_usage_observer(usage_queue.put_nowait)') plus concrete file pointers ('examples/', 'src/examples/python/generation/usage-observer.py', 'API.md'). Not fully copy-paste ready — `llm` and `usage_queue` are undefined — so it matches anchor 4 ('mostly executable; concrete code with minor gaps') rather than anchor 5, and is well above anchor 3's pseudocode.

4 / 5

Workflow Clarity

The body is organized by topic ('When To Use', 'Core Pattern', 'Centralized Usage Observer', 'Guardrails') with useful decision rules ('Use `no-key` examples for deterministic local checks'), but there is no explicit multi-step sequence or validation checkpoints — sequence is only implicit in the section ordering. Fits anchor 3 ('sequence present but checkpoints missing or implicit'); no destructive/batch operations apply the hard cap, and anchor 4's 'clear sequence with most checkpoints' is not met.

3 / 5

Progressive Disclosure

The skill is a single ~65-line file with no bundle (no references/, scripts/, or assets/ exist), and it points to external artifacts ('API.md', 'axir-capabilities.json', 'examples/') that are not part of the skill bundle. The long inline 'Relevant API Surface' symbol dump is content that clearly belongs in a separate reference file, matching anchor 3 ('content that should be separate is inline') rather than anchor 4's appropriately placed bulk content; the under-50-lines exception for a 5 does not apply.

3 / 5

Total

14

/

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: it pairs an explicit 'Use when' trigger clause with a concrete enumeration of the package's capability areas and is firmly anchored to a specific package, making it highly distinguishable. The main gaps are missing common synonyms (observability, monitoring, telemetry) and capability nouns that could be more action-oriented.

DimensionReasoningScore

Specificity

Names the domain ('writing Python code with `axllm`') and lists several concrete capability areas ('agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging'). Falls between anchors 4 and 5: the list is broad but items are feature nouns rather than fully concrete actions, leaving minor coverage gaps — not the comprehensive verb-plus-object coverage of anchor 5, well above the 1-2 actions of anchor 3.

4 / 5

Completeness

Explicitly answers both: what ('writing Python code with `axllm` for agent tracing, ... usage accounting, ... production debugging') and when ('Use when writing Python code with `axllm` for...'), with concrete trigger purposes enumerated in the when-clause itself. Clearly matches anchor 5 rather than anchor 4, whose 'when' is less specific — here the trigger context (Python + axllm + named purposes) is explicit and concrete.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'agent tracing', 'usage accounting', 'action logs', 'runtime diagnostics', 'replay', and 'production debugging'. Anchor 5 requires synonyms and variations; common alternatives like 'observability', 'monitoring', 'telemetry', or 'logging' are absent, matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 3's missing common variations.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific package ('`axllm`', 'Python'), giving it a clear niche, but generic industry terms like 'agent tracing' and 'production debugging' create minor overlap risk with other observability/tracing skills. Fits anchor 4 ('mostly distinct; minor overlap risk') better than anchor 5, which expects minimal conflict risk from distinct triggers.

4 / 5

Total

17

/

20

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.

Validation — 15 / 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

Path

packages/python/skills/ax-python-agent-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.