krillinai/opencreator

krillinai-pipeline

Use 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.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/krillinai/opencreator --skill krillinai-pipeline

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

bash
(cd "$KRILLINAI_CWD" && "$KRILLINAI_CLI" pipeline \
  --outputs "subtitle,tts,vertical-bilingual" \
  --dry-run)

Outputs Values

OutputStage
subtitleGenerate subtitle files
ttsGenerate dubbing
horizontal-bilingualRender landscape bilingual video
horizontal-dubbedRender landscape dubbed video
vertical-bilingualRender portrait bilingual video
vertical-dubbedRender portrait dubbed video
coverGenerate 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 subtitle succeeds and render fails, rerun only render with the same --workdir.
  • If TTS fails, keep subtitle outputs and rerun tts after fixing provider config.
  • Read krillinai_manifest.json before rerunning to avoid repeating expensive work.

Verification

  • Require terminal JSON with "ok": true for 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.