CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

84%

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

76%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 dense, efficient reference-style skill body that assumes competence and conveys precise package facts. Its main gaps are the scarcity of executable code examples and the absence of an explicit validate-checkpoint workflow.

Suggestions

Add one or two short, runnable Go snippets for the most common cases (e.g., a ProviderRouter or adaptive balancer setup) to lift actionability toward copy-paste ready.

Provide a brief numbered workflow with an explicit validation checkpoint for at least one fragile path, such as verifying a structured-output mode is supported before transport.

Consider moving the long 'Relevant API Surface' symbol list into a bundled reference file under references/ and pointing to it, to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and fact-dense with no padding or explanation of concepts Claude already knows; every line carries package-specific knowledge (profile names, option keys, capability rungs) that earns its place.

5 / 5

Actionability

It provides precise, concrete guidance — exact API symbols, option keys, and profile names — but offers only one minimal code snippet and describes common cases (routing, caching, Vertex) rather than showing copy-paste runnable examples, leaving minor gaps.

4 / 5

Workflow Clarity

Decision guidance and ordering hints are present ('Start from package examples', 'Start with examples/adaptive_balancer_no_key...then use...'), but there is no explicit multi-step sequenced workflow and validation checkpoints are only implicit.

3 / 5

Progressive Disclosure

Content is well organized into clearly headed sections with an appropriately scoped inline API surface and clear pointers to external package artifacts (examples/, API.md), though there is no in-bundle progressive split to reach a clean 5.

4 / 5

Total

16

/

20

Passed

Description

92%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, specific description that clearly states both purpose and trigger conditions, tied to a distinct package niche. Slightly weaker on trigger-term naturalness because it relies on package-specific jargon rather than common synonyms.

DimensionReasoningScore

Specificity

Names the domain (Go with the Ax package) and enumerates many concrete capabilities — 'named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers' — giving comprehensive coverage of specific actions.

5 / 5

Completeness

It explicitly answers both what (writing Go code with the package for the listed capabilities) and when ('Use when writing Go code with github.com/ax-llm/ax/packages/go'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when writing Go code' is a natural trigger and the listed capability terms (routers, balancers, Responses) are what a user of this package would say, but it leans on package jargon and omits synonyms or file extensions, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

It targets a single specific generated Go package with named concepts (deployment profiles, routers, balancers), carving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.

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