CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-gen

Use when writing Rust code with `axllm` for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

38%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 body functions as a monolithic dump of generated-package API behavior rather than a skill overview: exhaustive, accurate, and specific, but verbose, largely prose-based instead of example-based, and with no progressive disclosure into reference files. It needs aggressive splitting into references plus a concise core with runnable examples.

Suggestions

Split the exhaustive provider-behavior sections (OpenAI Decisions, Google Gemini Decisions, Astra Session Work, Provider Forward Options) into one-level-deep reference files such as references/decisions.md, references/astra.md, and references/forward-options.md, keeping SKILL.md as a concise overview with clearly signaled links.

Replace the behavioral prose for the main use cases with complete, runnable Rust examples — multi-sampling with a result picker, streaming_forward with an on_delta handler, and typed tool attachment — instead of describing their semantics in dense paragraphs.

Add an explicit sequenced workflow with validation checkpoints (e.g., start from a no-key example, adapt it to the signature, verify with the scripted transport, then switch to real credentials), and trim edge-case minutiae (timezone abbreviation handling, surrogate-pair joining, JSON key ordering) into the reference files.

DimensionReasoningScore

Conciseness

The body is a ~30KB wall of exhaustive behavioral prose — e.g., multi-hundred-word single paragraphs covering retry budget interactions ("a step's infrastructure retries share one budget, and each one restarts validation with a fresh budget"), timezone abbreviation rules ("`PST` is -08:00 all year; ambiguous ones such as `BST`, `IST` and `CST` are rejected"), and even surrogate-pair splitting across stream events. While it doesn't explain concepts Claude already knows (so not a 1), it is noticeably verbose with many padded reference-grade sections that bury the actionable core.

2 / 5

Actionability

There is some concrete guidance — a two-line core pattern (`axllm::ax("question:string -> answer:string")?` then `program.forward(&llm, inputs, None)?`) and exact identifiers like `streaming_forward(&mut client, values, options, on_delta)` and `with_result_picker` — but almost no complete, executable Rust examples. The skill itself defers syntax to external examples ("Start from package examples for exact native syntax before inventing a new call shape"), so guidance is described in prose rather than given as runnable code, matching 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

"When To Use", "Core Pattern", and "Guardrails" sketch a rough shape (build a program, forward it, consult examples), but the tasks the skill covers (multi-sampling with a picker, tool attachment, streaming, field processors) have no explicitly sequenced steps and no validation checkpoints such as running the no-key scripted examples or cargo checks before touching real providers. A sequence is present but checkpoints are missing or implicit.

3 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, or assets/ directories), and roughly 140 lines of API-reference detail — the entire OpenAI Decisions, Gemini Decisions, Astra Session, and Provider Forward Options sections — are inlined into SKILL.md. Mentions of "API.md and axir-api.json" and "examples/" point at generated-package paths, not clearly signaled one-level-deep skill references, so content that clearly belongs in separate files is inlined.

2 / 5

Total

10

/

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, specific description with an explicit trigger clause and a comprehensive enumeration of the package's feature areas. Its only weaknesses are the missing action-verb statement of what the skill does and the absence of synonymous trigger phrases.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — "forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing" — giving comprehensive coverage of the skill's scope, matching the anchor's 'multiple specific concrete actions; comprehensive coverage'. It is not merely naming a domain with generic actions (score 3/4) because nearly every supported feature area is listed explicitly.

5 / 5

Completeness

The 'when' is explicit ("Use when writing Rust code with `axllm` for AxGen programs...") and the 'what' is conveyed through the enumerated feature list. It does not reach 5 because the description never states what the skill actually does with an explicit action (e.g., 'Generates' or 'Builds'), leaving the 'what' implied by the trigger clause rather than clearly and independently stated.

4 / 5

Trigger Term Quality

Natural terms like "writing Rust code", "streaming", "tools", and "output parsing" are present alongside the package names a user would say ("axllm", "AxGen"), giving good keyword coverage. It falls short of the score-5 anchor because common synonyms and variations (e.g., "structured output", "structured generation", "LLM calls", "sampling") are missing.

4 / 5

Distinctiveness Conflict Risk

"writing Rust code with `axllm` for AxGen programs" carves out a clear niche with distinct triggers (Rust + axllm + AxGen), distinguishable even from sibling TypeScript or other-language variants of the same package, so conflict risk is minimal. It is far from the broad-overlap anchors (1–3), which involve generic domains like 'document files'.

5 / 5

Total

18

/

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