Name: ax-go-llm
Rating: 58.4 (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

68%

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

68%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 an efficient, well-structured quick reference with executable starter code and concrete file/symbol pointers. Its main weaknesses are the absence of an explicit multi-step workflow with validation checkpoints and a heavy inlined API-surface list that would be better split into a referenced file.

Suggestions

Move the long 'Relevant API Surface' symbol list into a referenced file (e.g. references/api-surface.md) and keep only the highest-value symbols inline, improving both conciseness and progressive disclosure.

Add a short ordered workflow for the common path (e.g. 1. pick entrypoint from examples/ 2. use no-key examples for local checks 3. switch to provider-api examples when credentials exist 4. verify against API.md), with an explicit validation/check step.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly reference-style (facts, a single code block, a symbol list, guardrails) with no padding over concepts Claude already knows; the main trims would be the introductory sentence that restates the description and the long inlined API-surface line, which is useful but dense.	4 / 5
Actionability	A copy-paste-ready Core Pattern snippet plus concrete file references ("API.md", "axir-api.json", "examples/") and named symbols make the guidance executable, but only the basic AI-creation case is shown with code while signatures, agents, flows, and optimizers are listed as bare symbol names without usage examples.	4 / 5
Workflow Clarity	The 'When To Use' bullets and Guardrails give scenario- and ordering-style hints ('Start from package examples for exact native syntax before inventing a new call shape'), but there is no explicit multi-step sequence or validation checkpoint, so sequence is present yet checkpoints are only implicit.	3 / 5
Progressive Disclosure	Sections are well organized (When To Use, Package Facts, Core Pattern, Relevant API Surface, Guardrails) and external reference targets are named, but the large inlined API-surface symbol list is content that could live in a separate reference file, leaving a minor organization gap; no bundle files are present to provide one-level-deep references.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is specific and clearly scoped to the generated Go Ax package, with an explicit 'Use when' trigger and concrete package references. It is slightly held back by relying on a technical import path as its main trigger and by some overlap risk with sibling Ax-language skills.

Suggestions

Add natural-language trigger synonyms (e.g. 'Ax Go SDK', 'Ax generators in Go') so users who don't recall the exact import path still match the skill.

Expand the 'when' clause with concrete scenarios (e.g. 'Use when starting a Go program with Ax, picking providers/generators/agents, or balancing providers') to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	The description names the domain ("writing Go code with `github.com/ax-llm/ax/packages/go`") and lists several concrete scoping elements ("factory functions, package docs, examples, and API reference"), though these read more as resources than explicit actions, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	Both halves are present: a 'what' (using the generated Ax package and its factory functions, docs, examples, API reference) and an explicit 'when' ("Use when writing Go code with..."), but the 'when' is a single condition that could be more specific about the situations that call for it.	4 / 5
Trigger Term Quality	It includes relevant terms ("writing Go code", the package import path) but leans on a technical import path as the primary trigger and lacks common natural variations or synonyms a user might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The package path pins it to a clear niche with minimal broad conflict risk, but there is minor overlap risk with closely related Ax skills for other languages, which the body itself alludes to ("language-specific AI skill", "repo-maintainer skills").	4 / 5
	Total	15 / 20 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: dec4f9e

Reviewed: 4 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.