CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

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

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

Well-structured and lean, but the body relies on a minimal code fragment plus external references rather than a complete executable example, and lacks an explicit validation step in its workflow. The inline API surface list and missing bundle files limit progressive disclosure.

Suggestions

Replace the two-line Core Pattern fragment with a complete, copy-paste-ready example (including `options` definition and a basic call) so the body is executable without leaving SKILL.md.

Add an explicit validation checkpoint to the workflow, e.g. "run `cargo check` and verify behavior against a `no-key` example before finalizing."

Move the inline "Relevant API Surface" symbol list into the referenced `API.md` (and include `API.md`, `axir-api.json`, `axir-capabilities.json`, and `examples/` in the bundle) so SKILL.md stays a lean overview with one-level-deep references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the inline "Relevant API Surface" symbol list duplicates the referenced `API.md`, a minor instance of content that could be trimmed.

4 / 5

Actionability

The Core Pattern is only a two-line fragment (`let llm = ai("openai", options)?;` with `options` undefined) and the body defers to `examples/` for complete code, leaving key execution details missing.

3 / 5

Workflow Clarity

The Guardrails provide rough guidance but there is no sequenced workflow and no validation checkpoint (e.g., run `cargo check` or verify against `no-key` examples), leaving checkpoints implicit.

3 / 5

Progressive Disclosure

Sections are clear and references to `API.md`, `axir-api.json`, and `examples/` are signaled, but the large inline API-surface list is content that belongs in a separate file, and the referenced files are not present in the bundle.

3 / 5

Total

13

/

20

Passed

Description

92%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, specific description with an explicit "Use when…" trigger and a comprehensive list of concrete actions in a distinct niche. The only minor gap is the absence of synonyms or file extensions that would push trigger-term coverage to the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples" — giving comprehensive coverage of the skill's domain.

5 / 5

Completeness

Explicitly answers both "what" (the four concrete actions) and "when" via the literal "Use when writing Rust code with `axllm`" trigger phrase.

5 / 5

Trigger Term Quality

Good natural keywords ("writing Rust code", "audio input/output", "realtime event folding", "OpenAI Responses") a user would say, but missing common synonyms or file extensions, so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Rust + `axllm` + audio/realtime — with distinct, specialized triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

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.