krillinai/OpenCreator / skills/krillinai-pipeline
krillinai-pipeline
VerifiedUse when validating or documenting a multi-stage KrillinAI CLI output plan; the current pipeline command supports dry-run planning only, not end-to-end execution.
KrillinAI Pipeline
Use this skill to validate a requested stage plan. Run real work through the individual stage commands because non-dry-run pipeline execution returns unsupported_command.
Plan Validation
(cd "$KRILLINAI_CWD" && "$KRILLINAI_CLI" pipeline \
--outputs "subtitle,tts,vertical-bilingual" \
--dry-run)
Outputs Values
| Output | Stage |
|---|---|
subtitle | Generate subtitle files |
tts | Generate dubbing |
horizontal-bilingual | Render landscape bilingual video |
horizontal-dubbed | Render landscape dubbed video |
vertical-bilingual | Render portrait bilingual video |
vertical-dubbed | Render portrait dubbed video |
cover | Generate cover |
The dry-run validates output names and returns a successful pipeline-stage JSON response. It does not execute stages or write a task manifest.
Execute The Plan
Map the validated outputs to subtitle, tts, render-horizontal, render-vertical, and cover. Run each required command independently and use the same absolute --workdir.
Recovery Strategy
- If
subtitlesucceeds and render fails, rerun only render with the same--workdir. - If TTS fails, keep subtitle outputs and rerun
ttsafter fixing provider config. - Read
krillinai_manifest.jsonbefore rerunning to avoid repeating expensive work.
Verification
- Require terminal JSON with
"ok": truefor dry-run validation. - For real work, confirm every independently executed stage succeeded.
- Confirm manifest stages and requested output files, not just the plan response.
- Inspect final requested media/cover files, not only intermediate outputs.
- For shared CLI details, read
skills/krillinai-cli/references/cli-contract.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |