CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-rust-signature

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

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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 lean, executable Rust reference with concrete code in every section and clear single-task guidance. Its weakness is progressive disclosure: external materials are named inline but not provided as a navigable bundle or clearly signaled links.

Suggestions

Provide the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) and link to them as clearly signaled one-level-deep references so navigation is unambiguous.

Introduce the f() builder used in the Native constraints example (it currently appears without context) or note that it is shorthand for the signature builder shown earlier.

Convert inline mentions of API.md and examples/ into markdown links with a short one-line label each (e.g. 'API reference: see API.md') to match the well-signaled reference pattern.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's Rust competence — each section is a tight code example with no padding explaining what a signature or schema is, so every token earns its place.

3 / 3

Actionability

Every pattern ships concrete, executable Rust using real symbols (axllm::s, FieldType::number(), to_json_schema); it is copy-paste ready, matching the anchor for fully executable code with specific examples.

3 / 3

Workflow Clarity

This is a single-task skill with no destructive or batch operations, so the validation-checkpoint cap does not apply; the core action is unambiguous and the guardrails give a clear start-from-examples sequence, which the simple-skill rule allows to score 3.

3 / 3

Progressive Disclosure

Sections are well-organized but references to API.md, axir-api.json, axir-capabilities.json, and examples/ appear as inline mentions rather than clearly signaled one-level-deep links, and no bundle files actually exist alongside the skill to back them.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and explicitly provides both the capability set and a 'Use when' trigger clause. It is tightly scoped to the axllm Rust package with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes' — matching the anchor for several specific concrete actions rather than a single domain mention.

3 / 3

Completeness

Explicitly answers both what (signatures, field descriptors, JSON schema, validation, tool args) and when via the 'Use when writing Rust code with axllm...' trigger clause.

3 / 3

Trigger Term Quality

'Use when writing Rust code with axllm' plus 'string signatures', 'JSON schema', and 'validation' are the natural terms a user of this package would say; coverage is good rather than the partial set that defines a 2.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the generated Rust package axllm with package-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

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