Krillinai Cli logo

Krillinai Cli

CommunityPopular
krillinai
krillinai-cli

Use when an agent needs to build or operate the embedded KrillinAI CLI, choose a supported command, or interpret its JSON, manifest, subtitle, dubbing, render, cover, speech, and voice outputs.

Overview

Publisherkrillinai
RepositoryOpenCreator
Skill namekrillinai-cli
Stars
12.6K
Forks
1.3K
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by krillinai on GitHub. Read the source before you install it.

Installation

Install the Krillinai Cli AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/krillinai/OpenCreator/tree/master/skills/krillinai-cli
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/krillinai/OpenCreator.git /tmp/OpenCreator
mkdir -p .claude/skills
cp -r /tmp/OpenCreator/skills/krillinai-cli .claude/skills/krillinai-cli
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Krillinai Cli in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Krillinai Cli on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Krillinai Cli is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

KrillinAI CLI

Use this as the top-level routing skill for KrillinAI command-line work.

Build And Locate The Binary

Build both KrillinAI binaries through the repository script:

bash
pnpm krillinai:build

For the current machine, locate the CLI without assuming a platform or architecture:

bash
TARGET="$(node -p "process.platform + '-' + process.arch")"
SUFFIX="$(node -p "process.platform === 'win32' ? '.exe' : ''")"
KRILLINAI_CLI="$PWD/.runtime/build/krillinai/$TARGET/bin/krillinai-cli$SUFFIX"
test -f "$KRILLINAI_CLI"

The CLI loads config/config.toml relative to its process working directory. For real runs from a source checkout, use runtime/krillinai as the process working directory and create its ignored config/config.toml from config/config-example.toml without overwriting an existing file. A release archive should be run from its unpacked package root.

For build layout, configuration, JSON, manifest, output, and error details, read:

text
skills/krillinai-cli/references/cli-contract.md

Choose The Command

User intentCommand / skill
Generate source, target, bilingual, and short vertical subtitlessubtitle; use krillinai-subtitle
Generate target-language dubbing from subtitlestts; use krillinai-tts
Create landscape videosrender-horizontal; use krillinai-render-horizontal
Create portrait/short-form videosrender-vertical; use krillinai-render-vertical
Generate a cover from a complete image promptcover; use krillinai-cover
Generate speech from plain textspeech
List provider voice codes for Aliyun, OpenAI, or MiniMaxvoices
Validate a requested multi-stage output planpipeline --dry-run; use krillinai-pipeline

pipeline only validates plans in dry-run mode; non-dry-run execution returns unsupported_command. status is reserved and unsupported.

Operating Rules For Agents

  • Use a dedicated --workdir; do not scatter outputs in the repo root.
  • Use --dry-run for command-shape validation before external calls.
  • Parse stdout as JSON lines. The terminal response is the object containing ok; OpenCreator mode may emit progress frames first.
  • Treat krillinai_manifest.json and actual output files as the source of truth after a real stage.
  • Reuse manifest outputs for later stages instead of guessing filenames.
  • If a command fails, classify by error.kind: usage, retryable, dependency, or internal.
  • Avoid rerunning expensive stages if the manifest already has valid upstream outputs.
  • Do not claim that cover consumed a reference image: the current CLI accepts a complete text prompt and size only.
  • Do not request an Edge TTS voice catalog: voices currently supports aliyun, openai, and minimax.

Minimal Workflow

bash
REPO_ROOT="$PWD"
WORKDIR="$REPO_ROOT/tasks/demo"
mkdir -p "$WORKDIR"

(cd "$REPO_ROOT/runtime/krillinai" && "$KRILLINAI_CLI" subtitle \
  "https://www.youtube.com/watch?v=VIDEO_ID" \
  --origin-lang en \
  --target-lang zh_cn \
  --workdir "$WORKDIR" \
  --caption-source any \
  --prepare-video)

(cd "$REPO_ROOT/runtime/krillinai" && "$KRILLINAI_CLI" render-vertical \
  --workdir "$WORKDIR")

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Krillinai Cli AI skill do?

Use when an agent needs to build or operate the embedded KrillinAI CLI, choose a supported command, or interpret its JSON, manifest, subtitle, dubbing, render, cover, speech, and voice outputs.

Why use Krillinai Cli on TypingMind?

Because you install it once and use it with any model. Krillinai Cli is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Krillinai Cli in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/krillinai/OpenCreator/tree/master/skills/krillinai-cli. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Krillinai Cli?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Krillinai Cli?

As many as you like. As long as a model supports skills, you can use Krillinai Cli with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Krillinai Cli AI skill free?

Yes. It is published on GitHub by krillinai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇