CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-go-agent-context

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for deciding between context maps, trajectory context policy, offline optimization (ACE/GEPA), and memory recall for long-context agents.

Quality

70%

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-agent-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 concise, well-sectioned body that avoids over-explanation and includes a runnable core pattern, but it under-delivers on its stated purpose: the decision criteria for choosing among the four context features are absent, and all referenced documentation files are missing from the bundle. It reads more like a package fact sheet than an actionable routing guide.

Suggestions

Add explicit decision criteria for the core routing task, e.g. a table or rules for when to use contextMap vs contextPolicy vs optimization vs recall.

Include one short runnable example per feature (contextMap, contextPolicy, Optimize, recall) so guidance is copy-paste executable rather than name-only API listings.

Ship the referenced files (API.md, axir-capabilities.json, examples/) in the bundle's references/ directory, or inline the minimal API details needed and drop the dangling references.

DimensionReasoningScore

Conciseness

The body is lean and fact-dense — terse bullet lists ('Real network support: yes', 'Scripted no-key transport support: yes'), a minimal code snippet, and no explanation of concepts Claude already knows. Only minor tokens could be trimmed (e.g. 'Language: Go.' is redundant with the description), so it sits between efficient (4) and every-token-earns-its-place (5).

4 / 5

Actionability

There is one executable-looking snippet ('helper := ax.NewAgent("question:string -> answer:string", nil)') and a concrete API surface list, but the skill's core purpose — deciding between contextMap, contextPolicy, optimization, and recall — has no decision guidance, no per-feature example, and no code showing how to invoke any of the four features. Concrete guidance is present but incomplete.

3 / 5

Workflow Clarity

'When To Use' bullets ('Choose between contextMap, contextPolicy, optimization, and recall', 'Avoid mixing persistent corpus orientation with within-run compaction') and the Guardrails give rough direction, but the routing logic is implicit: no criteria for when each feature applies and no checkpoints. Steps are listed but the decision sequence is underspecified, matching the anchor for present-but-gapped sequencing.

3 / 5

Progressive Disclosure

Sections are well organized, but the body's references ('API.md', 'axir-api.json', 'axir-capabilities.json', 'examples/') do not exist in the skill bundle — no references/, scripts/, or assets/ directories are present — so navigation to the detailed material is unverifiable. The inlined 'Relevant API Surface' list is content that could live in a proper reference file, leaving organization better than minimal but clearly improvable.

3 / 5

Total

13

/

20

Passed

Description

71%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 well-scoped, package-specific description with an explicit 'Use when' trigger and a clear enumeration of the four decision areas. Its main weaknesses are jargon-heavy trigger terms lacking natural user phrasings and a 'what' that stops at 'deciding between' rather than stating concrete capabilities.

Suggestions

Add natural trigger phrasings users would actually say, e.g. 'when the user mentions context maps, GEPA/ACE prompt optimization, or agent memory' rather than only package-internal terminology.

State the concrete capability alongside the routing role, e.g. 'Selects and wires up contextMap, contextPolicy, optimization, or recall features' so the 'what' goes beyond 'deciding between'.

DimensionReasoningScore

Specificity

The description names the domain (Go code with `github.com/ax-llm/ax/packages/go`) and lists four concrete decision areas: 'context maps, trajectory context policy, offline optimization (ACE/GEPA), and memory recall for long-context agents'. It falls short of 5 because the only action stated is 'deciding between' these features — no concrete tasks or outputs are enumerated, leaving coverage gaps.

4 / 5

Completeness

Both parts are present: the 'what' is routing among context maps, context policy, optimization, and recall, and an explicit 'Use when writing Go code with...' clause gives the 'when'. Not 5 because the trigger clause names the package rather than concrete user-intent phrases, so the 'when' could be more explicit and specific.

4 / 5

Trigger Term Quality

Keywords like 'Go code', 'context maps', 'offline optimization (ACE/GEPA)', 'memory recall', and 'long-context agents' are relevant to the niche, but the phrasing is technical-jargon-heavy and lacks natural variations or synonyms a user might say (e.g. 'prompt optimization', 'context engineering', 'agent memory'). Not 4 because common natural phrasings are missing alongside the jargon.

3 / 5

Distinctiveness Conflict Risk

The description is pinned to a single named package (`github.com/ax-llm/ax/packages/go`) with niche-specific features (ACE/GEPA, trajectory context policy), giving it a clear niche with distinct triggers and minimal conflict risk against generic Go or memory skills.

5 / 5

Total

16

/

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