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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/rust/skills/ax-rust-signature/SKILL.md

Quality

Content

68%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 well-structured, mostly actionable reference with clean code examples and good progressive-disclosure signaling. It lacks an explicit multi-step workflow with validation checkpoints, and a few code examples are redundant or not fully self-contained.

Suggestions

Add a short numbered workflow (e.g. pick pattern → build signature → render schema → attach to AxGen → run from examples/) with an explicit verify step so multi-step use is unambiguous.

Make code snippets self-contained (full `use` imports and enclosing `fn main() -> Result<...>` context) or explicitly state they are excerpts to be placed into the example programs.

De-duplicate the `to_json_schema("outputs")` call and consolidate the Core Pattern and Simple string contract examples to trim tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean with terse fact bullets and focused code blocks, but "Core Pattern" overlaps the "Simple string contract" example and `to_json_schema("outputs")` appears twice, so a few tokens could be trimmed.	4 / 5
Actionability	Concrete executable Rust snippets cover the common cases (string form, class output, native constraints, JSON schema, reuse), but they are fragments missing full imports/`fn main`/Result context, leaving minor gaps before copy-paste completeness.	4 / 5
Workflow Clarity	There is an implied progression (Core Pattern → More Patterns → "start from examples") and guardrails give selection guidance, but no explicit sequenced multi-step workflow with validation checkpoints is present.	3 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep pointers ("API.md", "axir-api.json", "examples/", and the gallery URL) keep SKILL.md an overview; however those referenced paths are not present in the bundle to verify, a minor navigation gap.	4 / 5
	Total	15 / 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 precise, third-person description that names a clear niche and several concrete capabilities with an explicit "Use when" trigger. It could add user-natural trigger phrases distinct from the capability list to reach the top anchor.

Suggestions

Add concrete user-side trigger phrases (e.g. "Use when the user asks for Ax signatures, output schemas, or typed tool args in Rust") so the "when" is distinct from the capability list.

Soften jargon like "field descriptors" and "typed tool argument shapes" with synonyms a user might actually say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes" — giving comprehensive coverage of the package's surface rather than a single vague action.	5 / 5
Completeness	The "Use when writing Rust code with `axllm` for ..." clause supplies both a what and a when, but the when largely restates the capability list rather than offering distinct user-facing trigger phrases, so it falls just short of the anchor-5 example.	4 / 5
Trigger Term Quality	Good keyword coverage with natural terms ("Rust code", "axllm", "JSON schema", "validation", "tool argument shapes"), though "field descriptors" and "typed tool argument shapes" lean technical and lack common synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply scoped to writing Rust code with the `axllm` package for Ax signature constructs, making collision with unrelated skills very unlikely.	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: packages/rust/skills/ax-rust-signature/SKILL.md
Commit: dec4f9e

Reviewed: ~23 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.