CtrlK
BlogDocsLog inGet started
Tessl Logo

podcast-generation

Generate real audio narratives from text content using Azure OpenAI's Realtime API.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/podcast-generation/SKILL.md

The canonical home for this skill is podcast-generation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-5

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

A solid skill that provides concrete, executable code for Azure OpenAI Realtime API audio generation with good structure and reasonable conciseness. Its main weaknesses are the lack of error handling/validation checkpoints in the workflow and references to bundle files that don't exist, leaving a key dependency (PCM-to-WAV conversion) unresolved. The 'When to Use' section is meaningless filler.

Suggestions

Add error handling code for WebSocket connection failures and empty audio responses (e.g., check `len(audio_chunks) > 0` before conversion, wrap connection in try/except with specific error types).

Either inline the `pcm_to_wav` function implementation or provide the referenced `scripts/pcm_to_wav.py` bundle file — this is a critical dependency that's currently missing.

Remove the 'When to Use' section, which is a tautology that wastes tokens.

Add a validation step after WAV conversion (e.g., check file size, verify WAV header) to create a feedback loop before returning to the frontend.

DimensionReasoningScore

Conciseness

Generally efficient with minimal unnecessary explanation. The voice options table and audio format section are concise. Minor over-explanation exists (e.g., the 'When to Use' section is a vacuous tautology that adds nothing). The note about the endpoint URL format is genuinely useful non-obvious information.

4 / 5

Actionability

Provides executable Python and JavaScript code for both backend generation and frontend playback. The code is mostly copy-paste ready. Minor gap: the pcm_to_wav function is referenced but not defined inline (deferred to a script file), and error handling is only mentioned in the events list without concrete code.

4 / 5

Workflow Clarity

The Quick Start lists a clear 5-step sequence, and the core workflow sections follow that sequence. However, there are no validation checkpoints — no error handling code for WebSocket connection failures, no verification that audio was actually generated before conversion, and no feedback loop for API errors. For an operation involving external API calls and audio processing, this absence of validation caps the score at 3.

3 / 5

Progressive Disclosure

References to architecture.md, code-examples.md, and pcm_to_wav.py are listed, but no bundle files are actually provided, making these references unverifiable dead links. The inline content is reasonably structured with clear sections, but the critical pcm_to_wav function is deferred to a non-existent file, creating a gap in the skill's completeness.

3 / 5

Total

14

/

20

Passed

Description

45%Scale 1-5

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 specific technology stack and core action but is too terse to serve as an effective skill selector. It lacks a 'Use when...' clause, misses common synonyms users would naturally say (e.g., 'text-to-speech', 'TTS'), and doesn't enumerate the full range of capabilities beyond basic generation.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'when the user asks to convert text to speech, generate audio narration, create spoken audio, or mentions TTS'.

Include common synonyms and related terms such as 'text-to-speech', 'TTS', 'voice generation', 'spoken audio', and 'narration'.

Expand the capability list to mention specifics like supported voice options, output formats, or content types that can be narrated.

DimensionReasoningScore

Specificity

Names the domain (audio narratives from text) and one concrete action (generate), plus specifies the technology (Azure OpenAI's Realtime API), but doesn't describe additional capabilities like format options, voice selection, or output handling.

3 / 5

Completeness

Has a clear 'what' (generate audio narratives from text using Azure OpenAI's Realtime API) but completely lacks a 'when' clause or any trigger guidance. Per rubric guidelines, missing 'Use when...' caps completeness at 3, and this is a weak case even within that cap.

2 / 5

Trigger Term Quality

Includes relevant terms like 'audio', 'narratives', 'text content', and 'Azure OpenAI', but misses common user phrases like 'text-to-speech', 'TTS', 'voice generation', 'read aloud', 'spoken audio', or file extensions.

3 / 5

Distinctiveness Conflict Risk

The specificity of 'Azure OpenAI's Realtime API' and 'audio narratives' makes it fairly distinct from general text-to-speech or other audio skills, though there could be minor overlap with other audio generation or TTS skills.

4 / 5

Total

12

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.