CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-typesafe

Use when writing Rust code with `axllm` for Typesafe Jev image inputs, boolean/class/rubric score/box signatures, decision evidence and provenance, native Noul/Choice/Score/Box, structured criteria and hybrid generation.

Quality

70%

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

Quality

Content

57%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 is a dense, information-rich API fact sheet that assumes reader competence and wastes few tokens, but it functions as an inlined reference manual: only one fragmentary code example, no ordered workflows with validation, and no progressive disclosure into bundle files. Shifting constraint/reference detail into separate files and adding executable Rust examples would substantially improve it.

Suggestions

Provide 2–3 complete, runnable Rust examples (with imports and setup) for the most common tasks — a typed decision, an evidence-bearing score, and an image localization request — instead of one fragmentary snippet.

Move the 'Relevant API Surface' symbol list and transport/validation constraint detail (byte limits, probability tolerances, key regexes) into a references/ file, keeping SKILL.md as an overview with one-level-deep pointers.

Add ordered step sequences with validation checkpoints for multi-step flows such as image localization (validate image constraints → attach asset → verify reference appears in a string value → check presence boolean before consuming the box).

DimensionReasoningScore

Conciseness

No padding and no explanation of concepts Claude already knows — the body is an extremely dense fact sheet. Minor trimmable material remains, such as version pins ('Use jev-1.14.0 or jev-preview') and edge-case tolerances ('Totals of 0.99 and 1.01 are accepted') that read as API-reference detail.

4 / 5

Actionability

The single 'Core Pattern' snippet is fragmentary (undefined api_key/ticket) and much of the rest is prose directives or pseudocode like 'request.with_assets(...)'; real API names and signature DSL strings are concrete, but imports, setup, and executable examples for the common cases (native questions, image assets, Gemini decisions) are missing.

3 / 5

Workflow Clarity

An implicit sequence exists in the Core Pattern (ai() → ax()?.forward()) and a mini-sequence for reranking ('evaluate pairs... retain candidate IDs... sort by relevance.value'), but advanced flows like image localization and native question construction are unsequenced constraint dumps with no validation checkpoints or error-recovery loops.

3 / 5

Progressive Disclosure

Section headers exist and external pointers are given (API.md, examples/, doc URLs), but there are no bundle files at all and the bulk — the long 'Relevant API Surface' symbol list and pages of transport/validation constraints — is inlined in the single SKILL.md rather than split into reference files.

3 / 5

Total

13

/

20

Passed

Description

71%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 highly specific, well-triggered description for a narrow niche, with an explicit 'Use when' clause and distinct trigger terms. Its main weakness is jargon density: capability nouns like 'Noul' and 'Typesafe Jev' replace natural user phrasing, and the 'what' is a noun list rather than stated actions.

Suggestions

Add one or two plain-language trigger phrases or synonyms (e.g., 'typed decisions', 'image localization') alongside the package-internal jargon so users can match the skill with natural wording.

Convert part of the noun list into action verbs (e.g., 'Write typed decision signatures... retain evidence and provenance...') to state what the skill actually does.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "boolean/class/rubric score/box signatures", "decision evidence and provenance", "native Noul/Choice/Score/Box", "structured criteria and hybrid generation" — but they are jargon-heavy nouns rather than the action verbs of the 5 anchor, and coverage reads as a keyword dump.

4 / 5

Completeness

The explicit "Use when writing Rust code with axllm..." trigger answers 'when' concretely and the capability list answers 'what', but the 'what' is a verb-less noun list rather than the clearly articulated actions of the 5 anchor.

4 / 5

Trigger Term Quality

"Rust code with axllm" and "image inputs" are natural phrases for package users, but "Typesafe Jev", "native Noul/Choice/Score/Box" are internal jargon and no synonyms or common variations are offered, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The combination of `axllm`, Rust, and Typesafe Jev is a clear niche with distinct triggers and minimal overlap risk with generic Rust or LLM skills.

5 / 5

Total

16

/

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