$npx -y skills add Rune-kit/rune --skill marketingCreate marketing assets and execute launch strategy. Use when crafting landing copy, social banners, SEO meta, blog posts, or video scripts — coordinates with launch (deploy + announce) and the @rune-pro/growth pack (research / content / CRO).
| 1 | # marketing |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Create marketing assets and execute launch strategy. Marketing generates landing page copy, social media banners, SEO metadata, blog posts, and video scripts. Analyzes the project to create authentic, data-driven marketing content. |
| 6 | |
| 7 | ## Called By (inbound) |
| 8 | |
| 9 | - `launch` (L1): Phase 4 MARKET — marketing phase of launch pipeline |
| 10 | - User: `/rune marketing` direct invocation |
| 11 | |
| 12 | ## Calls (outbound) |
| 13 | |
| 14 | - `scout` (L2): scan codebase for features, README, value props |
| 15 | - `trend-scout` (L3): market trends, competitor positioning |
| 16 | - `research` (L3): competitor analysis, SEO keyword data |
| 17 | - `asset-creator` (L3): generate OG images, social cards, banners |
| 18 | - `video-creator` (L3): create demo/explainer video plan |
| 19 | - `slides` (L3): generate presentation decks for launches and demos |
| 20 | - `doc-processor` (L3): export marketing deliverables as PDF/DOCX (press kits, one-pagers, sponsor decks) |
| 21 | - `browser-pilot` (L3): capture screenshots for marketing assets |
| 22 | - L4 extension packs: domain-specific content when context matches (e.g., @rune/content for blog posts, @rune/analytics for campaign measurement) |
| 23 | - `@rune-pro/growth/content-scorer` (L4 Pro, optional): 5-dimension content quality gate — if available, score all generated copy for AI phrase contamination and humanity |
| 24 | - `@rune-pro/growth/cro-analyst` (L4 Pro, optional): psychology-driven CRO analysis for landing pages — if available, audit generated landing copy through 7 behavioral lenses |
| 25 | |
| 26 | ## Execution Steps |
| 27 | |
| 28 | ### Step 1 — Understand the product |
| 29 | |
| 30 | Call `rune:scout` to scan the codebase. Ask scout to extract: |
| 31 | - Feature list (what the product actually does) |
| 32 | - README summary |
| 33 | - Target audience signals (from code, comments, config) |
| 34 | - Tech stack (relevant for developer marketing) |
| 35 | |
| 36 | Read any existing `marketing/`, `docs/`, or `landing/` directories if present. |
| 37 | |
| 38 | ### Step 2 — Research market |
| 39 | |
| 40 | Call `rune:trend-scout` with the product category to identify: |
| 41 | - Top 3 competitors and their positioning |
| 42 | - Current market trends relevant to this product |
| 43 | - Differentiators to emphasize |
| 44 | |
| 45 | Call `rune:research` for: |
| 46 | - SEO keyword opportunities (volume vs. competition) |
| 47 | - Competitor messaging patterns to avoid or counter |
| 48 | |
| 49 | ### Step 2.5 — Establish Brand Voice |
| 50 | |
| 51 | Before generating any copy, define the brand voice contract. This prevents inconsistent tone across marketing assets. |
| 52 | |
| 53 | **Brand Voice Matrix** — answer these for the product: |
| 54 | |
| 55 | | Dimension | Spectrum | This product | |
| 56 | |-----------|----------|--------------| |
| 57 | | Formality | Casual ←→ Formal | [position] | |
| 58 | | Humor | Serious ←→ Playful | [position] | |
| 59 | | Authority | Peer ←→ Expert | [position] | |
| 60 | | Warmth | Clinical ←→ Friendly | [position] | |
| 61 | | Urgency | Patient ←→ Urgent | [position] | |
| 62 | |
| 63 | **Voice rules** (generate 3-5): |
| 64 | - "We say [X], never [Y]" — e.g., "We say 'start free', never 'sign up now'" |
| 65 | - "Our tone is [X] because our users are [Y]" |
| 66 | - "Avoid [specific words/phrases] because [reason]" |
| 67 | |
| 68 | **Vocabulary list** (5-10 terms): |
| 69 | - Preferred terms: [words this brand uses] |
| 70 | - Forbidden terms: [words to avoid and why] |
| 71 | - Jargon policy: [use/avoid/explain technical terms] |
| 72 | |
| 73 | Save voice contract to `marketing/brand-voice.md`. All subsequent copy MUST follow this voice. |
| 74 | |
| 75 | If `marketing/brand-voice.md` already exists → Read it and apply. Do NOT regenerate without user request. |
| 76 | |
| 77 | ### Step 3 — Generate copy |
| 78 | |
| 79 | Using product understanding, market research, and **brand voice contract**, produce: |
| 80 | |
| 81 | **Anti-AI Copy Rules** (apply to ALL generated copy): |
| 82 | - NEVER open with "In today's...", "Are you struggling with...", "Have you ever wondered..." |
| 83 | - NEVER use: "game-changer", "revolutionary", "seamlessly", "leverage", "unlock the power of", "dive deep into", "delve", "robust", "streamline", "cutting-edge" |
| 84 | - MUST use one of 5 hook types for headlines: Provocative Question, Specific Scenario, Surprising Statistic, Bold Statement, or Counterintuitive Claim |
| 85 | - MUST include specific numbers, names, or outcomes — not vague claims ("many users love it") |
| 86 | - If the copy sounds like it was written by a generic AI → rewrite until it has personality |
| 87 | |
| 88 | **Hero section** |
| 89 | - Headline (under 10 words, outcome-focused, uses one of the 5 hook types above) |
| 90 | - Subheadline (1-2 sentences expanding the promise) |
| 91 | - Primary CTA button text |
| 92 | |
| 93 | **Value propositions** (3 items) |
| 94 | - Icon/emoji, title, 1-sentence description each |
| 95 | |
| 96 | **Feature list** (pulled from Step 1 scout output) |
| 97 | - Name + benefit phrasing for each feature |
| 98 | |
| 99 | **Social proof section** (placeholder copy if no real testimonials) |
| 100 | |
| 101 | **Secondary CTA** (bottom of page) |
| 102 | |
| 103 | ### Step 3.5 — Competitive Response Playboo |