CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-java-agent-observability

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

Quality

84%

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

75%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, information-dense reference skill: executable core snippets, concrete guardrails, and sensible delegation of bulk documentation to package files. The main improvements are showing the usageContext/AI-service call shapes in code and moving the raw API-surface listing into a separate reference file.

Suggestions

Add a short executable snippet showing usageContext attachment (service default plus per-call override) since attribution is the skill's headline use case but currently appears only in prose.

Move the 'Relevant API Surface' class-name listing into a separate reference file (or the already-mentioned API.md) and keep only the handful of classes used in the core patterns inline.

Present the usage-observer lifecycle as an explicit numbered sequence (register → enqueue synchronously → attach context → clear on teardown) so the production guidance reads as a checklist rather than scattered bullets.

DimensionReasoningScore

Conciseness

The body is dense and informational — bullets like "The observer is process-wide, best-effort, and fail-open" and the two code snippets carry real payload with no padding, and nothing explains concepts Claude already knows. Minor trimming is possible (the 'Package Facts' list repeats the frontmatter's language/package, and the 'Relevant API Surface' list is a long token dump), so it sits at 4 rather than the fully lean 5.

4 / 5

Actionability

Concrete, executable code is given for the core flow ("AxGlobals.setUsageObserver(usageQueue::add)") and the Core Pattern, with a pointer to a runnable example (`src/examples/java/generation/UsageObserverExample.java`) and crisp directives in Guardrails. The gap keeping it below 5: key operations like attaching `usageContext` in option maps and the AI-service setup (`Ax.ai`, typesafe clients) are described in prose but never shown in code.

4 / 5

Workflow Clarity

The reference-style layout (When To Use → Package Facts → Core Pattern → observer guidance → Guardrails) gives a coherent path, and guardrails like "Start from package examples for exact native syntax before inventing a new call shape" act as implicit checkpoints; no destructive or batch operations exist that would require validation loops. It stays at 4 rather than 5 because the observer section's ordering (register → enqueue → attribute → clear on teardown) is implicit across bullets rather than presented as an explicit sequence.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so the skill is a single well-sectioned SKILL.md; bulk detail is appropriately delegated to package-side files (`API.md`, `axir-api.json`, `examples/`) with one clearly signaled example path. It is not a 5 because the long inline 'Relevant API Surface' class-name list is content that would fit better in a separate reference file, a mild version of the anchor-3 pattern.

4 / 5

Total

16

/

20

Passed

Description

87%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 names a specific package and language, enumerates six concrete capability areas, and leads with an explicit 'Use when' trigger clause. The only refinement would be converting noun-phrase capabilities into verb-led actions and adding a few common synonyms like 'observability' or 'telemetry'.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging" — giving clear, specific coverage of the skill's scope. It falls short of a 5 because the items are domain noun phrases rather than explicit actions (no verb-led tasks like 'trace agent loops' or 'register a usage observer'), leaving minor gaps in how the capabilities are exercised.

4 / 5

Completeness

Opens with an explicit trigger clause — "Use when writing Java code with `dev.axllm:ax` for agent tracing, ... or production debugging" — and the enumerated capability list concretely answers both what the skill covers and when to reach for it. It matches the 5 anchor (explicit when with concrete trigger phrases) rather than 4, where the 'when' would be generic or less specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "agent tracing", "usage accounting", "action logs", "production debugging", plus the package coordinate `dev.axllm:ax` and "Java", which users of this package would naturally mention. A few natural synonyms are missing (e.g., "observability", "telemetry", "monitoring", "metrics"), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The combination of "Java", the specific package `dev.axllm:ax`, and the observability capability list carves out a clear niche with minimal overlap risk against generic Java, logging, or debugging skills. It clearly fits the 5 anchor (clear niche with distinct triggers) rather than the 4 anchor's 'minor overlap risk with closely related skills'.

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