CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-go-agent-memory-skills

Use when writing Go code with `github.com/ax-llm/ax/packages/go` for agent memory, recall callbacks, dynamic skill discovery, loaded-skill state, and used-skill tracking.

68

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

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-organized API reference skill that is concise and actionable, with executable code and exact symbol/file pointers. It loses points on workflow clarity and progressive disclosure because it is a flat monolithic reference with no validation steps and no real bundle-file separation.

Suggestions

Add a short validation/checkpoint step to the lifecycle guidance (e.g., how to confirm a forward-time skill overrode a constructor skill) to close the workflow feedback loop.

Move the inline 'Lifecycle And State' and 'Relevant API Surface' detail into reference bundle files and link to them one level deep from a tighter SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — terse 'Package Facts' and 'Lifecycle And State' bullets add only what Claude would not already know, with no padding or basic-concept explanation.

3 / 3

Actionability

It provides an executable Go 'Core Pattern' snippet, exact example file paths under 'Runnable Examples', and concrete API symbols under 'Relevant API Surface', making guidance copy-paste ready.

3 / 3

Workflow Clarity

'When To Use' lists use cases and 'Guardrails' give ordering hints, but this is reference material with no explicit validation checkpoints or feedback loops for the multi-faceted operations it covers.

2 / 3

Progressive Disclosure

Sections are well organized, but 'Package Facts', 'Lifecycle And State', and 'Relevant API Surface' are inline reference content that could live in separate bundle files, and the referenced API.md/examples are not part of any actual bundle.

2 / 3

Total

10

/

12

Passed

Description

85%

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 specific, well-scoped description with an explicit trigger clause and concrete capabilities, distinguishing it clearly from other skills. Its only weakness is reliance on technical jargon over natural user phrasing for some trigger terms.

Suggestions

Soften jargon like 'recall callbacks' and 'loaded-skill state' toward phrases a user would actually say (e.g., 'remembering context between turns', 'tracking which skills were used').

Add common natural variants such as 'Go agent', 'memory for agents', or 'skill catalog' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'agent memory, recall callbacks, dynamic skill discovery, loaded-skill state, and used-skill tracking' — rather than vague abstractions.

3 / 3

Completeness

It explicitly answers both what (the listed memory/skill capabilities) and when (an explicit 'Use when writing Go code with ...' clause), so it is not capped at 2.

3 / 3

Trigger Term Quality

'Use when writing Go code' is a natural trigger, but 'recall callbacks', 'loaded-skill state', and 'used-skill tracking' are technical jargon a user would rarely utter, missing common variations.

2 / 3

Distinctiveness Conflict Risk

The specific package path 'github.com/ax-llm/ax/packages/go' plus narrow capability scope gives it a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

11

/

12

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.