🎬 Video Script & Storyboard
Turns an existing article, product page or idea into a hook, script and shot-by-shot storyboard.
Who it's for
Short-video creators, small marketing teams.
Article URL, product page or key selling points.
Hook variants, script with timings, storyboard table sized for Shorts / Reels / TikTok.
Output preview
Task given to the agent: “Turn the blog post in article.md into a 45-second Short script with a storyboard.”
**45-second Short — “Imported an n8n workflow? You’re not done yet.”** **Format:** Vertical screen recording with voiceover. ~105 spoken words; allow brief pauses for clicks. | Time | Voiceover | Storyboard / on-screen text | |---|---|---| | 0–4s | “Imported an n8n workflow? It’s not ready to run just yet.” | Show a workflow canvas with warning icons. **“Imported ≠ ready”** | | 4–9s | “First, inspect the JSON for authentication headers or sensitive details.” | Show JSON in a text editor. Highlight a dummy authentication header. **“1. Check the file”** | | 9–15s | “Open a new workflow, then choose Import from File in the Workflow menu.” | Record the menu selection and the workflow appearing. **“2. Import JSON”** | | 15–21s | “Open warning nodes and connect your own credentials for each service.” | Open a warning node; select a credential. Keep secrets hidden. **“3. Connect your accounts”** | | 21–28s | “Replace the author’s URLs, spreadsheet IDs, recipients, and schedule times with yours.” | Quick cuts through the relevant node fields. **“4. Make it yours”** | | 28–34s | “Click Execute workflow. Check each node’s output and fix any failures.” | Click Execute workflow; inspect successful node outputs. **“5. Test every step”** | | 34–41s | “Then click Publish and wait for confirmation. Autosaved edits stay drafts until published.” | Show Publish, the confirmation dialog, then the successful status. **“6. Publish to go live”** | | 41–45s | “Practise with our free Weekly Uptime Check flow.” | End card: **“Try Weekly Uptime Check”** with **“Link in description”**. |
# How to import and configure an n8n workflow from JSON Core idea: Import a workflow JSON, swap in your credentials and settings, test it once, then publish it live. · Length: 45 s · Format: 9:16 · Voiceover words: 116 ## Hook options 1. Got a workflow JSON? Here’s how to use it. 2. Import an n8n workflow in five quick steps. 3. Before you hit publish, do this first. ## Script Got a workflow JSON? Here’s how to use it. n8n stores workflows as JSON, so shared workflows usually arrive as one .json file. Before you import, open it and check for credential names, IDs, or headers you don’t want to share. Then import it from a file, from a URL, or by pasting the JSON straight into n8n. Next, connect your own credentials, replace any original URLs, IDs, recipients, or schedule times, and test the workflow once. When everything works, publish it. That makes schedules run, webhooks switch to production URLs, and connected apps trigger the workflow live. Try a free flow first if you want a quick practice run. ## Storyboard | # | Time | Visual | Voiceover | On-screen text | |---|---|---|---|---| | 1 | 0–3 s | Fast cut: JSON file opens, n8n canvas appears | Got a workflow JSON? Here’s how to use it. | Workflow JSON? | | 2 | 3–8 s | Close-up on file editor highlighting credentials and headers | n8n stores workflows as JSON, so shared workflows usually arrive as one .json file. | Check the file first | | 3 | 8–13 s | Highlight import menu options in n8n | Before you import, open it and check for credential names, IDs, or headers you don’t want to share. | Look for sensitive data …
Show full output
# How to import and configure an n8n workflow from JSON Core idea: Import a workflow JSON, swap in your credentials and settings, test it once, then publish it live. · Length: 45 s · Format: 9:16 · Voiceover words: 116 ## Hook options 1. Got a workflow JSON? Here’s how to use it. 2. Import an n8n workflow in five quick steps. 3. Before you hit publish, do this first. ## Script Got a workflow JSON? Here’s how to use it. n8n stores workflows as JSON, so shared workflows usually arrive as one .json file. Before you import, open it and check for credential names, IDs, or headers you don’t want to share. Then import it from a file, from a URL, or by pasting the JSON straight into n8n. Next, connect your own credentials, replace any original URLs, IDs, recipients, or schedule times, and test the workflow once. When everything works, publish it. That makes schedules run, webhooks switch to production URLs, and connected apps trigger the workflow live. Try a free flow first if you want a quick practice run. ## Storyboard | # | Time | Visual | Voiceover | On-screen text | |---|---|---|---|---| | 1 | 0–3 s | Fast cut: JSON file opens, n8n canvas appears | Got a workflow JSON? Here’s how to use it. | Workflow JSON? | | 2 | 3–8 s | Close-up on file editor highlighting credentials and headers | n8n stores workflows as JSON, so shared workflows usually arrive as one .json file. | Check the file first | | 3 | 8–13 s | Highlight import menu options in n8n | Before you import, open it and check for credential names, IDs, or headers you don’t want to share. | Look for sensitive data | | 4 | 13–19 s | Menu shows file, URL, and paste options | Then import it from a file, from a URL, or by pasting the JSON straight into n8n. | Import three ways | | 5 | 19–27 s | Warning icons on nodes, credential dropdowns, settings fields changing | Next, connect your own credentials, replace any original URLs, IDs, recipients, or schedule times, and test the workflow once. | Swap in your settings | | 6 | 27–35 s | Manual run executes nodes successfully | Next, connect your own credentials, replace any original URLs, IDs, recipients, or schedule times, and test the workflow once. | Test before publishing | | 7 | 35–42 s | Publish button clicked, workflow goes live | When everything works, publish it. That makes schedules run, webhooks switch to production URLs, and connected apps trigger the workflow live. | Publish to go live | | 8 | 42–45 s | Quick end card with a practice workflow example | Try a free flow first if you want a quick practice run. | Practice first | ## Notes - Facts used from the source: n8n workflows are stored as JSON; import options include file, URL, and paste; imported workflows need your own credentials and settings; testing uses Execute workflow; publishing makes schedules, webhooks, and connected apps go live.
Real, unedited output from recorded runs on Oct 18, 2026 · Codex (codex-cli 0.163.0) · model gpt-5.4-mini (baseline run used model gpt-6.1-sol). Test inputs are fixtures (fictional brand, example.com links). AI output can be wrong: check facts before you publish anything like it.
What's in the pack
video-script-storyboard/references/hooks.mdvideo-script-storyboard/SKILL.md
Install
Unzip first. You get a folder named video-script-storyboard containing SKILL.md. Put it in your tool's skills folder:
- Claude Code
~/.claude/skills/video-script-storyboard/ - Codex
~/.agents/skills/video-script-storyboard/ - Cursor
~/.cursor/skills/video-script-storyboard/ - Claude.ai Customize → Skills → + → Create skill → Upload a skill, then pick the ZIP (code execution must be on).
Step-by-step install guide. Only the tools listed under “Works with → tested” have passed a recorded run.
Trigger test pack
- "Turn this blog post into a 45-second Short script"
- "Storyboard a Reel for this product page"
- "Write a 2,000-word article"
- "Check my site speed"
Acceptance checks
- Hook lands in the first 3 seconds
- Script fits the target length
- Every shot has visual + audio + on-screen text
Each acceptance check is run automatically on every recorded test. See the test log below.
Security label
| Scripts | None |
| Network calls | None by the skill itself |
| Credentials | None |
| Writes files | Writes the script file |
| Remote instructions | Never — everything is in the pack |
| Pack contents | Text files only, no executable code (checked at build) |
Works with
Dependencies & cost: Your AI agent subscription only.
Known limitations
- Does not generate the video itself
Pairs with an n8n flow
⚡ New blog post → short-video scriptRSS · AI agent · Google Docs · setup ~20 minVersion log
| v0.1.0 | First release. Passed its first recorded test on Oct 18, 2026. |
Test log
| Date (UTC) | Tool | Model | Run | Result | Checks | Tokens in / out |
|---|---|---|---|---|---|---|
| Oct 18, 2026 | Codex | gpt-5.4-mini | Test | Passed | 11/11
| 53,181 / 1,148 |
| Oct 18, 2026 | Codex | gpt-6.1-sol | Test | Passed | 11/11
| 77,398 / 1,986 |
| Oct 18, 2026 | Codex | gpt-6.1-sol | Baseline (no skill) | Comparison only | 3/10
| 41,758 / 566 |
| Oct 18, 2026 | Codex | gpt-6.1-sol | Test | Failed | 10/11
| 96,196 / 2,375 |
Each row is a real run recorded by our test runner. For each tool, the latest test run decides whether it appears under “Tested on”. Baseline runs do the same task with no skill installed and never count.