CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-agent-observability

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

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/rust/skills/ax-rust-agent-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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, well-sectioned orientation skill whose usage-observer guidance is genuinely dense with non-obvious operational detail (queue bounding, fail-open semantics, teardown, cost calculation). However, its code snippets are fragmentary rather than executable, the multi-step tasks lack any sequenced workflow with validation checkpoints, and the inline API symbol dump is reference content that belongs in a separate file.

Suggestions

Make the Core Pattern snippet self-contained: show the `use` imports and how `llm` is constructed (e.g., via an `AxAI`/no-key client) so `helper.forward(...)` is copy-paste runnable.

Add a short ordered workflow for the main tasks (e.g., 1. pick a matching example from `examples/`, 2. adapt the call shape, 3. verify deterministically with a no-key scripted run) with an explicit validation checkpoint.

Move the "Relevant API Surface" symbol list into a bundled reference file (e.g., `references/api-surface.md`) and link to it, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific ("The observer is process-wide, best-effort, and fail-open", "Nested `attributes` are shallow-merged") with no explanations of concepts Claude already knows, but the ~40-symbol "Relevant API Surface" dump and parts of "Package Facts" are token cost that could be trimmed or moved — anchor 4's "minor instances" of excess rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

The snippets are real Rust but not executable as written — "helper.forward(&llm, inputs, None)?" leaves `llm` and `inputs` undefined with no imports shown, and the observer snippet references an undefined `usage_queue` — matching anchor 3's "concrete guidance but incomplete... missing key details" rather than anchor 4's mostly-executable bar; the pointer to "src/examples/rust/generation/usage_observer.rs" mitigates but does not close the gap.

3 / 5

Workflow Clarity

The skill covers several multi-part tasks (register the observer, attribute usage by tenant, debug agent loops) but presents them as capability sections plus guardrails ("Start from package examples for exact native syntax") with no sequenced steps or validation checkpoints for any task; no destructive or batch operations apply a cap, so it sits at anchor 3 rather than anchor 4's "clear sequence with most checkpoints".

3 / 5

Progressive Disclosure

Sections are well organized with headers, but the inline "Relevant API Surface" symbol list is reference material that belongs in a separate file, and the cited paths ("API.md", "axir-api.json", "examples/") point to the external generated package rather than a skill bundle — no references/, scripts/, or assets/ directories exist to verify — fitting anchor 3's "content that should be separate is inline" rather than anchor 4's mostly-appropriate placement.

3 / 5

Total

13

/

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 explicitly states both what the skill does and when to use it, names six concrete capabilities, and is tightly scoped to the axllm Rust package so conflict risk is minimal. Its main weaknesses are the missing observability/telemetry synonym triggers and a single fused when-clause that lacks separate user-mention trigger conditions.

DimensionReasoningScore

Specificity

Lists six concrete capabilities — "agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging" — comprehensively covering the skill's actual scope; "production debugging" is slightly contextual but not a coverage gap, so this matches anchor 5 rather than anchor 4's "minor gaps in coverage".

5 / 5

Completeness

Both parts are explicit — "Use when writing Rust code with `axllm`" answers when, and the capability list answers what — but the when is a single fused condition with no separate user-mention triggers (e.g., "when the user mentions traces, tenants, or usage"), fitting anchor 4's "'when' could be more explicit or specific" rather than anchor 5.

4 / 5

Trigger Term Quality

Good natural keywords ("agent tracing", "usage accounting", "action logs", "replay", "Rust", "axllm") but missing common synonyms such as "observability", "telemetry", "monitoring", or "metrics" — notably the skill's own name-word "observability" never appears — matching anchor 4's "a few natural terms missing" rather than anchor 5's synonym-rich coverage.

4 / 5

Distinctiveness Conflict Risk

The pairing of "Rust code with `axllm`" with package-specific features (multi-tenant usage attribution, action logs, replay) carves a clear niche with distinct triggers and minimal conflict risk against generic Rust or observability skills, matching anchor 5.

5 / 5

Total

18

/

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/rust/skills/ax-rust-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.