$npx -y skills add sendaifun/solana-new --skill marketing-videoCreate marketing videos for Solana projects using Remotion (code-driven) and Renoise (AI-generated). Use when a user says "marketing video", "product video", "promo video", "deck review", "video pitch", "create a video", or "Remotion project".
| 1 | ## Preamble (run first) |
| 2 | |
| 3 | ```bash |
| 4 | _TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier": *"[^"]*"' | head -1 | sed 's/.*"telemetryTier": *"//;s/"$//' || echo "anonymous") |
| 5 | _TEL_TIER="${_TEL_TIER:-anonymous}" |
| 6 | _TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" || echo "no") |
| 7 | _TEL_START=$(date +%s) |
| 8 | _SESSION_ID="$$-$(date +%s)" |
| 9 | mkdir -p ~/.superstack |
| 10 | echo "TELEMETRY: $_TEL_TIER" |
| 11 | echo "TEL_PROMPTED: $_TEL_PROMPTED" |
| 12 | if [ "$_TEL_TIER" != "off" ]; then |
| 13 | _TEL_EVENT='{"skill":"marketing-video","phase":"launch","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' |
| 14 | echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null || true |
| 15 | _CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"convexUrl":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "") |
| 16 | [ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"marketing-video","phase":"launch","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 & |
| 17 | true |
| 18 | fi |
| 19 | ``` |
| 20 | |
| 21 | If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry. |
| 22 | Use AskUserQuestion: |
| 23 | |
| 24 | > Help superstack get better! We track which skills get used and how long they take — |
| 25 | > no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`. |
| 26 | |
| 27 | Options: |
| 28 | - A) Sure, help superstack improve (anonymous) |
| 29 | - B) No thanks |
| 30 | |
| 31 | If A: run this bash: |
| 32 | ```bash |
| 33 | echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json |
| 34 | _TEL_TIER="anonymous" |
| 35 | touch ~/.superstack/.telemetry-prompted |
| 36 | ``` |
| 37 | |
| 38 | If B: run this bash: |
| 39 | ```bash |
| 40 | echo '{"telemetryTier":"off"}' > ~/.superstack/config.json |
| 41 | _TEL_TIER="off" |
| 42 | touch ~/.superstack/.telemetry-prompted |
| 43 | ``` |
| 44 | |
| 45 | This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow. |
| 46 | |
| 47 | > **Wrong skill?** See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills. |
| 48 | |
| 49 | # Marketing Video — Remotion + Renoise |
| 50 | |
| 51 | Create marketing videos for your Solana project using two complementary approaches: |
| 52 | - **Remotion** (code-driven): Programmatic React videos — full control, reproducible, version-controlled. Uses the [official Remotion skills](https://github.com/remotion-dev/skills) (38 rule modules). |
| 53 | - **Renoise** (AI-generated): AI video generation — fast, creative, no code needed |
| 54 | |
| 55 | **Goal: Professional quality that doesn't look AI-generated.** Read [references/professional-quality-guide.md](references/professional-quality-guide.md) before starting any Remotion work. |
| 56 | |
| 57 | ## When to Use |
| 58 | |
| 59 | - `/marketing-video` — Full video production workflow |
| 60 | - `/deck-review` — Convert pitch deck into video format |
| 61 | - "Create a marketing video for my Solana project" |
| 62 | - "Make a product demo video" |
| 63 | - "Turn my pitch deck into a video" |
| 64 | - "Create a social media promo" |
| 65 | - "Make a TikTok for my dApp" |
| 66 | |
| 67 | ## Non-Negotiables |
| 68 | |
| 69 | - **Never skip the interview.** Don't guess the product, the audience, or the visual direction. Ask. |
| 70 | - **Never ask about animation technicalities.** The user doesn't care about spring configs or TransitionSeries. Ask about their product, their story, their taste. |
| 71 | - **Stay opinionated.** If the user's idea for a video is weak (too long, wrong audience, no hook), say so plainly and redirect. |
| 72 | - **Visual taste first, code second.** Establish what the video should FEEL like before writing a single line of Remotion. |
| 73 | - **Gather elements proactively.** Ask for screenshots, logos, brand colors. If they don't have them, source SVG icons (Lucide, Heroicons), generate color palettes, and suggest illustration styles. |
| 74 | - **One-stop shop.** This skill handles everything: interview → concept → storyboard → element gathering → scaffold → code → render → platform cuts. The user should not need another tool. |
| 75 | |
| 76 | ## Workflow |
| 77 | |
| 78 | ### Step 1: Context Gathering (Before You Ask Anything) |
| 79 | |
| 80 | Silently check for existing context. Read these files if they exist — don't ask the user to repeat themselves: |
| 81 | |
| 82 | ``` |
| 83 | .superstack/idea-context.md → Product concept, audience, value prop |
| 84 | .superstack/build-context.md → Tech stack, features, deployment status |
| 85 | ``` |
| 86 | |
| 87 | Also check: Does a Remotion project already exist in the working directory? (`remotion.config.ts` or `package.json` with remotion dependency) |
| 88 | |
| 89 | **Auto-detect product assets.** Before the interview, scan the project for usable visual material: |
| 90 | |
| 91 | ```bash |
| 92 | # Screenshots and images |
| 93 | find . -maxdepth 3 -type f \( -name "*.png" -o -name "*.jpg" -o -name "*.jpeg" -o -name "*.webp" \) ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null | head -20 |
| 94 | |
| 95 | # SVG files (logos, icons, illustrations) |
| 96 | find . -maxdepth 3 -type f -name "*.svg" ! -path "*/node_modules/ |