CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-go-agent-optimize

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.

Quality

82%

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

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.

A dense, token-efficient skill body that front-loads genuinely non-obvious package facts and optimizer semantics. Its main weaknesses are an illustrative-only code snippet whose `ax.` prefix conflicts with its own `axllm.` API listing, and the absence of an explicit sequenced workflow with validation checkpoints for optimization runs.

Suggestions

Make the Core Pattern snippet match the stated API surface (e.g. `axllm.NewGEPA`/`axllm.AxGEPA` instead of `ax.NewGEPA`) and either make it copy-paste runnable or name the specific file under `examples/` to copy from.

Add a short numbered workflow for a bounded optimization run (define evaluator -> set budget/dataset caps -> run engine -> compare `metadata.bestScore` with `baselineScore` -> persist artifacts) with the verification gate as an explicit checkpoint step.

Clarify where `API.md`, `axir-api.json`, and `examples/` live (package root vs. skill bundle), or link them, so the references are unambiguous.

DimensionReasoningScore

Conciseness

The body is lean bullet-facts ('Language: Go.', 'Real network support: yes.', the Guardrails list) with zero padding and no explanation of concepts Claude already knows; every line carries package-specific or optimizer-semantics knowledge Claude could not infer.

5 / 5

Actionability

The 'Core Pattern' snippet ('engine := ax.NewGEPA(reflectionClient, nil)', 'result := engine.Optimize(request, evaluator)') uses undefined variables and an `ax.` prefix that contradicts the 'Relevant API Surface' listing (`axllm.AxGEPA`, `axllm.Optimize`), so it is closer to illustrative pseudocode than executable code; concrete pointers exist ('Package API docs: `API.md`', 'Runnable examples: `examples/`') but key details are missing.

3 / 5

Workflow Clarity

'When To Use' lists tasks rather than a sequenced run workflow, and there is no ordered procedure with checkpoints for a bounded optimization run; validation concepts are mentioned ('keep only playbook proposals that pass the verification gate', budget/accounting rules like 'metadata.bootstrapMetricCalls plus metadata.totalMetricCalls equals metadata.totalCalls') but the checkpoints are implicit rather than explicit steps.

3 / 5

Progressive Disclosure

At ~44 lines with clean sections (Package Facts, Core Pattern, Relevant API Surface, Guardrails) the single-file organization is good, but referenced artifacts ('API.md', 'axir-api.json', 'examples/') are not clearly signaled as living in the package rather than the skill bundle — no links or paths qualify their location.

4 / 5

Total

15

/

20

Passed

Description

88%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 that names a precise niche (the generated Ax Go package), gives comprehensive concrete capabilities, and pairs an explicit 'Use when' trigger with a clear 'what'. Its only weaknesses are a few missing natural synonyms and a lead trigger phrase ('writing Go code') broad enough to slightly overlap generic Go skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA' — which comprehensively covers the skill's stated use cases; it is not below the 4 anchor because coverage matches the body's 'When To Use' list without gaps.

5 / 5

Completeness

It explicitly answers both questions in one sentence: 'when' via 'Use when writing Go code with `github.com/ax-llm/ax/packages/go`' and 'what' via the concrete capability list, matching the anchor-5 pattern of the good examples.

5 / 5

Trigger Term Quality

Good natural keyword coverage for this niche ('Go', 'agent optimization', 'evaluators', 'judges', 'BootstrapFewShot', 'GEPA'), but a few natural phrasings users might say are missing (e.g. 'Ax', 'few-shot', 'prompt optimization'), so it falls between the 'good coverage' (4) and 'comprehensive synonyms' (5) anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The package path plus 'BootstrapFewShot' and 'GEPA' carve a clear niche with distinct triggers, but the leading phrase 'Use when writing Go code' is broad enough to overlap with a general Go-coding skill, so overlap risk is minor rather than minimal — the 4 anchor ('mostly distinct; minor overlap risk with closely related skills') fits better than 5.

4 / 5

Total

18

/

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-agent-optimize/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.