ax-rust-llm

Use when writing Rust code with `axllm` for using the generated Ax package, factory functions, package docs, examples, and API reference.

Quality

64%

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-llm/SKILL.md

Quality

Content

72%

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

The body is a lean, well-organized reference card that appropriately offloads detail to bundled reference files, but its lone code example is a fragment rather than a complete runnable sample and it lacks an explicit workflow with validation checkpoints.

Suggestions

Expand the 'Core Pattern' into one complete, copy-paste-runnable example (with imports and a defined `options`) so guidance is fully executable.

Add a short ordered workflow (pick an example -> adapt signatures -> run no-key check -> switch to provider-api) with an explicit validation step.

Show a one-line no-key transport snippet since it is flagged as supported, to make local verification concrete.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse bullet lists, a tiny code snippet, and a dense symbol listing, with no padding or explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides a concrete 'Core Pattern' snippet and exact symbol names, but the code is a fragment (`options` undefined, not copy-paste runnable) and the real guidance defers to `examples/` rather than giving a complete executable example.	2 / 3
Workflow Clarity	As a simple reference skill its single action is fairly unambiguous, but the sequencing is scattered across 'When To Use' and 'Guardrails' with no explicit validation/feedback checkpoint.	2 / 3
Progressive Disclosure	At ~46 lines it is well-organized into clearly labeled sections and points one level deep to real reference paths (API.md, axir-api.json, axir-capabilities.json, examples/), matching the simple-skill allowance for a 3.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 specific to a clear niche and includes an explicit 'Use when' trigger, but it lists resources more than concrete actions and its 'when' guidance overlaps with its 'what' rather than providing rich, distinct triggers.

Suggestions

Reword around concrete actions (e.g. 'Generate and call Ax provider/agent/flow code in Rust using `axllm`') instead of listing resources.

Add distinct trigger terms users would actually say, such as 'Rust LLM', 'Ax package', 'provider balancing', or 'AxGen/AxFlow agents'.

Make the 'when' clause enumerate the situations that call for this skill rather than restating the 'what'.

Dimension	Reasoning	Score
Specificity	Names the concrete domain (Rust, `axllm`) and lists specific resources ('factory functions, package docs, examples, and API reference'), but enumerates resources rather than multiple concrete actions, so it is not comprehensive.	2 / 3
Completeness	It has an explicit 'Use when...' clause and states what the skill does, but the 'when' trigger largely restates the 'what' rather than offering distinct explicit triggers, so it is not a clear full what-and-when pair.	2 / 3
Trigger Term Quality	Leads with the natural phrase 'Use when writing Rust code with `axllm`' and includes real terms, but mixes in jargon ('generated Ax package', 'factory functions') and misses common variations.	2 / 3
Distinctiveness Conflict Risk	Tied to the specific Rust package `axllm`, giving it a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	9 / 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-llm/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.