audio-transcriber

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

2.17x

Quality

30%

Does it follow best practices?

Impact

85%

2.17x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Discovery

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 suffers from missing explicit trigger guidance and lacks comprehensive action verbs. The phrase 'intelligent summaries using LLM integration' is vague marketing language rather than concrete capability description. Without a 'Use when...' clause, Claude may fail to select this skill appropriately.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'transcribe', 'audio file', 'meeting recording', 'voice memo', or file extensions like '.mp3', '.wav'

Replace vague phrases like 'intelligent summaries using LLM integration' with concrete actions such as 'transcribe speech, extract action items, generate meeting notes'

Include common user language variations: 'transcription', 'speech-to-text', 'meeting notes', 'podcast notes'

Dimension	Reasoning	Score
Specificity	Names the domain (audio recordings, Markdown documentation) and mentions some actions (transform, summaries), but lacks comprehensive concrete actions like 'transcribe', 'format timestamps', 'extract key points', or specific output formats.	2 / 3
Completeness	Describes what it does (transform audio to documentation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms ('audio recordings', 'Markdown documentation', 'summaries') but misses common user variations like 'transcribe', 'meeting notes', 'voice memo', 'mp3', 'wav', or 'speech-to-text'.	2 / 3
Distinctiveness Conflict Risk	The audio-to-documentation niche is somewhat specific, but 'professional Markdown documentation' and 'intelligent summaries' could overlap with general documentation or summarization skills without the explicit audio trigger.	2 / 3
	Total	7 / 12 Passed

Implementation

27%

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

This skill suffers from severe verbosity, including over 400 lines of content that could be condensed to under 100 lines. While it attempts to be comprehensive, it explains too many basic concepts, includes incomplete placeholder code, and lacks proper progressive disclosure. The workflow has missing steps (2 and 4) and inconsistent structure that would confuse implementation.

Suggestions

Reduce content by 70%+ by removing explanations of basic concepts (file existence checks, format lists) and condensing examples to 1-2 representative cases

Complete the placeholder functions (cluster_by_topic, extract_action_items, call_ai_model) or remove them and provide actual executable implementations

Fix the workflow numbering (Steps 0, 1, 3, 5 are present but 2 and 4 are missing) and consolidate the fragmented scenario sections

Split detailed content into separate reference files (e.g., EXAMPLES.md, INSTALLATION.md, OUTPUT-TEMPLATES.md) and keep SKILL.md as a concise overview with clear links

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive bash scripts, redundant explanations, and multiple lengthy examples. The content explains basic concepts Claude already knows (what formats are supported, how to check if files exist) and includes excessive boilerplate that could be dramatically condensed.	1 / 3
Actionability	Contains executable code snippets and bash commands, but many are incomplete or pseudocode-like (e.g., `call_ai_model(summary_prompt)` is a placeholder). The Python functions like `cluster_by_topic()` and `extract_action_items()` are referenced but never defined.	2 / 3
Workflow Clarity	Steps are numbered and sequenced (Step 0, 1, 3, 5 - notably missing Step 2 and 4), but validation checkpoints are inconsistent. The workflow jumps between scenarios without clear decision trees, and error recovery paths are incomplete. Missing steps create confusion.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files for detailed content. Everything is inline including lengthy code blocks, multiple examples, and scenario descriptions that could be split into separate reference documents. No clear navigation structure.	1 / 3
	Total	6 / 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 (556 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: 5c5ae21

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