CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-go-agent-observability

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.

Quality

74%

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

Quality

Content

50%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.

The body is well-sectioned and the centralized-usage-observer guidance is genuinely expert-grade, but it falls short on executability and navigation: only one of the six advertised capabilities has working code, the API surface is a context-free symbol dump, and every referenced file (API.md, examples/, the usage_observer example) is missing from the bundle so nothing can actually be navigated to. It reads as a truncated reference card rather than an actionable skill.

Suggestions

Move the ~40-entry 'Relevant API Surface' symbol list into a references/api-surface.md file and keep only the handful of symbols used in the body's examples, so the inline content instructs instead of enumerating.

Add a short executable snippet for each headline capability in the description (tracing, action logs, replay, diagnostics) — currently only usage accounting has one — or link to concrete example files that actually ship in the skill bundle.

Resolve the dangling references: 'API.md', 'axir-api.json', 'axir-capabilities.json', 'examples/', and 'src/examples/go/generation/usage_observer.go' do not exist in the skill bundle; either include them under references/ and examples/ or reword the paths so they point at files the skill actually carries.

DimensionReasoningScore

Conciseness

Most sections are dense and efficient ('Package Facts', the observer bullets give genuinely non-obvious production guidance), but the 'Relevant API Surface' section is a ~40-symbol name dump (e.g. 'axllm.AxBalancer', 'axllm.MultiServiceRouter', 'axllm.CreateBalancerRouteStats') with no context — tokens that neither explain nor instruct. This fits anchor 3 (mostly efficient but some unnecessary content that could be tightened) better than anchor 4.

3 / 5

Actionability

Two snippets are executable ('helper := ax.NewAgent("question:string -> answer:string", nil)...' and the SetUsageObserver example), but the headline capabilities in the description — agent tracing, action logs, replay, runtime diagnostics — have no code at all, and the API surface is given as bare symbol names. This is concrete-but-incomplete guidance, matching anchor 3; anchor 4 would require only minor gaps.

3 / 5

Workflow Clarity

There is no multi-step sequence or validation checkpoint anywhere; the Guardrails section provides only partial ordering ('Start from package examples for exact native syntax before inventing a new call shape', 'Clear it during test teardown'). Structure exists (task-oriented sections, do/don't guidance) but no explicit steps or checkpoints, sitting between anchors 2 and 3 and fitting 3.

3 / 5

Progressive Disclosure

The body has clear section headers and points to external materials ('API.md', 'axir-capabilities.json', 'examples/', 'src/examples/go/generation/usage_observer.go'), but none of these files exist in the skill bundle — there is no references/ or examples/ directory alongside SKILL.md — and the long inline API symbol list is content that clearly belongs in a separate reference file. This matches anchor 3 (some structure, references present but not resolvable, content that should be separate is inline) rather than anchor 4.

3 / 5

Total

12

/

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 pairs a concrete trigger clause ('Use when writing Go code with <package>') with an explicit enumeration of the package's observability capabilities, and it is tightly scoped to one package so conflict risk is minimal. The only weaknesses are mild: capability areas are listed as nouns rather than actions, and a few natural synonyms (observability, monitoring, telemetry) are absent.

DimensionReasoningScore

Specificity

The description names the domain ('writing Go code with `github.com/ax-llm/ax/packages/go`') and lists six specific capability areas ('agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging'). These are concrete capability nouns rather than crisp actions like the anchor-5 'extract/fill/merge' example, and a few package capabilities are unmentioned, so it fits anchor 4 (several specific actions, minor gaps) better than 5.

4 / 5

Completeness

It explicitly answers both questions: 'what' via the enumerated capabilities ('agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging') and 'when' via the concrete trigger phrase 'Use when writing Go code with `github.com/ax-llm/ax/packages/go`'. This matches the anchor-5 pattern of a clear what plus an explicit, specific when; anchor 4 would require the 'when' to be less explicit, which is not the case here.

5 / 5

Trigger Term Quality

It includes natural phrases users would say such as 'Go code', 'agent tracing', 'replay', and 'production debugging', giving good keyword coverage. Common variations a user might naturally say — 'observability', 'monitoring', 'telemetry', 'metrics' — are missing, so it does not reach the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The trigger is anchored to a single specific Go package import path, creating a clear niche with distinct triggers and minimal conflict risk with any other skill. A skill would only fire here when that exact package is in use, 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/go/skills/ax-go-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.