CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-audio

Paid Gemini TTS audio for a finished blog post: summary, full read-aloud, or two-speaker dialogue, with an MP3 and an HTML5 embed. Asks for explicit consent before the first paid call. Runs only on an explicit request: /blog audio, "generate audio for this blog post", "narrate this blog post", "audio version of this post", or "podcast version of this post". Not for general speech or dictation questions.

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A strong, highly executable skill body: complete commands, a well-sequenced workflow with validation and cost caps matched to the paid API, and disciplined externalization of volatile facts into dated reference files. The only weakness is token efficiency in the runtime-directory section and some repetition of the consent and command material.

Suggestions

Tighten the 'Persistent runtime directory' section to a short rule list (one trusted absolute root, fail-closed on relative/unresolved paths, no migration) and move the plugin retention and quoting rationale into a reference file.

Drop the 'Quick Reference' command table or the duplicated setup/consent text, since the same commands and gate rules appear verbatim in later sections.

Move the per-platform embed snippets (Hugo/MDX/WordPress) into a small references/embed.md and keep only the standard HTML5 tag and placement rule inline.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific with little explanation of concepts Claude already knows, but the dense 'Persistent runtime directory' section (plugin data retention, migration rules, quoting rationale) is convoluted, and the consent gate and Quick Reference repeat information already stated in the mandatory gate section. Dated facts are properly deferred to references/models.md. Anchor 5 ('every token earns its place') is not met due to this repetition; anchor 3 would require unnecessary explanations of known concepts, which are absent.

4 / 5

Actionability

Fully executable throughout: copy-paste bash for the wrapper (including the absolute-path case guard), generation commands for both single-voice and two-voice modes with explicit flags, an API-key check snippet, a dry-run verification command, and per-platform embed snippets. The common cases (generate, voices, setup, dialogue) are all covered with runnable commands.

5 / 5

Workflow Clarity

The generate workflow is a clearly sequenced 6-step process with explicit validation checkpoints appropriate to a paid batch operation: API key gate, consent gate with cost estimate before the first paid call, '--dry-run --json' estimate, '--max-chunks' cap with 'stop and ask the user before raising it', a one-retry limit, and an error-handling table with recovery actions. Feedback loops (rate-limit wait-and-retry, setup dry-run verification) are present.

5 / 5

Progressive Disclosure

Clean split verified against the actual bundle: dated model/pricing facts live in references/models.md and the 30-voice catalog in references/voices.md (both real files), each one level deep and clearly signaled. The body explicitly instructs 'Load on-demand: do NOT load all at startup' and describes what each reference contains, while keeping workflow and quick-reference recommendations inline where they belong.

5 / 5

Total

19

/

20

Passed

Description

100%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.

A model description: concrete third-person capability statement, an explicit consent-cost caveat, five natural trigger phrasings with synonyms, and a negative-scope clause that sharply reduces conflict risk. Both 'what' and 'when' are answered explicitly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage: 'summary, full read-aloud, or two-speaker dialogue, with an MP3 and an HTML5 embed' plus the consent behavior ('Asks for explicit consent before the first paid call'). All three modes, both output artifacts, and the spending gate are named explicitly.

5 / 5

Completeness

Explicitly answers both what (paid Gemini TTS audio of a finished blog post in three modes, MP3 plus HTML5 embed) and when ('Runs only on an explicit request:' followed by concrete trigger phrases), and adds negative scope ('Not for general speech or dictation questions'). Exceeds the level-4 anchor where 'when' could be more explicit.

5 / 5

Trigger Term Quality

Five natural user phrasings with synonym coverage: '/blog audio', "generate audio for this blog post", "narrate this blog post", "audio version of this post", "podcast version of this post". These are exactly the phrasings a user would say; file extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche (blog-post audio narration) with distinct blog-specific triggers, and the explicit exclusion 'Not for general speech or dictation questions' prevents overlap with generic TTS/speech skills. Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-audio/SKILL.md

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.