CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

narrator

Activate when the user explicitly names the narrator skill or requests production-ready narration in either case: (1) numbered takes fitted to fixed video windows, or (2) one continuous long-form story read in a locked voice that must be measured and retried for timbre or internal pauses. Collect missing text, voice_id, or voice_type after activation; their absence is not a reason to skip this workflow. Own pacing, speech-duration gates, retries, and ready audio delivery; never time-stretch. Do not use for ordinary TTS, "read this aloud", an unconstrained voiceover, voice browsing, music, SFX, singing, dubbing existing speech, or voice cloning.

Quality

92%

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

88%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 is an exceptionally actionable operational contract: exact tool calls, payloads, commands, numeric targets, speech-validation gates, and bounded feedback loops for both modes, with no filler or teaching of known concepts. Cross-section rule duplication and a deployment-path-only reference to the bundled metrics script keep it just short of top marks on conciseness and progressive disclosure.

Suggestions

Deduplicate rules stated twice — the voice-lock rule ("re-read that file before EVERY call") and the no-resubmit rule ("Retry only failed takes; never resubmit completed ones") both reappear in 'Hard rules'; state each once and keep 'Hard rules' as one-line recaps without re-explaining.

Reference the bundled script by its bundle-relative path (scripts/speech_metrics.sh, matching its own usage header) alongside the ${HF_WORKFLOWS} deployment path, so the reference is discoverable from the skill folder itself.

Trim motivational rationales where the rule is already emphatic (e.g. "A remembered-not-reread pair is exactly how a video ends up with different voices per block") to bare directives.

DimensionReasoningScore

Conciseness

Dense operational directives with no teaching of concepts Claude already knows, and the explanatory asides carry unknown domain facts ("Every period ≈0.7s and comma ≈0.5s of dead air", "The script trims the provider's head/tail padding"). Not 5: several rules are stated twice across sections ("re-read that file before EVERY call" vs "ONE voice everywhere... re-read from voice.lock"; "Never resubmit the whole batch because one line failed" vs "Retry only failed takes; never resubmit completed ones"), and some motivational rationales ("A remembered-not-reread pair is exactly how a video ends up with different voices per block") could be trimmed. Not 3: there is no real padding or over-explanation.

4 / 5

Actionability

Fully executable, copy-paste ready: exact tool calls and payload shapes ("generate_audio_batch. Every item is {index, params:{model:\"seed_audio\", prompt, voice_id, voice_type, format:\"wav\", count:1}}"), an exact prompt template ("[ {DELIVERY}, {optional line mood}, starts speaking immediately] [00:00-00:09] {line}"), an exact sandbox command ("bash ${HF_WORKFLOWS}/.../speech_metrics.sh work/voices/voice01.wav"), and an exact join command ("ffmpeg -f concat -safe 0 -i parts.txt -c copy work/voices/narration.wav"), all with concrete numeric targets (9.4–9.8s window, ~30–34 words, groups of six, timeout_seconds:25, 2048-char limit, ~1800-char chunks).

5 / 5

Workflow Clarity

Clear sequences per mode with explicit validation gates ("`speech=` must land in the window; `pauses=` must be 0"), feedback loops ("Out of window → REWRITE THE TEXT and regenerate. Never atempo..."; "Retry only failed takes; never resubmit completed ones"), error-recovery paths ("If all_terminal:false, wait poll_after_seconds and call it again"), and anti-loop protections ("If the group shows no status change for 20 minutes, return its pending indices/job ids to the caller instead of looping silently"; "Budget ~3 attempts per line... never loop"). This batch workflow has validation and retry handling throughout, so the batch-cap at 3 does not apply.

5 / 5

Progressive Disclosure

Well-sectioned single file (Inputs/outputs, tool contract, Mode A, Mode B, Hard rules, Reporting, Safety) where all inline content is needed at runtime; the bundled script exists (scripts/speech_metrics.sh, real and functional). Not 5: the body never points to the bundle by its own path — the script is referenced only via its deployment path "${HF_WORKFLOWS}/faceless-channel-video/scripts/narrator/speech_metrics.sh", and assets/icon.svg is unused, so references are not well-signaled relative to the actual bundle structure. Not 3: structure is strong and navigation within the file is easy.

4 / 5

Total

18

/

20

Passed

Description

92%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 highly specific, well-scoped description with an explicit activation clause covering two concrete use cases, a thorough exclusion list, and imperative (not first/second person) voice. Trigger keywords are strong, though a few natural phrasing variants are missing.

DimensionReasoningScore

Specificity

Multiple concrete actions with comprehensive coverage end-to-end: "numbered takes fitted to fixed video windows", "one continuous long-form story read in a locked voice", "Own pacing, speech-duration gates, retries, and ready audio delivery; never time-stretch", plus intake behavior ("Collect missing text, voice_id, or voice_type"). Not 4: coverage spans the whole workflow (intake, pacing, gating, retries, delivery) rather than several actions with minor gaps.

5 / 5

Completeness

Explicitly answers both questions. What: paced, gated, retried narration delivery with fixed-window fitting. When: "Activate when the user explicitly names the narrator skill or requests production-ready narration in either case: (1) numbered takes fitted to fixed video windows, or (2) one continuous long-form story..." plus a "Do not use for..." exclusion list. Not 4: the when is fully explicit with concrete trigger conditions, not merely present or implicit.

5 / 5

Trigger Term Quality

Good keyword coverage: "narrator", "narration", "numbered takes", "fixed video windows", "long-form story", "locked voice", "timbre", "internal pauses", plus exclusion terms ("ordinary TTS", "read this aloud", "voice cloning"). Not 5: a few natural user phrasings are absent ("narrate", "voice-over" spelling variant, "audiobook"-style synonyms), so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (fixed-window video narration with measured speech gating and one locked voice) with distinct triggers, and the explicit exclusion list ("Do not use for ordinary TTS, 'read this aloud', an unconstrained voiceover, voice browsing, music, SFX, singing, dubbing existing speech, or voice cloning") removes the main overlap risks. Not 4: no minor overlap remains because the nearest competing use cases are explicitly ruled out.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/higgsfield/skills/narrator/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.