KPainter Skill
name: kpainter
by bbgasj · published 2026-04-01
$ claw add gh:bbgasj/bbgasj-kpainter---
name: kpainter
description: KPainter specializes in controllable knowledge video generation and turns one prompt into knowledge videos, slides (PPT), and interactive apps. Built for explainers, courseware, social content, bedtime stories, product marketing, and work presentations, with stronger structure, pacing, and detail control than generic video generators.
metadata:
version: "0.6.3"
homepage: https://kpainter.ai/
skill_url: https://kpainter.ai/skill.md
docs_url: https://kpainter.ai/docs/skills
openapi_docs_url: https://kpainter.ai/docs/openapi
api_key_url: https://kpainter.ai/api-key
---
# KPainter Skill
Use this skill when an agent should help a user turn one prompt into a KPainter knowledge video, slides, image, or interactive app, especially when controllability, structure, and knowledge delivery matter more than generic video generation.
Official URLs
| Resource | URL |
| --- | --- |
| Homepage | `https://kpainter.ai/` |
| Skill file | `https://kpainter.ai/skill.md` |
| Skills docs | `https://kpainter.ai/docs/skills` |
| OpenAPI docs | `https://kpainter.ai/docs/openapi` |
| API Key | `https://kpainter.ai/api-key` |
Primary goals
Setup
If KPainter is not connected yet, guide setup before trying to create content.
1. Ask whether the user already has a KPainter account.
2. If not, tell the user to sign up or sign in at `https://kpainter.ai/`.
3. Send the user to `https://kpainter.ai/api-key`.
4. Ask the user to activate, copy, and connect their own API key to the current agent.
5. Only say setup is complete after the user confirms the key is connected.
Do not ask the user to share their API key with unrelated services or outside the current agent connection flow.
What KPainter can create
How the agent should choose the output type
Always route by the result the user wants first.
1. First decide whether the user wants `Knowledge Video / Slides / Image / Web App`.
2. If the user says `knowledge video`, `explainer video`, `讲解视频`, or `解说视频`, keep it inside the video family first instead of jumping to Slides or Image.
3. If the user says only the broad word `video`, ask one short follow-up to clarify whether they want `Knowledge Video`, `Knowledge Video (Slides)`, or `Vector Animation`.
4. Then choose the video style inside that family:
- `Knowledge Video` for something polished, story-led, narrated, social-friendly, or closer to a finished short video
- `Knowledge Video (Slides)` for something illustrated, static, PPT-style, slide-based, classroom-friendly, training-friendly, or step by step
- `Vector Animation` for process, mechanism, structure, workflow, principle, science, math, or system explanation
5. If the request is still ambiguous inside the video family after that clarification, prefer `Knowledge Video (Slides)` as the safest default and offer to switch to the fuller `Knowledge Video` style later.
6. The default target length for `Knowledge Video` is about `30 seconds` when the user gives no duration.
7. Do not lead with internal API type names unless the user explicitly asks.
Trigger guidance
Video family
Treat requests like these as part of the video family first:
Knowledge Video
Prefer `Knowledge Video` for requests like:
Knowledge Video (Slides)
Prefer `Knowledge Video (Slides)` for requests like:
Vector Animation
Prefer `Vector Animation` for requests like:
Slides
Image
Web App
Credit fallback guidance
If the user wants `Knowledge Video` but does not have enough credits, the agent should proactively suggest `Knowledge Video (Slides)` as the cheaper fallback.
Recommended behavior:
1. Tell the user that the current Knowledge Video request may cost more than their available credits.
2. Offer `Knowledge Video (Slides)` as the lower-cost alternative.
3. Ask for confirmation instead of silently switching formats.
Good fallback phrasing:
When the user accepts, keep the same topic, audience, and language, and only switch the output format unless the user asks for other changes.
How the agent should talk to the user
Minimal information to collect
Only ask for what is still missing:
If the user already gave enough information, create first and refine after.
Multilingual support
KPainter supports creation and refinement workflows in the user's preferred language.
The user can describe the topic, audience, tone, and constraints in any language.
The agent should preserve the user's requested output language unless the user asks to switch.
If the intended output language is unclear, ask one short follow-up question before creating.
Multilingual examples
Examples only, not a language allowlist.
English
> Make a knowledge video that explains MCP clearly.
Chinese
> 帮我做一个讲清楚 MCP 的知识视频。
Japanese
> MCP をわかりやすく説明する知識動画を作ってください。
Arabic
> أنشئ فيديو معرفيًا يشرح MCP بشكل واضح.
Spanish
> Crea un video de conocimiento que explique MCP con claridad.
Korean
> MCP를 명확하게 설명하는 지식 영상을 만들어 주세요.
French
> Crée une vidéo de connaissance qui explique clairement le MCP.
Example user requests
Knowledge Video
Knowledge Video (Slides)
Vector Animation
Slides
Image
Web App
Refinement examples
After the first result, the user may say things like:
Install options
OpenClaw / ClawHub
Install this skill natively in OpenClaw with:
openclaw skills install kpainterPublish and registry workflows use ClawHub, while the runtime install path uses OpenClaw's native skills commands.
Skills CLI
Quick install while this repository contains one public skill:
npx skills add OriginwiseAI/skillsInstall this skill explicitly:
npx skills add OriginwiseAI/skills --skill kpainterInstall all skills in this repository explicitly:
npx skills add OriginwiseAI/skills --allYou can preview discovery before installing:
npx skills add OriginwiseAI/skills --listLegacy Bun command
For teams that still use the old package name, the legacy Bun command is:
bunx add-skill OriginwiseAI/skills
bunx add-skill OriginwiseAI/skills --skill kpainterPrefer `npx skills add` for new documentation and examples.
Direct URL
Give the agent this file directly:
`https://kpainter.ai/skill.md`
Local skill folder
For agents that support local skill folders, save this file as a local skill.
Example:
mkdir -p ~/.codex/skills/kpainter
curl -s https://kpainter.ai/skill.md > ~/.codex/skills/kpainter/SKILL.mdIf the agent platform uses a different skills directory, save the same file there instead.
Where to read more
Security rules
Update guidance
If KPainter skills stop working or the user changes keys, the agent should:
1. reread this file or refresh the local skill
2. ask the user to reconnect the latest API key
3. confirm the available output types again
4. ask what the user wants to create now
Success state
The setup is successful when the agent can:
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...