ax-cpp-audio

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

Quality

67%

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/cpp/skills/ax-cpp-audio/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The body is well-structured and free of padding, but it relies on a single minimal code snippet plus pointers to external files that are not present in the bundle, and it lacks an explicit sequenced workflow with validation. It reads as a reference card more than a complete, self-contained guide.

Suggestions

Add one or two complete, copy-paste-ready C++ examples (e.g. a no-key event-folding example and a provider-api audio example) directly in the body so guidance is actionable without the missing external files.

Ship the referenced bundle files (`API.md`, `axir-api.json`, `axir-capabilities.json`, `examples/`) under references/ or assets/, or remove the dangling references so progressive-disclosure navigation is real.

Tighten the 'Relevant API Surface' list to the audio/realtime symbols this skill actually targets, moving balancer/router/usage-observer entries to a separate reference to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with no concept over-explanation, but the 'Relevant API Surface' line dumps many balancer/router/usage-observer symbols that sit outside the skill's audio focus and could be tightened, landing between efficient and fully lean.	2 / 3
Actionability	A concrete two-line 'Core Pattern' snippet and a list of API symbols are provided, but full copy-paste-ready examples are deferred to external `examples/` and `API.md` rather than included, so guidance is concrete but incomplete.	2 / 3
Workflow Clarity	The 'When To Use' and 'Guardrails' sections give scenario and rule guidance, but there is no explicit multi-step sequence or validation checkpoint; the sequence is implied rather than staged with feedback loops.	2 / 3
Progressive Disclosure	Sections are reasonably organized and references to `API.md`, `axir-api.json`, `axir-capabilities.json`, and `examples/` are clearly signaled one level deep, but none of these referenced bundle files actually exist in references/scripts/assets, so the navigation is broken rather than complete.	2 / 3
	Total	8 / 12 Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and clearly distinguishes a niche C++ audio/realtime skill. Its only weakness is that several capability phrases lean on internal jargon ('realtime event folding', 'generated package audio examples') rather than terms users naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'audio input/output, OpenAI Responses audio mapping, realtime event folding, and generated package audio examples' — rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	It explicitly answers both 'what' (the listed audio/realtime capabilities) and 'when' (an explicit 'Use when...' clause), meeting the both-what-and-when anchor.	3 / 3
Trigger Term Quality	It opens with a clear 'Use when writing C++ code' trigger and natural terms like 'audio input/output' and 'realtime', but 'realtime event folding' and 'OpenAI Responses audio mapping' are technical jargon a user would be less likely to say verbatim, so coverage is good but not comprehensive.	2 / 3
Distinctiveness Conflict Risk	The narrow combination of 'C++ code with `axllm`' plus audio/realtime/OpenAI-Responses mapping defines a clear niche unlikely to trigger for unrelated skills.	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/cpp/skills/ax-cpp-audio/SKILL.md
Commit: 9087a01

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