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

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 ./website/static/rust/.well-known/agent-skills/ax-rust-llm/SKILL.md

Quality

Content

67%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 compact, well-structured quick reference that respects token budget and targets a clear niche, weakened mainly by a partial code snippet and symbol-only API listings that leave the agent to infer call shapes.

Suggestions

Replace the `options` placeholder in the Core Pattern with a minimal concrete value (e.g. `ai("openai", Default::default())?` or a 1-2 line AxOptions struct) so the canonical snippet is copy-paste ready.

Add one short inline usage example for the most common non-AxAI surface (e.g. AxGen/AxFlow/AxAgent) so the agent doesn't have to guess call shapes from symbol names.

Turn the Package Facts file mentions into explicit navigation pointers (e.g. 'Full signatures: see API.md') so references are clearly signaled rather than buried in a fact list.

Dimension	Reasoning	Score
Conciseness	Lean quick-reference that assumes Claude's competence (no explaining what Rust/LLMs are) with a token-dense API symbol list; held just below 5 because the intro and 'Package Facts' restate the frontmatter (name, language, package).	4 / 5
Actionability	Provides one real code snippet ('use axllm::ai; let llm = ai("openai", options)?;') but `options` is an undefined placeholder and the rest of the 'API Surface' is symbol listings without usage, matching the 'some concrete guidance but incomplete' anchor rather than the mostly-executable level of 4.	3 / 5
Workflow Clarity	Single-purpose reference with an unambiguous core pattern and ordering guardrails ('Start from package examples...'); no destructive or batch operation is present, so the missing explicit validation checkpoint does not cap the score, though it keeps it below 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections (When To Use, Package Facts, Core Pattern, API Surface, Guardrails) with one-level references to package artifacts (API.md, axir-api.json, examples/); no bundle files are present, and references are listed as facts rather than signaled navigation links, keeping it just below 5.	4 / 5
	Total	15 / 20 Passed

Description

73%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 concise, well-targeted description with an explicit trigger and a clear niche, slightly held back by generic verbs in place of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('writing Rust code with `axllm`') and several specific items (factory functions, package docs, examples, API reference), but the verbs are generic ('writing', 'using') rather than concrete actions, so it sits at the 'names domain and 1-2 concrete actions' level rather than the comprehensive-action level of 4.	3 / 5
Completeness	Explicit 'Use when...' clause answers 'when', and the list of factory functions/docs/examples/API reference answers 'what'; the 'when' is explicit but could be more scenario-specific, matching the both-present-but-could-be-tighter anchor of 4 rather than the fully-concrete anchor of 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Rust code', 'axllm', 'Ax package', 'API reference') with good coverage; falls short of 5 only because it lacks synonyms or file-extension-style variations.	4 / 5
Distinctiveness Conflict Risk	Tightly anchored to the specific package `axllm` and Rust, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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-llm/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.