ax-rust-audio

Use when writing Rust code with `axllm` for audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples.

Quality

81%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-organized reference skill that mostly respects token budget and workflow clarity, but its actionability and progressive disclosure are weakened by a thin inline code example and by referencing bundle files that are not present.

Suggestions

Add one complete, copy-paste-ready Rust example (e.g., a full audio request mapped through axllm) instead of relying on the single-call Core Pattern fragment.

Either ship the referenced bundle files (API.md, axir-api.json, axir-capabilities.json, examples/) or remove/qualify the references so navigation does not break.

Move the inline 'Relevant API Surface' symbol dump into API.md and link to it, keeping the body as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is lean, well-sectioned, and assumes Claude's competence with no concept teaching; the inline API symbol list is reference data rather than padding.	3 / 3
Actionability	It provides one minimal code fragment and specific file/example pointers, but the snippet is incomplete and most executable detail is delegated to example files rather than given copy-paste-ready inline.	2 / 3
Workflow Clarity	As a reference-style skill with a single API surface, its When-To-Use triggers and Guardrails sequence usage unambiguously, including an AxIR-source-of-truth regeneration guidance; no destructive batch step requires validation checkpoints.	3 / 3
Progressive Disclosure	It signals one-level-deep references (API.md, axir-api.json, axir-capabilities.json, examples/), but none of those bundle files actually exist and the API surface is dumped inline — structure is present but navigation breaks and content that belongs in a referenced file is inline.	2 / 3
	Total	10 / 12 Passed

Description

85%

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, scoped description with an explicit trigger and concrete capability list; its only real weakness is trigger phrasing that leans on package-specific jargon rather than terms users naturally say.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'audio input/output', 'OpenAI Responses audio mapping', 'realtime event folding', and 'generated package audio examples' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Opens with an explicit 'Use when...' clause and enumerates what the skill does, so both what and when are answered with an explicit trigger.	3 / 3
Trigger Term Quality	'writing Rust code' and 'audio' are natural, but 'OpenAI Responses audio mapping', 'realtime event folding', and 'generated package audio examples' are specialist jargon a user would rarely say, and common variants ('voice', 'speech', 'realtime audio') are missing.	2 / 3
Distinctiveness Conflict Risk	The Rust + axllm + audio/realtime niche is clearly scoped and unlikely to collide with a generic Rust or LLM skill.	3 / 3
	Total	11 / 12 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-audio/SKILL.md
Commit: fe8baf8

Reviewed: 5 days 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.