CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-go-llm

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for using the generated Ax package, factory functions, package docs, examples, and API reference.

Quality

83%

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

86%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-built progressive-disclosure router: lean overview, task-mapped table to 16 real one-level-deep guides, and useful conventions (version check, authoritative API sources). The only notable gaps are the absence of any inline quick-start snippet and a missing recovery path for version mismatches.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence: "Read the guides relevant to the task before writing code", "Check the installed package version against the guide version", and a task→file table. No padding, no explanation of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

Concrete, actionable routing: a 16-row task→file table and named authoritative sources ("Use the package's `API.md`, `axir-api.json`, and `axir-capabilities.json` for exact signatures"). Falls short of 5 because no executable snippet or quick-start example appears inline — the reader must always open a reference first, which is a minor gap even for a router skill.

4 / 5

Workflow Clarity

The sequence is clear — identify the task, read the matching guide before writing code, check the installed version against the guide version, verify exact signatures in API.md — and the version check acts as an explicit checkpoint. Not 5 because there is no guidance for what to do when versions mismatch (no feedback/recovery loop).

4 / 5

Progressive Disclosure

Verified against the actual bundle: all 16 files referenced in the task table exist under references/, references are exactly one level deep (no nested references/ links inside the guides; API.md mentions point to the external package's files), and the overview body is appropriately split with well-signaled, easy-to-navigate pointers.

5 / 5

Total

18

/

20

Passed

Description

73%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 distinctive, well-triggered description anchored by the exact package path, with an explicit use-when clause. Its main weakness is the what-side: it lists resources with generic verbs ("using") instead of concrete capabilities such as creating provider clients, defining signatures, or building agents.

Suggestions

Replace the generic verb chain 'for using the generated Ax package, factory functions, package docs, examples, and API reference' with concrete capabilities, e.g. 'Create provider clients, define typed signatures, build RLM agents, and orchestrate workflow graphs using the generated Ax package'.

Add a few natural trigger synonyms such as 'Golang', 'Ax for Go', or 'ax Go SDK' so users phrasing the need differently still match the skill.

State what the skill does for the user in a crisp subject-verb form ('Guides writing…', 'Provides factory functions, docs, and API reference for…') so the what-half is as explicit as the when-half.

DimensionReasoningScore

Specificity

The description names the domain with precision ("github.com/ax-llm/ax/packages/go") and lists resources ("factory functions, package docs, examples, and API reference"), but the only action verbs are the generic "writing" and "using" — it enumerates objects rather than concrete actions like the 4-5 anchors require.

3 / 5

Completeness

Both parts are present: an explicit "Use when writing Go code with…" trigger clause and a what-side covering "the generated Ax package, factory functions, package docs, examples, and API reference". Not 5 because the what is an awkward, loosely framed resource list ("for using… for using") rather than clearly stated capabilities.

4 / 5

Trigger Term Quality

"writing Go code" plus the exact import path "github.com/ax-llm/ax/packages/go" are natural, high-precision phrases a user would say or have in their go.mod. It falls short of 5 because common synonyms like "Golang", "SDK", or "Ax for Go" are absent, but is well above 3 since the core natural terms are covered.

4 / 5

Distinctiveness Conflict Risk

The exact package import path creates a clear niche with distinct triggers and minimal conflict risk — it would only fire for work with this specific package, matching the 5 anchor.

5 / 5

Total

16

/

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-llm/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.