CtrlK
BlogDocsLog inGet started
Tessl Logo

podcast-generation

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

52

Quality

59%

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-claude/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

65%Weight 40%Scale 1-5

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

The body delivers concrete executable code and a clear section structure, but its workflow omits validation/error-recovery checkpoints and its progressive-disclosure references point to bundle files that are not present. Adding error-handling feedback and creating the referenced files would materially improve it.

Suggestions

Add an explicit error-handling/validation step in the audio-generation flow (detect 'error' events, verify non-empty PCM, retry on failure) to satisfy the feedback-loop expectation.

Create the referenced bundle files (references/architecture.md, references/code-examples.md, scripts/pcm_to_wav.py) or remove the broken references so navigation is sound.

Define or inline the pcm_to_wav conversion so the main code example is fully self-contained and copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is largely lean with sectioned Quick Start steps, code blocks, and compact tables, assuming Claude's competence with only minor trimmable redundancy (e.g. the restated description line), matching the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready Python and JavaScript code plus env config and event names, but relies on an external pcm_to_wav helper not defined inline, leaving a minor gap per the 'mostly executable, minor gaps' anchor.

4 / 5

Workflow Clarity

A 5-step Quick Start sequence is present but lacks validation checkpoints or error-handling feedback loops for the streaming audio generation, fitting the 'steps listed but validation gaps' anchor.

3 / 5

Progressive Disclosure

Sections are well-organized with a one-level-deep References block, but the referenced bundle files (references/architecture.md, references/code-examples.md, scripts/pcm_to_wav.py) do not exist, so the structure is only partially realized per the 'could be better organized' anchor.

3 / 5

Total

14

/

20

Passed

Description

53%Weight 40%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 clearly states what the skill does and names a specific provider/technology niche, but lacks any explicit 'Use when...' trigger guidance and only lists a single concrete action. Adding trigger phrases and enumerating a couple more actions would lift specificity and completeness.

Suggestions

Add an explicit trigger clause such as 'Use when generating audio narration, voiceovers, or text-to-speech from text using Azure OpenAI Realtime API.'

Enumerate 2-3 concrete actions (e.g. 'stream PCM audio, transcribe narration, convert to WAV') to improve specificity and trigger-term coverage.

Include common natural synonyms users say ('text-to-speech', 'narration', 'voiceover') to broaden trigger matching.

DimensionReasoningScore

Specificity

Names the domain (audio narratives from text) and one concrete action (generate audio) via Azure OpenAI's Realtime API, but does not enumerate several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Provides a clear 'what' (generate real audio narratives from text) but no 'Use when...' trigger clause; per guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes some natural terms like 'audio narratives' and 'Realtime API' but omits common phrasings a user would say ('text-to-speech', 'narration', 'voiceover'), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Azure OpenAI Realtime API audio-narration niche is mostly distinct from generic TTS skills with only minor overlap risk, matching the 'mostly distinct' anchor.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

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.