CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-rust-signature

Use when writing Rust code with `axllm` for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.

Quality

73%

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

A dense, information-rich reference that is strong on package-specific facts and concrete limits but reads as a catalog rather than a guided skill. The dominant issues are cross-section redundancy among the provider sections and the inlining of provider deep-dives that belong in separate reference files.

Suggestions

Deduplicate rules repeated across provider sections (trueThreshold default 0.5, the 0.01 probability-sum tolerance, 'numeric bounds never define a Score rubric', the src/examples/rust/generation/ path) into one shared section each section links back to.

Move the Typesafe/Jev, OpenAI Decisions, and Gemini Decisions deep-dives into separate reference files (e.g. references/typesafe.md, references/openai-decisions.md) and keep a one-line summary plus a clearly signaled pointer per provider in SKILL.md.

Consolidate the scattered, repeated example pointers into a single 'Examples' section, and either complete the Rust snippets (imports, fn main) or explicitly label them as fragments to be adapted from examples/.

DimensionReasoningScore

Conciseness

Mostly package-specific facts that Claude would not know, but with noticeable tightening opportunities: "trueThreshold ... default 0.5" appears in three sections, the "inclusive 0.01 tolerance" probability rule and "Numeric bounds never define a Score rubric" each appear twice, and "Runnable ... examples are under src/examples/rust/generation/" is repeated four times. Not 2 because nothing explains generic concepts Claude already knows; not 4 because the cross-section redundancy exceeds minor over-explanation.

3 / 5

Actionability

Concrete Rust snippets for the core patterns (`s("question:string -> answer:string")`, `axllm::ax(...)`, `FieldType` builders with `minimum`/`pattern`, `to_json_schema`, `program.signature = signature`) plus highly specific limits (16 MiB per decoded image, 256-1568 pixels, `[A-Za-z0-9_-]{1,64}`). Not 5 because the snippets are fragments (no imports, no `fn main`, `f`/`FieldType` unresolved) rather than copy-paste ready, though the skill explicitly directs to `examples/` for complete programs.

4 / 5

Workflow Clarity

An implicit progression exists (string form -> native constraints -> JSON schema -> attach signature -> `forward`, anchored by "Start from the complete programs under `examples/`"), but there is no explicit validation checkpoint or error-recovery loop anywhere. Not 4 because checkpoints are entirely implicit rather than present with minor gaps; not 2 because a discernible sequence and guardrails section do structure the work.

3 / 5

Progressive Disclosure

Section headers are clear and the body points to `examples/`, `API.md`, and external doc URLs, but the deep-dive provider material (Typesafe/Jev ~20 lines, OpenAI Decisions, Gemini Decisions) is inlined in SKILL.md where a brief summary plus a one-level-deep reference would fit better, and the examples/ pointers are scattered and repeated rather than consolidated. No bundle directories (references/, scripts/, assets/) exist, so the cited API.md and axir-api.json paths cannot be verified.

3 / 5

Total

13

/

20

Passed

Description

78%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 description that explicitly combines a clear trigger condition with a concrete list of capabilities tied to a named package. Its main weakness is that the capability list understates the skill's actual scope, which centers heavily on decision-evidence, typed providers, and provider-specific decision APIs that the description never mentions.

DimensionReasoningScore

Specificity

Names five concrete capability areas ("string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes") tied to a specific package. Not 5 because the body's substantial decision-evidence and provider-specific topics (Typesafe/Jev, OpenAI Decisions, Gemini Decisions) are not hinted at; not 3 because it lists several specific actions rather than just 1-2.

4 / 5

Completeness

Explicitly answers when ("Use when writing Rust code with `axllm`") and what (the "for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes" list). Not 5 because the 'what' is a prepositional list inside the when-clause rather than explicit action verbs, and the when is a single condition without additional trigger phrases.

4 / 5

Trigger Term Quality

Includes natural trigger terms users of this package would say: "Rust", "axllm", "signatures", "JSON schema", "validation", "tool argument shapes". Not 5 because common variations like "Ax", "signature builder", or "typed outputs" are missing; clearly above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Names a specific generated package (`axllm`) and language (Rust), creating a clear niche with distinct triggers and minimal conflict risk with other skills. No overlap concerns; a user mentioning axllm or Rust signature work would unambiguously land here.

5 / 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-signature/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.