CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-agent-context

Use when writing Rust code with `axllm` for deciding between context maps, trajectory context policy, offline optimization (ACE/GEPA), and memory recall for long-context agents.

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%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-structured overview with a concrete core code pattern and clear guardrails. The significant gap is workflow clarity: the skill exists to route between four features but never states the decision criteria that distinguish them, and the code example omits setup for `llm` and `inputs`.

Suggestions

Add explicit selection criteria for the four features, e.g. 'Use contextMap when the corpus persists across runs; use recall when ...; use optimization (ACE/GEPA) when ...', so the central routing decision is unambiguous.

Complete the Core Pattern example by showing how `llm` and `inputs` are constructed (e.g. via a no-key transport setup) so the snippet is copy-paste runnable.

Add a validation checkpoint such as running the corresponding `no-key` example to confirm the chosen feature behaves as expected before wiring real network calls.

DimensionReasoningScore

Conciseness

The body is lean and efficient: terse factual bullets ("Real network support: yes.", "Runtime profiles: `javascript-quickjs`"), one tight code snippet, and no explanations of concepts Claude already knows — every token earns its place.

5 / 5

Actionability

The Core Pattern snippet ("let helper = axllm::agent(\"question:string -> answer:string\")?; let out = helper.forward(&llm, inputs, None)?;") is concrete Rust, but `llm` and `inputs` are undefined, so it is not fully copy-paste ready — a minor gap that fits the 'mostly executable' anchor.

4 / 5

Workflow Clarity

The skill's central task is choosing between contextMap, contextPolicy, optimization, and recall, but no criteria are given for when each applies — "Route long-context agent work to the right generated-package feature" is circular — and there is no validation checkpoint, only conditional guardrails for example selection.

3 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files, organized into five clear sections, and points one level deep to clearly signaled package artifacts ("Package API docs: `API.md` and `axir-api.json`", "Runnable examples: `examples/`"), matching the simple-skill standard for a well-organized overview.

5 / 5

Total

17

/

20

Passed

Description

78%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, niche-specific description with an explicit 'Use when' trigger clause and concrete named capabilities. Its main weakness is that the 'what' is embedded in the 'when' phrasing and keyword coverage lacks synonyms, leaving it just short of the top anchors.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas ("context maps, trajectory context policy, offline optimization (ACE/GEPA), and memory recall") but they all hang off a single verb ("deciding between"), so coverage is specific with minor gaps rather than the multiple distinct action verbs of the top anchor.

4 / 5

Completeness

Both elements are present: an explicit when-clause ("Use when writing Rust code with `axllm`") and a what ("deciding between context maps... and memory recall"), but the what is woven into the when-phrase rather than stated as its own capability sentence with distinct concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural keywords like "Rust code", "axllm", "offline optimization (ACE/GEPA)", "memory recall", and "long-context agents" give good coverage a user of this package would actually say, but there are no synonyms or common variations of these terms, which the top anchor requires.

4 / 5

Distinctiveness Conflict Risk

The combination of "Rust code with `axllm`", "trajectory context policy", and "ACE/GEPA" carves out a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

17

/

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/rust/skills/ax-rust-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.