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/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 is too high-level and lacks explicit trigger guidance. It reads more like a marketing tagline than a functional skill description, using buzzwords like 'intelligent' and 'professional' without specifying concrete capabilities. Adding a 'Use when...' clause and more specific action verbs would significantly improve skill selection accuracy.

Suggestions

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

Replace vague language ('intelligent summaries', 'professional Markdown documentation') with specific actions like 'transcribe speech to text, generate section headings, create bullet-point summaries, identify key topics'.

Include common file formats or contexts (e.g., 'meeting recordings, interviews, lectures, podcasts') to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain (audio recordings) and some actions (transform, summaries), but lacks specific concrete actions like 'transcribe speech', 'generate timestamps', 'identify speakers', or 'format transcripts'.	2 / 3
Completeness	It 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 somewhat vague, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'audio recordings', 'Markdown documentation', and 'summaries', but misses common user terms like 'transcribe', 'transcription', 'meeting notes', 'voice memo', '.mp3', '.wav', or 'speech-to-text'.	2 / 3
Distinctiveness Conflict Risk	The combination of audio + Markdown + LLM summaries is somewhat distinctive, but 'professional Markdown documentation' and 'intelligent summaries using LLM integration' are broad enough to overlap with general documentation or summarization skills.	2 / 3
	Total	7 / 12 Passed

Implementation

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, mixing languages and including extensive terminal UI mockups that waste tokens. Critical workflow steps are missing (the actual transcription step is absent, jumping from validation to output generation), and key functions are undefined placeholders. The content would benefit enormously from being split into separate files and trimmed to focus on the essential workflow with concrete, complete code.

Suggestions

Add the missing Step 2 (actual transcription execution) and Step 4, and renumber steps sequentially to create a coherent workflow with validation checkpoints after transcription completes.

Replace placeholder functions (call_ai_model, cluster_by_topic, extract_action_items) with actual executable implementations or remove them and describe the approach concisely.

Reduce content by 60-70%: remove terminal UI mockups, trim examples to one or two, eliminate installation flow details (move to a separate INSTALL.md), and cut explanatory prose Claude doesn't need.

Split into multiple files: move installation instructions to scripts/INSTALL.md, output templates to TEMPLATES.md, and examples to EXAMPLES.md, keeping SKILL.md as a concise workflow overview with references.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Explains obvious concepts (what audio formats are, how file validation works), includes extensive UI mockups for terminal output, mixes languages (Portuguese/English), and repeats information. Much of this content (installation flows, progress bar mockups, batch processing examples) is unnecessary for Claude.	1 / 3
Actionability	Contains concrete bash and Python code snippets for detection, validation, and processing, but critical pieces are pseudocode or placeholders (e.g., `call_ai_model()`, `cluster_by_topic()`, `extract_action_items()` are undefined). The actual transcription step (Step 2) appears to be missing entirely, jumping from Step 1 to Step 3.	2 / 3
Workflow Clarity	Steps are numbered inconsistently (Step 0, 1, 3, 5 — Steps 2 and 4 are missing). The core transcription step is absent. Scenarios A is described but Scenario B is never defined. No validation checkpoints exist for the actual transcription output. The batch processing example mentions no validation or error recovery for individual file failures.	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. Installation scripts, output templates, Python processing code, and multiple examples are all inlined. References to `scripts/install-requirements.sh` suggest bundle files should exist but none are provided or structured.	1 / 3
	Total	5 / 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: sickn33/antigravity-awesome-skills
Commit: 9e5d4dd

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