ax-rust-gen

Use when writing Rust code with `axllm` for AxGen programs, forward calls, streaming, tools, assertions, traces, usage, and output parsing.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/rust/skills/ax-rust-gen/SKILL.md

Quality

Content

65%

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

The skill is a concise, well-structured reference card with a clear niche and good token efficiency, but its single code example is incomplete, the multi-capability workflows lack sequenced validation steps, and every referenced detail file is missing from the bundle.

Suggestions

Ship the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) or remove the dangling references so progressive-disclosure navigation actually resolves.

Expand the Core Pattern into a minimal complete, copy-paste-ready example that includes imports and how the `llm` client is constructed.

Add a short sequenced workflow with a validation checkpoint for attaching typed tools / MCP tools to a generation call, rather than only listing the API symbols.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: terse Package Facts, a minimal Core Pattern snippet, a symbol-level API surface list, and short Guardrails, with no over-explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	The Core Pattern gives real Rust ("let program = axllm::ax(...)?; let out = program.forward(&llm, inputs, None)?;") but it is incomplete — missing imports and how `llm` is constructed — and the API surface is only a symbol list, fitting 'some concrete guidance but incomplete; missing key details'.	2 / 3
Workflow Clarity	The Core Pattern is a clear two-step sequence (build program, forward), but there are no validation/checkpoint steps and the multi-capability flows (tools, MCP, streaming) are only listed as API surface without a sequenced workflow, matching 'steps listed but checkpoints missing'.	2 / 3
Progressive Disclosure	The body is well-organized into clearly signaled sections and points one level deep to API.md, axir-api.json, axir-capabilities.json, and examples/, but none of those referenced files are present in the (empty) bundle, so the disclosure path leads to dead ends.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 has an explicit 'Use when' trigger and a distinctive, well-scoped niche, but its capability list leans on jargon and feature nouns rather than crisp concrete actions, slightly weakening specificity and trigger-term naturalness.

Suggestions

Rewrite the capability list as concrete verb phrases (e.g., 'forward generation calls, attach typed tools, stream responses, parse structured outputs') instead of feature nouns like 'streaming, tools, usage, traces'.

Add a few natural-language trigger variations a user might actually say (e.g., 'Rust LLM client', 'typed tool calls') alongside the package jargon.

Dimension	Reasoning	Score
Specificity	Lists seven capability areas ("forward calls, streaming, tools, assertions, traces, usage, and output parsing"), but several are feature nouns/buzzwords rather than concrete verb-actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Opens with an explicit "Use when writing Rust code with `axllm` for AxGen programs..." trigger (the when) and enumerates what the skill covers, clearly answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	"writing Rust code" and "axllm" are natural terms a user in this ecosystem would say, but the trailing capability list is jargon-heavy and lacks common variations, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Tightly scoped to Rust with the named `axllm`/AxGen package, giving it a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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: packages/rust/skills/ax-rust-gen/SKILL.md
Commit: fe8baf8

Reviewed: 5 days 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.