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.
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
connect the user's own KPainter account and API key
help the user choose the right output type
Verwandte Skills
collect only the missing information needed to create or refine the result
stay in normal user language unless the user asks for technical details
Setup
If KPainter is not connected yet, guide setup before trying to create content.
Ask whether the user already has a KPainter account.
If not, tell the user to sign up or sign in at https://kpainter.ai/.
Send the user to https://kpainter.ai/api-key.
Ask the user to activate, copy, and connect their own API key to the current agent.
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
Knowledge Video
Knowledge Video (Slides)
Vector Animation
Slides
Image
Web App
How the agent should choose the output type
Always route by the result the user wants first.
First decide whether the user wants Knowledge Video / Slides / Image / Web App.
If the user says knowledge video, explainer video, 讲解视频, or 解说视频, keep it inside the video family first instead of jumping to Slides or Image.
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.
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
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.
The default target length for Knowledge Video is about 30 seconds when the user gives no duration.
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:
make a knowledge video
make an explainer video
make a narrated explainer
帮我做一个讲解视频
帮我做一个解说视频
做一个知识视频把这件事讲清楚
Knowledge Video
Prefer Knowledge Video for requests like:
make a knowledge video
make it more polished
make it more story-led
make it more social-friendly
make it feel like a finished short video
make a narrated explainer video
做一个更像成片的讲解视频
做一个更适合传播的解说视频
Knowledge Video (Slides)
Prefer Knowledge Video (Slides) for requests like:
illustrated
static
PPT-style video
PPT video
slide-based video
slide-like
explain this step by step
classroom explainer
training explainer
图解版
PPT视频
课件视频
分步骤讲解
Vector Animation
Prefer Vector Animation for requests like:
vector animation
flow animation
mechanism animation
architecture animation
animate this process or principle
用动画讲这个流程
用动画讲这个机制
Slides
Trigger on phrases like slides, PPT, slide deck, deck, presentation materials.
Image
Trigger on phrases like image, poster, cover, cover image, visual summary.
Web App
Trigger on phrases like app, web app, interactive page, interactive demo, learning 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:
Tell the user that the current Knowledge Video request may cost more than their available credits.
Offer Knowledge Video (Slides) as the lower-cost alternative.
Ask for confirmation instead of silently switching formats.
Good fallback phrasing:
You may not have enough credits for a full Knowledge Video right now. I can switch this to Knowledge Video (Slides), which is usually cheaper. Do you want me to do that?
Your current credits may be a better fit for Knowledge Video (Slides). If you want, I can keep the same topic and switch only the format.
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
Ask one follow-up at a time.
Keep questions short and concrete.
Use normal language instead of technical labels whenever possible.
Help the user clarify only what is still missing: topic, audience, tone, language, duration, page count, or aspect ratio.
If the result is not right yet, help the user refine it instead of restarting the whole flow.
Do not silently change the output type, audience, language, or format.
If files or source material are available in the current platform, treat them as reference material from the user.
Minimal information to collect
Only ask for what is still missing:
topic
audience
language
duration or page count
tone or visual direction
source files or reference material
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
Explain what MCP is as a knowledge video
Make a knowledge video for new product managers about AI agents
Make a knowledge video around 30 seconds that explains MCP clearly
Make an explainer video that walks through MCP
帮我做一个讲解视频，把 MCP 讲清楚
帮我做一个解说视频，适合发在社媒上
Knowledge Video (Slides)
Make a knowledge video (slides) that explains this step by step
做一个 PPT 视频，分步骤讲解 MCP
做一个课件视频，给新员工培训用
Vector Animation
Create a vector-style animation that explains how attention works
用矢量动画讲清楚这个机制
Slides
Create an onboarding deck about MCP
Make a teaching slide deck about prompt engineering
Image
Create a course cover image about MCP
Make a social poster about prompt engineering
Web App
Build an interactive page that explains the MCP flow
Create a small learning app about attention
Refinement examples
After the first result, the user may say things like:
make it shorter
make it more polished
switch it to Knowledge Video (Slides)
switch it to vector animation
keep it as an explainer video but make it feel more like a finished short video
keep the same topic but change the tone
make it more suitable for classroom use
Install options
OpenClaw / ClawHub
Install this skill natively in OpenClaw with:
openclaw skills install kpainter
Publish 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:
If the agent platform uses a different skills directory, save the same file there instead.
Where to read more
https://kpainter.ai/docs/skills
https://kpainter.ai/docs/openapi
https://kpainter.ai/api-key
Security rules
the API key belongs to the user
the agent should not ask the user to share the key with unrelated services
the agent should not present itself as the KPainter account owner
if the user resets the key, the agent should ask the user to reconnect it
Update guidance
If KPainter skills stop working or the user changes keys, the agent should:
reread this file or refresh the local skill
ask the user to reconnect the latest API key
confirm the available output types again
ask what the user wants to create now
Success state
The setup is successful when the agent can:
guide the user through account and API key setup
explain the available output types in simple language
choose the right video style when the request is ambiguous, including 讲解视频 / 解说视频 / PPT视频 style requests, without treating bare video as an automatic Knowledge Video trigger