audio-transcriber
Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration
37
23%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-audio-transcriber/SKILL.mdQuality
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 conveys the general purpose of converting audio to Markdown documentation but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It uses somewhat buzzwordy language ('intelligent summaries', 'professional') without concrete actions, and critically omits a 'Use when...' clause that would help Claude know when to select this skill.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user wants to transcribe audio files, convert recordings to text, or generate meeting notes from audio.'
Include natural trigger terms users would say, such as 'transcribe', 'transcription', 'meeting notes', 'voice memo', '.mp3', '.wav', 'speech-to-text'.
Replace vague qualifiers like 'professional' and 'intelligent' with specific concrete actions, e.g., 'Transcribes audio files to text, generates structured Markdown with headings and timestamps, and produces topic summaries.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (audio recordings, Markdown documentation) and mentions some actions (transform, summaries, LLM integration), but lacks specific concrete actions like 'transcribe speech', 'generate timestamps', 'extract key points', 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 broad enough to overlap with general documentation or summarization skills. The audio focus helps but isn't sharply delineated. | 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 suffers from severe verbosity, disorganized workflow (missing steps 2 and 4), and incomplete implementation (placeholder functions without definitions, missing core transcription step). The content mixes languages, includes excessive terminal UI mockups, and fails to separate concerns into referenced files. While the intent is clear, the execution makes it difficult for Claude to follow reliably.
Suggestions
Fix the workflow numbering (Steps 2 and 4 are missing) and add the actual transcription step with executable code, not just validation and output formatting
Replace placeholder functions (call_ai_model, cluster_by_topic, extract_action_items) with actual implementations or remove them in favor of concrete instructions
Move installation instructions, output templates, and examples into separate referenced files (e.g., INSTALL.md, TEMPLATES.md, EXAMPLES.md) to reduce the main file to a concise overview
Remove redundant terminal output mockups and consolidate to one example; eliminate explanations of basic concepts like file existence checks and format validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ 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 could be condensed to under 100 lines. The installation walkthrough, interactive prompts, and multiple example scenarios are excessive padding. | 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) appears to be missing entirely - it jumps from Step 1 to Step 3. Key implementation details are absent. | 2 / 3 |
Workflow Clarity | The workflow is disorganized and incomplete. Step numbering is inconsistent (Step 0, Step 1, Step 3, Step 5 - missing Steps 2 and 4). The 'Scenario A' section appears mid-flow without clear context. There are no validation checkpoints between transcription and output generation. The batch processing example lacks any validation or error recovery steps. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files for detailed content. The entire installation guide, all examples, output templates, and LLM processing details are inlined. Content that should be in separate files (installation guide, output templates, examples) bloats the main skill file significantly. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
81%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 (555 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
f1697b6
- 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.