CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-agent-memory-skills

This skill helps an LLM generate correct AxAgent memory retrieval, context-map, and dynamic skill-loading code using @ax-llm/ax. Use when the user asks about contextMap, AxAgentContextMap, onMemoriesSearch, memoriesCatalog, recall(...), inputs.memories, onLoadedMemories, onUsedMemories, onSkillsSearch, skillsCatalog, AxAgentCatalogSkill, discover({ skills }), onLoadedSkills, onUsedSkills, preloaded skills, preloading memories at forward time, relevanceRanking hints, loaded memory/skill IDs, or carrying memories across forward() calls.

69

Quality

87%

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

78%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.

An excellent rules/reference skill for code generation: executable examples for every feature, explicit defaults and anti-patterns, and no filler concept explanations. Its main weaknesses are monolithic single-file structure with inlined type/API reference material, one padded statistics passage, and rule repetition that could be deduplicated or moved to a reference file.

Suggestions

Split the full options/type reference (the 'Types' listings, AxAgentCatalogSkill/AxAgentContextMap types) and cross-language persistence notes into a references/ file, keeping SKILL.md to defaults, key examples, and rules.

Drop the A/B gate statistics sentence from the relevanceRanking section; keep only the behavioral contract (default ON, opt out with false, non-authoritative hint).

Deduplicate the repeated rules — 'return void', do-not-loop, and child-agent non-inheritance each appear in both 'Use These Defaults' and 'Do Not Generate'; state each once and cross-reference.

DimensionReasoningScore

Conciseness

The body is dense with API-specific contracts ('Catalog content is NOT preloaded into the prompt; entries load only when recalled') and avoids explaining known concepts, but includes trimmable padding — the relevanceRanking A/B statistics sentence ('substance-judged, 49 runs per variant per model: small-model first-lookup precision 24%→90%...') is irrelevant to code generation, and the void-return/no-loop/child-agent rules repeat across 'Use These Defaults', actor usage rules, and 'Do Not Generate'.

4 / 5

Actionability

Every feature ships copy-paste-ready TypeScript: AxAgentContextMap construction with onUpdate persistence, an onMemoriesSearch implementation with alreadyLoaded dedup, catalog arrays, forward-time skill/memory preloading, a carried-memories pattern, and observer wiring, plus the supporting type definitions — fully executable and covering the common cases.

5 / 5

Workflow Clarity

'Use These Defaults' provides a clear decision entry point (static catalog vs. host callback vs. contextMap), each section follows an Enabling → Actor usage → Rules sequence, and 'Do Not Generate' acts as an explicit anti-pattern checklist. It stops short of a 5 because there is no explicit ordered decision flow for combining features in one agent.

4 / 5

Progressive Disclosure

The body is a well-sectioned but monolithic ~440-line single file: the full options/type reference, relevanceRanking details, and cross-language persistence notes are inlined rather than split into reference files. The only external pointers are clearly signaled one-level-deep GitHub example URLs, and no bundle (references/, scripts/, assets/) exists to offload the API reference material.

3 / 5

Total

16

/

20

Passed

Description

91%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: third-person voice, explicit what-and-when, and an unusually thorough trigger list of exact API identifiers and natural phrasings. The only weaknesses are a slightly narrow 'what' clause relative to the full feature surface and the absence of sibling-skill boundary guidance (which lives in the body instead).

DimensionReasoningScore

Specificity

The description states several concrete actions — 'generate correct AxAgent memory retrieval, context-map, and dynamic skill-loading code using @ax-llm/ax' — but the 'what' clause covers three capability areas while tracking/observer features surface only in the trigger list, leaving minor gaps in coverage.

4 / 5

Completeness

It explicitly answers both 'what' ('helps an LLM generate correct AxAgent memory retrieval, context-map, and dynamic skill-loading code') and 'when' ('Use when the user asks about...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when the user asks about' list is comprehensive and includes natural variations and synonyms — exact API identifiers (contextMap, onMemoriesSearch, recall(...), discover({ skills })) alongside phrasings users would actually say ('preloaded skills', 'preloading memories at forward time', 'carrying memories across forward() calls').

5 / 5

Distinctiveness Conflict Risk

AxAgent-specific identifiers (@ax-llm/ax, AxAgentContextMap, memoriesCatalog) create a clear niche, but the description does not delineate boundaries with sibling skills (ordinary agent setup, observability callbacks), so minor overlap risk with those closely related skills remains.

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