Name: ax-go-llm
Rating: 64 (1 reviews)
Author: ax-llm

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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/go/skills/ax-go-llm/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized quick reference with executable code and clear guardrails. Its main weaknesses are the thin single code example plus flat symbol list (actionability) and a large inline API surface that could be split into a referenced file (progressive disclosure).

Suggestions

Add one or two more complete, copy-paste-ready Go snippets (e.g., a signature + AxGen call, or a Flow) so the core pattern generalizes beyond `NewAI`.

Move the 'Relevant API Surface' symbol catalog into a referenced file (e.g., the existing API.md) and keep SKILL.md as a pointer, deepening the progressive-disclosure structure.

Bundle or verify the referenced files (API.md, axir-api.json, axir-capabilities.json, examples/) so the signaled references resolve to real paths.

Dimension	Reasoning	Score
Conciseness	The body is lean — terse bullets, a compact code snippet, and a symbol list — with no padding or explanations of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It provides one executable snippet (`ax.NewAI(...)`) and a specific symbol catalog, but the single code shape is minimal and the API surface is a flat reference list without per-symbol usage examples, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	For a single-purpose reference skill, the 'When To Use' and 'Guardrails' sections give an unambiguous decision flow ('Start from package examples ... before inventing a new call shape'), meeting the simple-skill allowance for a 3.	3 / 3
Progressive Disclosure	Sections are clearly labeled and references (API.md, examples/) are signaled one level deep, but the large inline 'Relevant API Surface' symbol list is content that arguably belongs in a separate reference file, and no bundle files exist to verify the referenced paths.	2 / 3
	Total	10 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-scoped to a specific Go package with an explicit 'Use when' trigger and answers both what and when. It is slightly held back by listing resources rather than concrete actions and leaning on a technical package path for its trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('writing Go code with `github.com/ax-llm/ax/packages/go`') and concrete resources ('factory functions, package docs, examples, and API reference'), but lists artifacts rather than multiple specific actions, so it stops short of the anchor-3 'multiple specific concrete actions'.	2 / 3
Completeness	It states what the skill does ('for using the generated Ax package, factory functions, package docs, examples, and API reference') and provides an explicit 'Use when...' trigger, satisfying both halves required for anchor 3.	3 / 3
Trigger Term Quality	'Use when writing Go code' is a natural phrase a user might say, but the trigger is dominated by the technical package path; common variations like 'Ax', 'Ax Go SDK', or 'LLM framework' are missing, matching the anchor-2 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The trigger is scoped to a specific named package (`github.com/ax-llm/ax/packages/go`), giving it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 16c2119

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.