audio-transcriber

Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration

Quality

23%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-audio-transcriber/SKILL.md

Quality

Content

14%

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

This skill is excessively verbose, poorly organized, and incomplete in critical areas. The workflow has missing steps (the actual transcription step is absent), jumps in numbering, and lacks validation checkpoints. While it provides some concrete code, key functions are undefined placeholders, and the content mixes languages and includes extensive terminal UI mockups that waste tokens without adding actionable guidance.

Suggestions

Add the missing Step 2 (actual transcription execution) and fix step numbering to be sequential — this is the core functionality and it's entirely absent from the workflow.

Reduce content by 60-70%: remove terminal UI mockups, installation interactive flows, and obvious bash checks (file existence, format validation). Move examples and installation instructions to separate referenced files.

Replace placeholder functions (call_ai_model, cluster_by_topic, extract_action_items) with actual executable implementations or remove them entirely if they depend on user-specific integrations.

Add explicit validation checkpoints: verify transcription output is non-empty, validate generated Markdown structure, and include error recovery steps especially for batch processing.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Explains obvious concepts (what audio formats are, how to check if a file exists), includes extensive UI mockups for terminal output, mixes languages (Portuguese/English), and repeats information. Much of this content (installation flows, interactive prompts, progress bars) is unnecessary for Claude to know.	1 / 3
Actionability	Contains concrete bash and Python code snippets, but many are incomplete or pseudocode-like (e.g., `call_ai_model()`, `cluster_by_topic()`, `extract_action_items()` are undefined placeholders). The actual transcription step (Step 2) is entirely missing from the workflow, jumping from Step 1 to Step 3. Key implementation details are absent.	2 / 3
Workflow Clarity	The workflow is disorganized: Step 0 exists, Step 1 follows, then it jumps to Step 3 (Step 2 is missing — the actual transcription!), then Step 5 (no Step 4). Scenarios A appears without a Scenario B introduction. There are no validation checkpoints for the transcription output, and batch processing is shown in examples but has no workflow steps or validation/error recovery.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite the content being far too long for a single SKILL.md. The installation script, output templates, LLM processing logic, and examples could all be split into separate files. References to `scripts/install-requirements.sh` exist in code but no bundle files are provided or referenced as documentation.	1 / 3
	Total	5 / 12 Passed

Description

32%

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 identifies a clear domain (audio-to-documentation) but relies on buzzwordy language ('intelligent summaries', 'professional') without specifying concrete actions or providing explicit trigger guidance. It lacks a 'Use when...' clause, which is critical for skill selection, and misses natural user terms like 'transcribe' or 'meeting notes'.

Suggestions

Add a 'Use when...' clause with trigger terms like 'transcribe audio', 'meeting recording', 'voice memo', 'audio to text', '.mp3', '.wav'

Replace vague phrases like 'intelligent summaries' and 'professional Markdown documentation' with specific actions such as 'transcribe speech to text, identify speakers, generate section summaries, format as structured Markdown'

Include common file format keywords users would mention, such as '.mp3', '.wav', '.m4a', 'recording', 'meeting notes', 'transcription'

Dimension	Reasoning	Score
Specificity	Names the domain (audio recordings to Markdown documentation) and mentions some actions (transform, summaries, LLM integration), but lacks specific concrete actions like 'transcribe speech', 'generate timestamps', 'format speaker labels', etc.	2 / 3
Completeness	Describes what the skill does (transform audio to Markdown with summaries) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately clear, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'audio recordings', 'Markdown documentation', and 'summaries', but misses common user-facing terms like 'transcribe', 'transcription', 'meeting notes', 'voice memo', '.mp3', '.wav', or 'speech-to-text'.	2 / 3
Distinctiveness Conflict Risk	The combination of audio-to-Markdown is somewhat distinctive, but 'professional Markdown documentation' and 'intelligent summaries' are vague enough to potentially overlap with general documentation or summarization skills.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (560 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: boisenoise/skills-collections
Commit: 55f2150

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