CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-agent-observability

This skill helps an LLM generate correct AxAgent observability code using @ax-llm/ax. Use when the user asks about axGlobals.onUsage, usageContext, centralized or multi-tenant usage accounting, actorTurnCallback, onContextEvent, agentStatusCallback, onFunctionCall, reportSuccess, reportFailure, getChatLog(), getUsage(), resetUsage(), debug traces, progress updates, or telemetry for AxAgent runs.

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

78%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, highly actionable reference for AxAgent observability with executable examples and precise type information throughout. Its weaknesses are inlined per-hook reference material that belongs in bundle files and some redundant or wordy passages.

Suggestions

Move the per-hook API detail (e.g., the actorTurnCallback/onContextEvent sections with their full type signatures) into references/ files, keeping SKILL.md as the hook-selection overview with one-line pointers per hook.

Remove the duplicated actorTurnCallback type signature; state once that a deprecated alias of the same shape exists instead of reprinting the full block.

Add a short verification step for wiring (e.g., how to confirm axGlobals.onUsage events arrive or that agentStatusCallback is firing) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is dense with non-derivable, API-specific facts and avoids explaining general concepts, but the actorTurnCallback type signature is printed twice verbatim (once as a deprecated alias) and several rule lists could be tightened. Efficient overall with minor trimmable redundancy fits anchor 4, not the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Every hook has copy-paste-ready TypeScript configuration plus exact type signatures (e.g., the full actorTurnCallback turn shape, the usageContext attribution object, getStagedUsage()/getTraces()/resetUsage() calls) covering the common cases. This matches the fully-executable anchor 5; it is clearly above anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

The 'Choose The Smallest Hook' section provides a clear selection sequence with escalation rules ('Do not add multiple hooks unless...') and teardown guidance, but there is no validate/verify loop for confirming wiring (e.g., that the usage observer actually emits). Clear sequence with most checkpoints present fits anchor 4 rather than the explicit-feedback-loop anchor 5.

4 / 5

Progressive Disclosure

Roughly 400 lines of per-hook API reference are inlined entirely in SKILL.md with no bundle files; the only clearly signaled external pointer is 'also read ax-ai'. Sections are well-organized, but content that should live in separate reference files (per-hook API details, event shapes) is inline, matching anchor 3.

3 / 5

Total

16

/

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 with an explicit what-and-when structure and a rich, concrete trigger list drawn from the actual API surface. Its main weaknesses are a thin action statement in the what-clause and trigger terms that partially overlap sibling ax skills.

DimensionReasoningScore

Specificity

The what-clause names one action ("helps an LLM generate correct AxAgent observability code using @ax-llm/ax") but the enumerated API surface (actorTurnCallback, getChatLog(), getUsage(), reportSuccess, etc.) makes the capabilities concrete. It lists several specific items with minor gaps rather than a comprehensive action list, fitting anchor 4.

4 / 5

Completeness

Explicitly answers both what ("generate correct AxAgent observability code using @ax-llm/ax") and when ("Use when the user asks about..." followed by concrete trigger phrases). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Includes exact API names users would type plus natural phrasings like "centralized or multi-tenant usage accounting", "debug traces, progress updates, or telemetry for AxAgent runs". Coverage is good but misses a few natural terms (getStagedUsage(), getTraces(), OpenTelemetry), so it is not anchor 5.

4 / 5

Distinctiveness Conflict Risk

AxAgent-specific hook names (axGlobals.onUsage, agentStatusCallback, actorTurnCallback) form a clear niche, but generic terms like "telemetry", "getUsage()", and "getChatLog()" overlap with the closely related ax-ai and other ax skills. Minor overlap risk with closely related skills fits anchor 4, not the minimal-conflict anchor 5.

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

website/static/typescript/.well-known/agent-skills/ax-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.