CtrlK
BlogDocsLog inGet started
Tessl Logo

krillinai-pipeline

Use when planning multi-stage KrillinAI CLI workflows such as subtitle plus TTS plus horizontal or vertical render; current pipeline execution is a reserved/planned surface unless implementation is wired in.

62

Quality

72%

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 ./skills/krillinai-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-3

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

The body is well-structured with strong verification and recovery loops, but mild redundancy and an unrunnable-as-documented headline command slightly undercut conciseness and actionability.

Suggestions

State the 'prefer individual commands' guidance once (in either the intro or 'When To Use Pipeline') instead of repeating it in both sections.

Show '--workdir' in the Command example since recovery depends on it, and clarify which outputs the current CLI actually executes versus only plans so the headline command is unambiguously runnable.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the 'prefer individual commands for real work' guidance is duplicated in both the intro and the 'When To Use Pipeline' section, a clear tightening opportunity.

2 / 3

Actionability

A concrete copy-paste command and specific recovery/verification steps are provided, but the skill itself flags the headline command may return 'unsupported_command' and '--workdir' (relied on by recovery) is not shown in the command example.

2 / 3

Workflow Clarity

Explicit Verification checkpoints (confirm stdout JSON success, confirm manifest stages, inspect final files) plus Recovery feedback loops (rerun only render with the same --workdir, read the manifest before rerunning) cover this batch-style pipeline.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections and a single clearly-signaled one-level reference (skills/krillinai-cli/references/cli-contract.md); no bundle files are present to require deeper structuring.

3 / 3

Total

10

/

12

Passed

Description

75%Weight 40%Scale 1-3

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 has an explicit 'Use when' trigger and a distinct, well-scoped niche, but its action list is framed as non-comprehensive examples and its trigger-term coverage omits common variants like dubbing and bilingual.

Suggestions

Replace the 'such as' framing with a direct, comprehensive action-verb list (e.g., 'Generate subtitles, generate TTS dubbing, render horizontal/vertical bilingual or dubbed video') to strengthen specificity.

Add common user-facing terms like 'dubbing', 'bilingual', 'transcribe', and 'translate' alongside 'subtitle' and 'TTS' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the KrillinAI pipeline domain and lists concrete outputs ('subtitle plus TTS plus horizontal or vertical render'), but the 'such as' framing under a single abstract verb ('planning') signals a non-comprehensive example list rather than a direct action-verb enumeration.

2 / 3

Completeness

Opens with an explicit 'Use when planning multi-stage KrillinAI CLI workflows...' trigger and states what the skill does, clearly answering both what and when.

3 / 3

Trigger Term Quality

Natural terms a user would say are present (subtitle, TTS, render, horizontal/vertical), but common variations the body itself uses (dubbing, bilingual, transcribe, translate) are missing.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (KrillinAI multi-stage pipeline) with distinct triggers (subtitle, TTS, render) unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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.