CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

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-audio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, knowledgeable reference with unusually specific provider defaults, key names, and error semantics, plus sensible guardrails and a no-key verification path. Its weaknesses are structural: an oversized inlined API symbol list (much of it non-audio) and the absence of one complete runnable example.

Suggestions

Trim the 'Relevant API Surface' list to the audio/realtime-relevant symbols (e.g., `ai`, `AxAIClient::speak`, `OpenAIResponsesClient`, `AxChatStream`) and point readers to `API.md` / `axir-api.json` for the full surface — this addresses both conciseness and progressive disclosure.

Add one complete, copy-paste runnable `speak()` example showing the request construction and the returned `data`/`format`/`transcript` fields, so the Core Pattern fragment becomes fully executable guidance.

Make the task approach an explicit ordered sequence — check `axir-capabilities.json`, pick the closest `examples/` example, apply the speech/audio field rules, verify with a `no-key` example — to turn the implicit workflow into explicit steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient — every bullet is factual package-specific behavior ('OpenAI defaults to `gpt-4o-mini-tts` with the `alloy` voice', 'Mistral defaults to `voxtral-mini-tts-2603`') with no primers on Rust or audio concepts. However, the ~40-symbol 'Relevant API Surface' bullet inlines many items unrelated to audio or realtime (`AxBalancer`, `set_meter`, `AxTracer`, `AxUsageObserver`), a non-trivial amount of content that could be tightened, matching the 3 anchor ('mostly efficient but includes some... could be tightened') better than the 4 anchor's 'minor instances'.

3 / 5

Actionability

Concrete guidance dominates: real Rust code ('use axllm::ai; let llm = ai("openai", options)?;'), exact result keys ('data` (base64 audio), `format`, `mimeType`, `transcript`'), exact provider defaults and error behavior, and directives like 'Start from package examples for exact native syntax'. It stops short of 5 because no complete copy-paste example exists — the core pattern is a fragment with undefined `options`, and the referenced `examples/` are deferred rather than shown.

4 / 5

Workflow Clarity

For a single-purpose reference skill, the approach is discernible and includes a validation checkpoint: 'Use `no-key` examples for deterministic local checks and provider request mapping' plus 'Keep live provider calls behind explicit credentials'. The sequence (consult examples → apply speak()/audio semantics → verify with no-key examples) is implicit rather than ordered, which is the minor gap keeping it at 4 instead of the simple-skill 5 ('single action is unambiguous' is undercut by the scattered presentation).

4 / 5

Progressive Disclosure

Sections are well-labeled (When To Use, Package Facts, Core Pattern, Guardrails) and package references are clearly signaled ('API.md and axir-api.json', 'axir-capabilities.json', 'examples/'), but no bundle files exist and the large inlined API symbol list is exactly the 'content that should be separate is inline' pattern of the 3 anchor. It is not the 4 anchor's 'most content appropriately placed' because the API reference block dominates a skill body that should point to API.md for it.

3 / 5

Total

14

/

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, appropriately concise description: it leads with an explicit 'Use when' trigger, names a highly specific niche (Rust + axllm + audio/realtime), and enumerates concrete task areas. Its main gap is missing natural synonyms (speech, TTS, voice, transcription) that users would likely say when needing this skill.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'audio input/output', 'OpenAI Responses audio mapping', 'realtime event folding', and 'generated package audio examples' — anchored to a named package (`axllm`) and language (Rust). They read as topic areas rather than the crisp verb actions of the 5 anchor ('extract... fill... merge'), and coverage of the audio surface (e.g., speech synthesis, transcription request mapping) has minor gaps, so 4 fits better than 5 and clearly above the 1-2-action coverage of 3.

4 / 5

Completeness

The 'when' is explicit ('Use when writing Rust code with `axllm` for...') and the 'what' is conveyed through the enumerated task areas, satisfying the 4 anchor's 'both present, when could be more explicit'. It falls short of 5 because the capability statement is embedded inside the trigger clause rather than stated as a separate explicit what ('Assists with...'), and the 3 anchor ('what' clear but 'when' missing) clearly does not apply since the when clause leads the description.

4 / 5

Trigger Term Quality

Natural terms a user would say are present — 'Rust', 'audio input/output', 'OpenAI Responses', 'realtime', 'audio examples' — matching the 'good keyword coverage; a few natural terms missing' anchor. Common synonyms like 'speech', 'TTS', 'voice', and 'transcription' are absent, which keeps it below the 5 anchor's comprehensive synonym coverage but above the 3 anchor's merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The combination of 'Rust code with `axllm`', 'OpenAI Responses audio mapping', and 'realtime event folding' carves a clear niche with distinct triggers and minimal conflict risk, matching the 5 anchor exactly; the 4 anchor's 'minor overlap risk with closely related skills' is not triggered because the Rust qualifier separates it from any TypeScript-package sibling.

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