CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-ai

Use when writing Rust code with `axllm` for named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers.

Quality

69%

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-ai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 dense, factually rich reference manual that packs extensive package-specific rules into SKILL.md but suffers from verbosity, near-absence of complete executable code, and inlining of material that belongs in the referenced (but not bundled) API/manifest/example files. Navigation is further weakened by inconsistent example path references.

Suggestions

Move per-model pricing, sampling-parameter rules, and version-specific details (GPT-6.1 Sol rates, Claude Haiku/Sonnet pricing, Gemini 4 Hydrogen budgets, jev-1.14.0) into a reference file such as references/models.md, keeping only model-selection guidance in SKILL.md.

Replace the fragmentary "let llm = ai("openai", options)?;" snippet with complete, runnable starter examples (imports, options construction, error handling) for the core `ai()` factory and at least one decisions provider.

Reconcile example path references ("examples/" in Package Facts vs "src/examples/rust/generation/" elsewhere) and add clearly signaled, one-level-deep links to the API docs and capability manifest instead of inlining the API surface list.

DimensionReasoningScore

Conciseness

The ~200-line body inlines reference-manual detail — per-model pricing ("$2/$0.10/$2.50/$10 through 272K total input"), per-vendor sampling minutiae, version-specific facts ("jev-1.14.0", GPT-5.1–5.6 rules) — that the skill itself says lives in `API.md`, `axir-capabilities.json`, and examples. It does not explain concepts Claude already knows, so it avoids a 1, but there are several padded sections and unsegregated time-sensitive details, matching 'noticeably verbose; several unnecessary... padded sections'.

2 / 5

Actionability

Concrete rules abound (exact defaults, error names like `AxAIServiceTimeoutError`, limits like "16 MiB per decoded image"), and sections repeatedly point to runnable examples, but the only code snippet — "use axllm::ai; let llm = ai("openai", options)?;" — is an incomplete fragment with an undefined `options`, and the API surface list gives names without signatures or usage. This fits 'some concrete guidance but incomplete' rather than 4, and exceeds 2 because the guidance is far above high-level hints.

3 / 5

Workflow Clarity

There is no numbered, sequenced workflow for any task; instead, well-headed topical sections provide use-condition decision rules ("Use `ProviderRouter` for...", "Opt into `AxBalancerAdaptiveStrategy` only for...") plus a Guardrails section directing where to start. This gives partial guidance with implicit rather than explicit checkpoints and sequences, matching anchor 3; it is not 2 because the decision boundaries are specific and consistently stated.

3 / 5

Progressive Disclosure

The body has clear section headers and mentions bundle artifacts (`API.md`, `axir-api.json`, `examples/`), but none of those files are present in the bundle, ~200 lines of API-reference-like content (per-model rules, pricing, an API-surface list) are inlined in SKILL.md, and example paths are inconsistent ("examples/" vs "src/examples/rust/generation/"). This matches 'some structure... content that should be separate is inline'.

3 / 5

Total

11

/

20

Passed

Description

83%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 strong, trigger-explicit description that names the language, package, and a broad set of concrete capability areas in third-person voice. Its main limitations are capability-noun phrasing rather than action verbs and coverage gaps for parts of the skill body (typesafe/Jev, decisions providers, session work).

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — "named deployment profiles, generic provider clients, model selection, OpenAI-compatible calls, Responses, Gemini, Anthropic, routers, and balancers" — but presents them as noun phrases rather than actions and omits several major areas the skill covers (typesafe/Jev, decisions providers, sessions, caching, retries), matching the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

It explicitly answers both questions in one sentence: the "what" ("writing Rust code with `axllm` for" the enumerated capabilities) and a clear, explicit "when" ("Use when writing Rust code with `axllm` for...") with concrete trigger phrases, matching the top anchor. Not below 5 because the 'when' is highly specific rather than generic, and not applicable below since both elements are explicit.

5 / 5

Trigger Term Quality

Natural trigger terms are present — "Rust", "axllm", "OpenAI-compatible", "Gemini", "Anthropic", "routers", "balancers" — which users of this package would plausibly say. A few common synonyms are missing (e.g., "Claude" alongside Anthropic, "failover"/"load balancing" alongside balancers), so it sits between anchors 4 and 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

The Rust + `axllm` + provider-name scoping carves a clear niche with minimal conflict risk against unrelated skills. Minor overlap remains with closely related skills (e.g., the TypeScript/other-language axllm siblings and the referenced Typesafe/Jev skill), fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

17

/

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-ai/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.