Install
$ agentstack add skill-vibeknow-cli-vibeknow-create ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
vibeknow-create
TRIGGER
- User wants to generate a video from a document, URL, or file
- Check video task status or wait for completion
- Download a rendered video
- List available voice templates
SKIP
- Document upload/status only (no video) → use vibeknow-doc
- Auth, profile, config, diagnostics → use vibeknow-core
Core Concepts
- Hero command:
vibeknow create --fromresolves input → uploads if needed → submits to figlens pipeline → streams progress → returns video URL. - --from accepts 3 input types:
doc_id(used directly), URL (auto-uploaded to vectoria), local file path (auto-uploaded). - Sync vs async: Default is sync (blocks until done).
--asyncreturns taskid + sessionid immediately. - NDJSON event stream:
--output ndjsonemits structured progress events (schema_version: "1"). See [events.md](references/events.md). - 6 pipeline stages:
parse→outline→storyboard→tts→render→publish. - session_id: All
videosubcommands require both `and--session-id. These are returned bycreate`.
Quick Reference
| Command | Description | |---------|-------------| | vibeknow create --from | Generate a video (sync by default) | | vibeknow video status --session-id | Get task status | | vibeknow video wait --session-id | Stream progress, block until done | | vibeknow video download --session-id | Download rendered video | | vibeknow voice list | List available voice templates |
For full flags and output examples, see [commands.md](references/commands.md).
Common Tasks
Generate a video (sync, simplest path)
vibeknow create --from slides.pdf
# Blocks until done, prints video URL
Generate with specific voice
vibeknow voice list # find voice ID
vibeknow create --from slides.pdf --voice v_warm_female
Async submit, then follow up
# Submit and exit immediately
vibeknow create --from https://example.com/doc --async
# Output: task_id=t_xxx session_id=s_yyy
# Later: check status
vibeknow video status t_xxx --session-id s_yyy
# Or: wait for completion
vibeknow video wait t_xxx --session-id s_yyy
Agent mode (NDJSON streaming)
vibeknow create --from doc_abc --output ndjson
# Each line is a JSON event: task.submitted, stage.started, stage.progress, ...
# Terminal event: task.succeeded (with video_url) or task.failed
Download the result
vibeknow video download t_xxx --session-id s_yyy
# Default output: .mp4
vibeknow video download t_xxx --session-id s_yyy --output ./my-video.mp4
vibeknow video download t_xxx --session-id s_yyy --output ./my-video.mp4 --overwrite
Exit Code Handling
| Exit | Meaning | Agent Action | |------|---------|--------------| | 0 | Success | Extract video_url from output | | 1 | General error | Read stderr | | 2 | Invalid arguments | Fix command syntax | | 3 | Auth error | Run vibeknow auth status to inspect credential source. Re-login with vibeknow auth login (interactive) or set VIBEKNOW_TOKEN. See vibeknow-core for profile/diagnostics if installed. | | 4 | Task failed, retryable | Re-submit the same create command | | 5 | Task failed, not retryable | Report error to user, do not retry | | 6 | Stream interrupted, task status unknown | vibeknow video wait --session-id to reconnect. Do NOT re-submit. | | 130 | User interrupt (SIGINT) | — |
For detailed error handling and recovery, see [errors.md](references/errors.md) and [recipes.md](references/recipes.md).
NDJSON Event Summary
Events share common fields: schema_version, ts, type.
Key events (pipeline engine):
| Event | Extra Fields | Meaning | |-------|-------------|---------| | node.started | stage, node, message | Pipeline node begins | | node.succeeded | stage, node, message | Node done | | node.failed | stage, node, message | Node failed (not necessarily terminal — wait for task.failed) | | task.succeeded | session_id, video_url, duration_ms | Terminal: video ready | | task.failed | code, message, retryable | Terminal: task failed (retryable=true → exit 4, false → exit 5) |
Agent engine (--engine agent) replaces node.started/succeeded/failed with node.progress carrying status + message, and omits duration_ms from task.succeeded.
See [events.md](references/events.md) for the complete field reference, engine differences, and parsing examples.
References
- [commands.md](references/commands.md) — Full flag reference for all commands
- [events.md](references/events.md) — NDJSON task event schema
- [errors.md](references/errors.md) — Exit codes, error codes, Error Object schema
- [recipes.md](references/recipes.md) — Advanced: retry, recovery, batch, NDJSON parsing
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: vibeknow
- Source: vibeknow/cli
- License: MIT
- Homepage: https://vibeknow.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.