CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-go-ai

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers.

Quality

72%

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-ai/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 an information-dense reference with accurate, specific rules and useful guardrails, but it functions as a monolithic dump: version-sensitive pricing and per-provider detail are inlined, only one code snippet is executable, and multi-step guidance lacks explicit sequencing or checkpoints. Restructuring into a lean overview plus per-topic reference files would substantially improve it.

Suggestions

Split the per-provider deep-dives (Typesafe/Jev, OpenAI Decisions, Gemini Decisions, Astra Session Work) into separate reference files under references/ and link to them from a concise SKILL.md overview.

Move version-sensitive pricing and per-model details (token rates, thinking-budget mappings, model-specific rules) into a dedicated reference or 'current model catalog' file so the main body stays lean.

Inline short, runnable code examples for the most common cases (client creation, structured output, router/balancer setup) instead of only naming example directories outside the bundle.

DimensionReasoningScore

Conciseness

The body is dense and fact-heavy rather than padded with concepts Claude already knows, but it buries operational guidance in long prose paragraphs and inlines large amounts of version- and time-sensitive minutiae (e.g., "$2/$0.10/$2.50/$10 through 272K total input", "jev-1.14.0", "gemini-4-hydrogen" budget mappings) that are not placed in a deprecated/old-patterns section. It is mostly efficient but includes detail that should be trimmed or moved, matching the 3 anchor rather than 4.

3 / 5

Actionability

Only one small executable snippet exists (the `ax.NewAI` core pattern); the rest names exact APIs, options, and limits ("Use `axllm.OpenAIDecisions` for explicit provider request shapes", "retry: { maxRetries: 0 } sends each request once") but points to example directories (`src/examples/go/generation/`, `examples/`) rather than inlining runnable code for common cases. Guidance is concrete in naming yet incomplete in executable coverage — descriptive rules instead of copy-paste-ready examples — fitting the 3 anchor better than 4.

3 / 5

Workflow Clarity

The "When To Use" bullets and topic sections give a recognizable structure, and the Guardrails section supplies do/don't guidance, but no multi-step process is presented as a sequence with validation checkpoints (e.g., choosing a profile → configuring credentials → verifying routing is scattered across sections). There are no risky destructive/batch operations that would impose a cap, but sequence and checkpoints are implicit, matching the 3 anchor.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, assets/), yet the body is a ~200-line monolith that inlines per-provider deep-dives (Typesafe/Jev, OpenAI Decisions, Gemini Decisions, Astra sessions, caching, pricing) — content that clearly belongs in separate reference files — while pointing to paths like `API.md`, `axir-capabilities.json`, and `examples/` that are not part of the skill bundle. Section headers provide some structure, placing it at 3 rather than 2, but organization into one-level-deep referenced files is absent.

3 / 5

Total

12

/

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: explicit "Use when" trigger guidance, a pinned package path for distinctiveness, and a concrete list of capability areas with natural provider-name keywords. The main improvement would be framing the capability list as actions and adding a few more natural synonyms.

DimensionReasoningScore

Specificity

The description names the domain ("writing Go code with `github.com/ax-llm/ax/packages/go`") and lists several concrete capability areas — "named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers" — giving specific, non-generic coverage. It falls short of a 5 because the items are capability nouns rather than explicit actions (e.g., "create provider clients", "route requests"), leaving minor gaps in what the skill actually does.

4 / 5

Completeness

It explicitly answers "when" with a leading "Use when writing Go code with `github.com/ax-llm/ax/packages/go`" and answers "what" through the concrete capability list that follows (profiles, provider clients, model selection, calls, routers, balancers). Both what and when are present with concrete trigger phrases, matching the 5 anchor; a 4 would require the 'when' to be less explicit or the 'what' to be vaguer.

5 / 5

Trigger Term Quality

It includes natural terms users would say when needing this skill: "Go code", "OpenAI", "Gemini", "Anthropic", "Responses", "routers", and "balancers". Coverage is good but a few natural variations are missing (e.g., "LLM", "chat completions", "failover", "failover/balancing" synonyms), so it sits between the 3 and 5 anchors, noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

Pinning the trigger to one specific Go import path (`github.com/ax-llm/ax/packages/go`) gives it a clear niche, but the provider names (OpenAI, Gemini, Anthropic) overlap with generic LLM-API skills, creating minor conflict risk with closely related skills. It is mostly distinct rather than fully minimal-risk, so 4 fits better than 5 or 3.

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

packages/go/skills/ax-go-ai/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.