CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-agent-optimize

Use when writing Rust code with `axllm` for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.

Quality

79%

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/rust/skills/ax-rust-agent-optimize/SKILL.md
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 tight, well-structured reference skill: excellent token efficiency, concrete API-level guidance, and correct delegation of detail to package docs. Its main weakness is the absence of an explicitly sequenced optimization workflow with validation checkpoints, and the core code snippet depends on undefined variables.

Suggestions

Add a short ordered workflow under When To Use — e.g., 1. copy the closest `examples/` variant, 2. define the evaluator closure, 3. run optimize with explicit budget/dataset caps, 4. verify metadata.bestScore vs baselineScore before persisting artifacts — so the sequence and checkpoints are explicit rather than implicit in guardrails.

Make the Core Pattern snippet self-contained or annotate where `reflection_client`, `request`, and `evaluator` originate (which example or API constructor), moving it from mostly-executable to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean throughout — telegraphic facts ("Language: Rust.", "Package: `axllm`."), a 4-line code pattern, and dense directive guardrails with zero padding or explanation of concepts Claude already knows (no explaining what GEPA or reflection is). It assumes competence and every bullet carries non-obvious information, matching anchor 5; anchor 4's 'minor instances of over-explanation' doesn't apply.

5 / 5

Actionability

Concrete guidance dominates: a Rust core pattern, an exact call signature (`optimize_with_client(&mut program, student.clone(), examples, options)` with `Rc<RefCell<Client>>`), and directives to start from package examples. It stops short of anchor 5 because the Core Pattern references undefined placeholders (`reflection_client`, `request`, `evaluator`) with no indication of where they come from, so the code is not copy-paste ready.

4 / 5

Workflow Clarity

There is no ordered sequence for the optimization workflow — steps are only implicit in the guardrails (start from examples → define evaluator → run bounded optimize → compare metadata.bestScore with baselineScore). Validation-ish guidance exists (verification gate, budget caps, score-comparison rules) but checkpoints are implicit rather than structured, matching anchor 3; anchor 4 requires a clear explicit sequence.

3 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files, and per the rubric's simple-skill guidance a compact, well-sectioned file warrants a 5. Sections are well-organized (When To Use, Package Facts, Core Pattern, API Surface, Guardrails) and detailed material is correctly delegated one level deep to package artifacts (`API.md`, `axir-api.json`, `examples/`) rather than inlined.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific, distinctive description with an explicit 'Use when' trigger and strong domain keywords, but it never states what the skill actually does — the capability side is a list of topic nouns rather than an explicit 'what' statement. Adding a leading capability phrase and a few more natural synonyms would round it out.

Suggestions

Precede the 'Use when' clause with an explicit capability statement, e.g., "Provides API patterns and guardrails for writing Rust agent-optimization code with `axllm`. Use when...", so the 'what' is stated rather than implied.

Convert the topic-noun list into verb phrases (e.g., "optimize AxAgents, build evaluator callbacks, evolve verified agent playbooks, persist optimizer artifacts") to strengthen the concrete-action framing.

Add natural trigger variations the body already uses, such as "AxAgent", "prompt optimization", and "few-shot", to widen keyword coverage toward anchor 5.

DimensionReasoningScore

Specificity

The description enumerates several concrete capability areas — "agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA" — all specific, none vague, though they are topic nouns rather than verb-stated actions (the only action is "writing Rust code with `axllm`"). This sits between anchor 3 (1-2 concrete actions) and anchor 5 (comprehensive action coverage), matching anchor 4's 'several specific items with minor gaps' while falling short of anchor 5's fully action-phrased, comprehensive coverage.

4 / 5

Completeness

The 'when' is explicit ("Use when writing Rust code with `axllm` for agent optimization...") but the 'what' is only implied — the description never states what the skill does (e.g., "provides API guidance and code patterns for..."). This is the inverse of anchor 3's profile ('what' clear, 'when' weak), while anchor 4 requires both to be present with the 'what' explicitly stated.

3 / 5

Trigger Term Quality

It includes multiple natural domain terms a user would plausibly say — "agent optimization", "evaluators", "judges", "BootstrapFewShot", "GEPA", "Rust" — giving good keyword coverage. It falls short of anchor 5 because common variations like "AxAgent", "prompt optimization", "few-shot", or "optimizer" (all terms the body itself uses) are missing.

4 / 5

Distinctiveness Conflict Risk

"Rust code with `axllm`" scoped to "agent optimization... BootstrapFewShot, and GEPA" carves out a clear niche with distinct trigger terms; a user mentioning GEPA or BootstrapFewShot in an axllm Rust context unambiguously means this skill. Anchor 4's 'minor overlap risk with closely related skills' doesn't apply because the optimizer-specific triggers separate it from general Rust or axllm-usage 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/rust/skills/ax-rust-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.