ax-rust-gepa

Use when writing Rust code with `axllm` for GEPA, Pareto tradeoffs, reflection clients, metric budgets, optimizer state, and artifacts.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The content is concise and well-structured with a concrete core pattern, but it lacks an explicit sequenced workflow with validation checkpoints, and the referenced bundle files do not exist to confirm progressive disclosure.

Suggestions

Add an explicit numbered workflow (e.g., 1. seed with BootstrapFewShot, 2. construct AxGEPA, 3. run optimize, 4. inspect Pareto/artifacts) with a validation or inspection checkpoint before relying on results.

Expand the core pattern into a more complete, copy-paste-ready example including imports and how reflection_client/evaluator are constructed, or point to a specific runnable example file.

Include the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) in references/ or assets/ so the signaled references resolve.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized with no padding or explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides a concrete core pattern and named API surface, but the code example is minimal (no imports/types) and the API list lacks signatures, leaving minor gaps from fully copy-paste-ready guidance.	4 / 5
Workflow Clarity	'When To Use' and 'Guardrails' imply rough ordering (BootstrapFewShot before GEPA) but there is no explicit numbered sequence or validation checkpoints for the optimization workflow.	3 / 5
Progressive Disclosure	Well-organized sections with clearly signaled single-level references (API.md, axir-api.json, examples/), but no bundle files are present in the skill, so those references cannot be verified against the actual bundle.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is strong: specific, complete with an explicit 'Use when' trigger, and highly distinct. Its only weakness is trigger-term quality leaning on specialized jargon rather than user-natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'GEPA, Pareto tradeoffs, reflection clients, metric budgets, optimizer state, and artifacts' — giving comprehensive, specific coverage of the domain.	5 / 5
Completeness	Explicitly states both what it does ('writing Rust code with axllm for GEPA...') and when to use it ('Use when...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'Use when writing Rust code with axllm' is a natural trigger with good keyword coverage, but the remaining terms are specialized jargon lacking common synonyms or variations.	4 / 5
Distinctiveness Conflict Risk	A clear niche (axllm + GEPA/Pareto optimization) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ax-llm/ax
Path: website/static/rust/.well-known/agent-skills/ax-rust-gepa/SKILL.md
Commit: 1abea97

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.