From rune
Generates marketing video plans: timed narration scripts, scene storyboards, shot lists, and asset checklists for product demos. Saves to marketing/video-plan.md.
npx claudepluginhub rune-kit/rune --plugin @rune/analyticsThis skill uses the workspace's default tool permissions.
Video content planning for product demos and marketing. Writes narration scripts with timing marks, creates scene-by-scene storyboards, defines shot lists, and lists required assets. Saves the complete production plan to a file. This skill creates PLANS for video production — not actual video files.
Use when the user wants to write a video script for a product demo, feature walkthrough, launch video, or social media video about a feature or product change
Generates 30-45 second promo video scripts and shot-by-shot storyboards from project PRD. Detects Remotion or Montage-tool for compatible configs.
Crafts scripts, storyboards, and messaging for explainer, testimonial, thought leadership, and product videos. Applies hook-problem-solution-proof-CTA framework with templates, tone checklists, and iteration tips.
Share bugs, ideas, or general feedback.
Video content planning for product demos and marketing. Writes narration scripts with timing marks, creates scene-by-scene storyboards, defines shot lists, and lists required assets. Saves the complete production plan to a file. This skill creates PLANS for video production — not actual video files.
marketing (L2): demo/explainer video scriptslaunch (L1): product demo videosNone — pure L3 utility.
Accept input from calling skill:
topic — what the video is about (e.g. "Rune plugin demo", "Feature X walkthrough")audience — who will watch (e.g. "developers", "non-technical founders", "existing users")duration — target length in seconds (e.g. 60, 120, 300)platform — where it will be published: youtube | twitter | tiktok | loom | internaloutput_path — where to save the plan (default: marketing/video-plan.md)Derive constraints from platform:
Write a narration script with timing marks:
Structure:
Format each section:
[00:00] HOOK
Narration: "..."
On screen: [what viewer sees]
[00:05] SETUP
Narration: "..."
On screen: [what viewer sees]
Create a scene-by-scene breakdown:
For each scene:
Example:
Scene 3: Live demo — install command
Duration: 12s
Visual: Terminal window, typed command "npm install -g @rune/cli", output scrolling
Narration: "Install in seconds with one command."
Transition: cut
Define exactly what needs to be recorded or shown:
Categorize by type:
Format:
Shot 1 — Screen recording
URL: https://myapp.com/dashboard
Action: Click "New Project" → fill form → click Create
Duration: ~8s
Shot 2 — Terminal
Command: npm install -g @rune/cli && rune init my-project
Expected output: [describe what should appear]
Duration: ~10s
List every asset required before recording can begin:
Use Write to save the complete video plan to marketing/video-plan.md (or the specified output_path):
# Video Plan: [topic]
- **Platform**: [platform]
- **Target Duration**: [duration]s
- **Audience**: [audience]
- **Created**: [date]
## Script
[full timestamped script from Step 2]
## Storyboard
[scene-by-scene breakdown from Step 3]
## Shot List
[all shots from Step 4]
## Assets Needed
[checklist from Step 5]
## Platform Notes
[constraints and tips for the target platform]
Then output a summary to the calling skill:
## Video Plan Created
- File: [output_path]
- Scenes: [count]
- Shots: [count]
- Estimated recording time: [n] minutes
- Assets to prepare: [count] items
### Next Steps
1. Prepare assets listed in the plan
2. Record shots in order from the shot list
3. Edit using the storyboard as reference
This skill creates PLANS for video production. Actual recording and editing must be done by a human or a dedicated screen recording tool.
Video Plan saved to marketing/video-plan.md with script, storyboard, shot list, assets checklist, and platform notes. Summary report with scene/shot counts and estimated recording time. See Step 6 Report above for full template.
Known failure modes for this skill. Check these before declaring done.
| Failure Mode | Severity | Mitigation |
|---|---|---|
| Platform constraints not applied (e.g., Twitter max 140s exceeded) | HIGH | Step 1: derive constraints from platform immediately — they constrain everything downstream |
| Missing CTA section in script | MEDIUM | CTA (last 10s) is required in every script — no exceptions regardless of duration |
| Not saving to file (only verbal output) | HIGH | Constraint 3 + Step 6: Write to output_path is mandatory — verbal only = no persistence |
| Promising an actual deliverable video file | MEDIUM | Note explicitly: this skill creates a PLAN — actual recording is done by a human |
~500-1500 tokens input, ~500-1000 tokens output. Sonnet for script quality.