CtrlK
BlogDocsLog inGet started
Tessl Logo

krillinai-tts

Use when generating target-language dubbing with KrillinAI CLI from SRT subtitles, including TTS audio creation and optional dubbed video generation.

71

Quality

86%

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

86%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 compact, action-oriented skill body that gives Claude exactly what it needs: a runnable command, flag semantics, expected outputs, and verification steps. The only real gap is an example value for the provider-specific --voice flag and an explicit error-recovery loop in verification.

Suggestions

Add an example value or two for `--voice` (e.g. a provider-specific voice id) so the flag is immediately usable rather than left as 'Provider-specific voice'.

Include an explicit error-recovery branch in the Verification section (e.g. 'If ok is false or the wav is missing, check config/config.toml TTS provider settings and re-run with --dry-run') to close the feedback loop.

Confirm the referenced `skills/krillinai-cli/references/cli-contract.md` path is resolvable from this skill's location, or use a relative path so the one-level reference does not break.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept padding or over-explanation; every section (command, inputs, flags, outputs, verification) is purely operational and assumes Claude's competence.

5 / 5

Actionability

Provides a complete copy-paste-ready command, a concrete flags table, and specific verification steps (ffprobe, ok:true check), but `--voice` is left as "Provider-specific voice" without an example value.

4 / 5

Workflow Clarity

Single-stage skill with a dedicated Verification section containing explicit checkpoints (ok:true, non-zero file size, ffprobe duration); lacks an explicit error-recovery feedback loop, keeping it just below a 5.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and no need for local bundle files; the single one-level-deep pointer to cli-contract.md for the JSON/error contract is clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

87%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 concise, well-targeted description that clearly states both the capability and its trigger conditions. It earns top marks on completeness and distinctiveness, with only minor gaps in action coverage and trigger-term synonyms.

DimensionReasoningScore

Specificity

Names several concrete actions — "TTS audio creation", "optional dubbed video generation", "generating target-language dubbing" from "SRT subtitles" — but stops short of comprehensive coverage of the full dubbing workflow.

4 / 5

Completeness

Explicitly answers both what (TTS audio creation + optional dubbed video from SRT) and when ("Use when generating target-language dubbing...") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural user terms like "dubbing", "TTS audio", "dubbed video", "SRT subtitles", and "KrillinAI", but misses common synonyms such as "text-to-speech" and the explicit ".srt" extension.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (KrillinAI CLI dubbing from SRT subtitles) with distinctive triggers, giving it minimal overlap with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
krillinai/KrillinAI
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.