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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%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 tight, code-first reference with good structure and clear pointers to bundle files. It loses a little on actionability and workflow clarity because one example is not fully self-contained and there are no explicit validation checkpoints.

Suggestions

Make the 'Native constraints' example self-contained: add the `use` import for `FieldType`/`f` and a raw-string literal Rust accepts, so it is copy-paste ready.

Add an explicit verify step after `forward()` (e.g. assert the output schema or run a no-key example) to give the workflow a validation checkpoint.

Move the 'Relevant API Surface' list closer to the Core Pattern or point it at API.md so the inlined API items are fully split out.

Dimension	Reasoning	Score
Conciseness	Lean throughout: short section intros ('Use the string form when field names and types are enough', 'A class field constrains the model to a known label set') followed directly by runnable code, with no preamble explaining what Rust, signatures, or JSON schema are.	5 / 5
Actionability	Examples are executable Rust snippets covering the common cases (string form, class output, native constraints, schema render, signature reuse), but the 'Native constraints' snippet is incomplete — `f()` and `FieldType`/`r...` are used without the import or builder origin, so it is not fully copy-paste ready.	4 / 5
Workflow Clarity	Sequenced guidance ('Start from package examples for exact native syntax before inventing a new call shape') and guarded branch selection (provider-api vs no-key examples) form a clear path, but there is no explicit validate/verify checkpoint after building a signature or running forward().	4 / 5
Progressive Disclosure	Well-organized sections with one-level-deep pointers to real bundle artifacts (API.md, axir-api.json, axir-capabilities.json, examples/, and an external gallery URL); a few key API items are inlined rather than fully split out, so it is not maximal.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

The description is specific, trigger-led, and well-scoped to the axllm Rust signatures domain, answering both what and when explicitly. Slightly technical phrasing keeps trigger-term quality and specificity just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (Rust/axllm) and lists several concrete actions — 'string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes' — but coverage stays within one narrow subsystem rather than spanning the package comprehensively.	4 / 5
Completeness	Explicitly answers both 'what' (signatures, field descriptors, JSON schema, validation, tool argument shapes) and 'when' (the leading 'Use when writing Rust code with axllm for...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'writing Rust code with axllm', 'signatures', 'JSON schema', and 'validation' are natural, on-topic triggers, though the phrasing leans technical and omits more casual synonyms.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific generated package (axllm) and Rust signatures, giving it a clear niche with minimal overlap against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ax-llm/ax
Path: website/static/rust/.well-known/agent-skills/ax-rust-signature/SKILL.md
Commit: 1abea97

Reviewed: ~18 hours ago

Table of Contents

Discovery Implementation Validation

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.