CtrlK
BlogDocsLog inGet started
Tessl Logo

ax-audio

This skill helps an LLM generate correct audio code with @ax-llm/ax. Use when the user asks about ai.transcribe(), ai.speak(), signature audio inputs or outputs, agent audio behavior, .chat() conversational audio, OpenAI audio or realtime models, Gemini Live native audio, Grok Voice Agent models, voices, formats, transcripts, or how audio fits with structured outputs.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A thorough, highly actionable audio codegen reference with copy-paste TypeScript examples across all major providers and surfaces. It is well-structured and concise, with only minor opportunities to trim repeated boilerplate and to add explicit validation/error-recovery guidance for realtime WebSocket flows.

DimensionReasoningScore

Conciseness

The body is dense and mostly assumes Claude's competence, presenting rules and executable code with little padding; a few provider-default sections and repeated boilerplate (apiKey lines, console.log outputs) could be trimmed slightly.

4 / 5

Actionability

Every section provides complete, copy-paste-ready TypeScript examples covering the common cases (transcribe, speak, signatures, agents, chat, OpenAI/Gemini/Grok defaults, streaming), with concrete config shapes and field types.

5 / 5

Workflow Clarity

The opening 'Pick the smallest audio surface that matches the job' routing rule plus Core Rules clearly sequences which API to choose, but there are no explicit validation checkpoints or error-recovery feedback loops for risky operations like realtime WebSocket calls.

4 / 5

Progressive Disclosure

Content is well organized into clearly headed sections that each handle one provider/topic, with no bundle files present to offload detail; the inlined per-provider default lists are reasonable but a single-file ~370-line reference could benefit from splitting advanced provider specifics into separate files.

4 / 5

Total

17

/

20

Passed

Description

85%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 a clear 'what' and a detailed 'Use when' trigger clause scoped to the @ax-llm/ax audio domain. Trigger keywords and provider names are comprehensive, with only minor synonym/extension gaps preventing a perfect specificity and trigger_term score.

DimensionReasoningScore

Specificity

Names concrete actions (transcribe(), ai.speak(), .chat() audio config, signature audio inputs/outputs) covering the audio codegen domain, with only minor gaps such as omitting streaming as a named action.

4 / 5

Completeness

Explicitly states what the skill does ('helps an LLM generate correct audio code with @ax-llm/ax') and gives a concrete 'Use when...' clause enumerating trigger scenarios.

5 / 5

Trigger Term Quality

Includes many natural terms users would say (voices, formats, transcripts, OpenAI audio, Gemini Live, Grok Voice Agent) but is missing some synonyms and file extensions; strong but not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche scoped to @ax-llm/ax audio APIs and provider-specific audio models, with distinct triggers unlikely to collide with unrelated skills.

5 / 5

Total

18

/

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.