assets/skills/marketing/video/SKILL.md
Plan and produce video content strategy including scripts, storyboards, and production specs. Use when user says "create video", "video content", "video script", "video strategy", "youtube content", "video plan".
npx skillsauth add phuthuycoding/moicle marketing-videoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Plan video content end-to-end: strategy, script, storyboard, production spec, publishing schedule.
brainstorm/marketing/marketing-contentSTRATEGY → SCRIPT → STORYBOARD → PRODUCTION → PUBLISH
Goal: lock the audience, goal, channels, and series plan.
Ask the user (skip what's already known):
| Field | Example | |-------|---------| | Primary goal (pick 1) | brand awareness / tutorial / lead gen / community / thought leadership | | Audience | "Senior backend engineers evaluating Postgres tooling" | | Channels (pick ≤3) | YouTube long / YouTube Shorts / TikTok / Reels / LinkedIn / X / Twitch | | Cadence | "1 long video / week + 3 shorts" | | Series concept | "From-zero series: build a SaaS in 10 episodes" | | Tone | "Casual, technical, no fluff" | | Existing assets | brand kit URL, prior videos, channel stats |
## Video Strategy: {brand}
- Goal: {one line}
- Audience: {one line}
- Channels: {list, with primary marked}
- Cadence: {long-form + shorts schedule}
- Series: {2-4 series, each with theme + episode count target}
- Brand: {voice, colors, logo lockup}
Goal: write a script that holds attention from frame 1.
HOOK (≤10 sec, ≤30 sec for long-form)
- one of: contrarian claim / surprising number / pain question / curiosity gap
INTRO (≤15 sec)
- what they'll get + why this person/channel
BODY
- one idea per segment, each ≤90 sec for long-form, ≤15 sec for shorts
- pattern interrupt every 30-45 sec (cut, b-roll, on-screen text)
PAYOFF
- the answer / the demo / the result
CTA (≤10 sec)
- one ask: subscribe, link, comment with X
| Type | Example | |------|---------| | Contrarian | "Everyone tells you to write tests first. Here's why I stopped." | | Number | "I shipped 47 features last quarter with 1 engineer. Here's how." | | Pain question | "Your DB is slow at 100k rows? That's a config issue, not a Postgres limit." | | Curiosity gap | "There's a feature in Go that nobody uses but it solves your timeout bug." |
| Format | Total | Hook | Body | CTA | |--------|-------|------|------|-----| | YouTube long | 8-15 min | 10-30 s | 7-13 min | 10-30 s | | YouTube Short / Reel / TikTok | 30-60 s | ≤3 s | 25-50 s | ≤5 s | | LinkedIn native | 1-3 min | ≤5 s | 50 s - 2 min 30 s | ≤10 s |
Goal: visual plan that the editor / camera-op can execute without asking questions.
| # | Time | Visual | Audio | Text overlay | Asset needed | |---|------|--------|-------|--------------|--------------| | 1 | 0:00-0:08 | Talking head, medium shot | Hook line | (none) | — | | 2 | 0:08-0:25 | Screen recording: IDE | VO | "Step 1: install" | terminal recording | | 3 | 0:25-0:40 | B-roll: server rack | VO | (none) | stock or own footage |
Goal: ship a production-ready file the publisher can upload without rework.
| Channel | Resolution | FPS | Codec | Max length | Notes | |---------|-----------|-----|-------|-----------|-------| | YouTube long | 1080p or 4K | 30 / 60 | H.264 | 12 h | Chapters required for >5 min | | YouTube Shorts | 1080×1920 | 30 / 60 | H.264 | 60 s | Vertical | | TikTok | 1080×1920 | 30 / 60 | H.264 | 10 min | Caption per scene | | Instagram Reels | 1080×1920 | 30 | H.264 | 90 s | First frame = thumbnail | | LinkedIn native | 1920×1080 / 1080×1080 | 30 | H.264 | 10 min | Captions burned in | | X (Twitter) | 1280×720+ | 30 / 60 | H.264 | 2 min 20 s | Add caption file |
Goal: get the video in front of the audience and measure.
?utm_source=youtube&utm_medium=video&utm_campaign={series}## Video Plan: {brand / series}
### Strategy
- Goal: {one line}
- Audience: {one line}
- Channels: {primary + secondary}
### Videos Planned (next 4 weeks)
| # | Title | Format | Channel | Status |
|---|-------|--------|---------|--------|
| 1 | ... | long | YouTube | scripted |
| 2 | ... | short | Reels + TikTok + Shorts | storyboard |
### Production Backlog
- {script ready, awaiting recording}
- {recording done, awaiting edit}
### Metrics
- Baseline → Target per video and per series
| When | Use |
|------|-----|
| Full marketing plan (logo + content + video) | /marketing |
| Need brand visuals first | /marketing-logo |
| Repurpose video → blog / threads | /marketing-content |
| Brainstorm video topics | brainstorm |
| Phase | Agent | Purpose |
|-------|-------|---------|
| STRATEGY | @docs-writer | Document the strategy brief |
| SCRIPT | @docs-writer | Draft and tighten scripts |
| STORYBOARD | @docs-writer | Scene descriptions |
| PRODUCTION | @devops | Tech specs + encoding |
| PUBLISH | @docs-writer | Channel adaptations + tracking |
development
Test-Driven Development workflow. Use when doing TDD, writing tests first, or when user says "tdd", "test first", "test driven", "red green refactor".
development
Thorough pull request review workflow with architecture compliance checks. Use when reviewing pull requests, checking code changes, or when user says "review pr", "check pr", "review code", "pr review", "review pull request".
development
Review local branch changes for architecture compliance, conventions, and code quality before pushing/PR. Stack-aware — detects the project stack and applies the matching rules. Use when user says "review changes", "review branch", "check branch", "check changes", "review my code", "review before pr".
testing
DDD architecture compliance review with automated checks and review loop. Use when user says "architect-review", "architecture review", "review architecture", "check architecture", "review ddd", "ddd review".