Usage guide / your own agent
Prepare your material, install the paid toolkit and copy these examples into your own agent. Review the storyboard, preview and final export.
Browse the samples, subscribe and paste the connection request into your agent. Approve its browser code, then start tasks using the included Skills. No individual Skill or template downloads.
Step 0 1
Use your own Claude Code or Codex account. Create a local project folder and collect a script, product notes or key numbers. State who will watch, the main message, target length and format.
Example prompt
Use the notes in launch-notes.md. Plan a 15-second, 16:9 product explainer for first-time visitors. The goal is to explain three benefits. Keep every number and source note unchanged. Show the storyboard before building.
Step 0 2
After payment, paste the connection request into your agent and approve the matching browser code. The nine Skills are connected together.
Check setup status →Step 0 3
Ask your connected agent to recommend a style. It shows the task direction, resource version, balance and exact quote. A standard new task costs 1,000 credits and requires your confirmation.
Example prompt
Recommend a style for this brief. Before any paid delivery, show the pack contents, version and exact credit cost. Wait for my confirmation. Use the same delivery receipt for retries.
Step 0 4
After task activation, your agent creates the source project locally and opens a browser preview. Check the wording, numbers, reading speed and representative frames. Materials and source files stay in the project you control.
Example prompt
Build the confirmed storyboard in this folder. Open the local browser preview. Check text overflow, missing assets and reading time before showing it to me.
Step 0 5
Name the scene and the exact change. Keep working in the existing project. Local edits and renders use no platform credits; changing to a different paid pack requires a new quote.
Example prompt
In scene 2, shorten the headline to six words and hold it for one extra second. Keep scene 1, the numbers and the existing style unchanged. Update the same project and show the preview again.
Step 0 6
Ask your agent to render locally and return both the MP4 and editable source folder. The installer checks resolution and duration with ffprobe. Inspect fonts and representative frames yourself before sharing. Node.js 22+, FFmpeg and your own agent access are required.
Example prompt
Render this project locally to MP4. Check the actual file’s resolution and duration, inspect the opening and closing frames, and give me the editable source folder together with the video. Report any failed check.
Make your first local video
If rendering fails, keep your source and inspect the error with your agent. Recover the same pack using its saved delivery receipt without another credit charge. Keep local copies of your material and project.