From rune
Generates marketing assets including landing copy, social banners, SEO meta, blog posts, and video scripts for product launches. Analyzes codebase for data-driven content.
npx claudepluginhub rune-kit/rune --plugin @rune/analyticsThis skill uses the workspace's default tool permissions.
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.
Provides 23 marketing skills for strategy, copywriting, SEO, CRO, paid ads, email, social, and growth tactics. Auto-activates for marketing needs in dev projects.
Crafts product positioning, messaging, value propositions, GTM strategies, and launch copy via sub-skills like pitch-position, pitch-message, and pitch-launch. Auto-activates on marketing requests.
Generates GTM strategy documents (brand, market landscape, messaging, channels) by scanning codebases and conducting multi-session user interviews. Supports initial research and git-diff updates.
Share bugs, ideas, or general feedback.
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.
launch (L1): Phase 4 MARKET — marketing phase of launch pipeline/rune marketing direct invocationscout (L2): scan codebase for features, README, value propstrend-scout (L3): market trends, competitor positioningresearch (L3): competitor analysis, SEO keyword dataasset-creator (L3): generate OG images, social cards, bannersvideo-creator (L3): create demo/explainer video planslides (L3): generate presentation decks for launches and demosdoc-processor (L3): export marketing deliverables as PDF/DOCX (press kits, one-pagers, sponsor decks)browser-pilot (L3): capture screenshots for marketing assets@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@rune-pro/growth/cro-analyst (L4 Pro, optional): psychology-driven CRO analysis for landing pages — if available, audit generated landing copy through 7 behavioral lensesCall rune:scout to scan the codebase. Ask scout to extract:
Read any existing marketing/, docs/, or landing/ directories if present.
Call rune:trend-scout with the product category to identify:
Call rune:research for:
Before generating any copy, define the brand voice contract. This prevents inconsistent tone across marketing assets.
Brand Voice Matrix — answer these for the product:
| Dimension | Spectrum | This product |
|---|---|---|
| Formality | Casual ←→ Formal | [position] |
| Humor | Serious ←→ Playful | [position] |
| Authority | Peer ←→ Expert | [position] |
| Warmth | Clinical ←→ Friendly | [position] |
| Urgency | Patient ←→ Urgent | [position] |
Voice rules (generate 3-5):
Vocabulary list (5-10 terms):
Save voice contract to marketing/brand-voice.md. All subsequent copy MUST follow this voice.
If marketing/brand-voice.md already exists → Read it and apply. Do NOT regenerate without user request.
Using product understanding, market research, and brand voice contract, produce:
Anti-AI Copy Rules (apply to ALL generated copy):
Hero section
Value propositions (3 items)
Feature list (pulled from Step 1 scout output)
Social proof section (placeholder copy if no real testimonials)
Secondary CTA (bottom of page)
When trend-scout identifies active competitors or market threats, generate pre-planned counter-strategies. This turns reactive scrambling into prepared responses.
Four Threat Scenarios:
| Scenario | Trigger Signal | Response Window |
|---|---|---|
| Price War | Competitor drops price >20% | 24-48 hours |
| New Market Entry | New competitor launches in your space | 1-2 weeks |
| Viral Competitor | Competitor content goes viral (10x normal engagement) | 24-72 hours |
| Fast Follower | Competitor copies your feature within 30 days of launch | 1 week |
For each relevant scenario, document:
## Counter-Strategy: [Scenario Name]
### Trigger
- Signal: [what to watch for]
- Detection: [how to monitor — social listening, price tracking, etc.]
- Response window: [how fast to react]
### Counter-Move
- **Immediate (Day 1)**: [first response — usually messaging/positioning]
- **Short-term (Week 1)**: [tactical moves — promos, content, outreach]
- **Medium-term (Month 1)**: [strategic adjustments — product, pricing, positioning]
### Resources Required
- Team: [who needs to be involved]
- Budget: [estimated cost]
- Assets: [what to prepare in advance]
### Success Metric
- [How to know the counter-strategy worked]
### Pre-Built Assets
- [ ] Response messaging template
- [ ] Social post drafts
- [ ] Email to existing customers
- [ ] FAQ for sales/support team
Rules:
Skip this step if:
Save to marketing/counter-playbook.md.
Produce ready-to-post content:
Twitter/X thread (5-7 tweets)
LinkedIn post (150-300 words)
Product Hunt tagline (under 60 characters)
Produce for the landing page:
<title>[Meta title — under 60 chars, primary keyword first]</title>
<meta name="description" content="[150-160 chars, includes CTA]">
<meta property="og:title" content="[OG title]">
<meta property="og:description" content="[OG description]">
<meta property="og:image" content="[OG image path]">
<link rel="canonical" href="[canonical URL]">
Target keywords list (5-10 terms with rationale).
If the project already has a deployed site or existing pages, run a technical SEO audit before generating new metadata.
Automated checks (use Grep + Read on codebase):
<title>, <meta description>, og:title, og:description, og:image. Flag pages missing any.<h1>. No skipped levels (h1→h3 without h2). Use Grep for <h1, <h2, <h3 patterns.<img without alt= attribute. Every image needs descriptive alt text (not "image", not empty).<link rel="canonical". Missing canonical = duplicate content risk.application/ld+json or microdata. Recommend adding if missing (Product, Organization, Article schemas).next/image or lazy loading on images. Flag <img> without loading="lazy" below fold.sitemap.xml or sitemap generation in build config. Flag if missing.robots.txt. Verify it doesn't accidentally block important pages.9. Schema Markup: Check for application/ld+json blocks. Recommend adding relevant types:
| Content Type | Schema Type | Key Properties |
|---|---|---|
| Product page | Product | name, description, offers, review, aggregateRating |
| Article/Blog | Article | headline, author, datePublished, dateModified, image |
| FAQ section | FAQPage | mainEntity[].name, mainEntity[].acceptedAnswer |
| How-to guide | HowTo | name, step[].name, step[].text, totalTime |
| Organization | Organization | name, url, logo, sameAs[] |
| Breadcrumbs | BreadcrumbList | itemListElement[].name, itemListElement[].item |
| Software | SoftwareApplication | name, operatingSystem, applicationCategory, offers |
| Review | Review | itemReviewed, reviewRating, author, reviewBody |
| Comparison | ItemList | itemListElement[] with individual Product/Review schemas |
| Local biz | LocalBusiness | name, address, telephone, openingHoursSpecification |
Use @graph pattern to combine multiple schema types on a single page:
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Organization", ... },
{ "@type": "WebPage", ... },
{ "@type": "BreadcrumbList", ... }
]
}
10. Programmatic SEO awareness: If the site has repeatable content patterns (product listings, city pages, comparison pages), note the opportunity for template-driven SEO pages. Common playbooks:
best [tool] for [persona] pages across personas[product A] vs [product B] for all competitor pairs[service] in [city] for local reach[product] + [integration] for every supported integrationFlag programmatic SEO opportunities in the audit report. Execution details are in @rune-pro/growth pack.
Output: SEO Audit Report with pass/fail per check. Save to marketing/seo-audit.md.
Fix critical SEO issues (missing titles, broken heading hierarchy) in the implementation plan. Non-critical issues go to marketing/seo-backlog.md.
Call rune:asset-creator to generate:
Call rune:video-creator to produce:
Call rune:slides to generate presentation decks for launch demos, sprint reviews, or investor pitches.
If rune:browser-pilot is available, capture screenshots of the running app to use as real product imagery.
Output all assets as structured markdown sections. Present to user for review before saving files.
After user approves, use Write to save:
marketing/brand-voice.md — voice contract from Step 2.5marketing/landing-copy.md — all copy from Step 3marketing/counter-playbook.md — competitive response strategies from Step 3.5 (if competitors exist)marketing/social-posts.md — all posts from Step 4marketing/seo-meta.json — SEO data from Step 5marketing/seo-audit.md — SEO audit results from Step 5.5 (if existing site)marketing/video-script.md — video plan from Step 6## Marketing Assets
- **Landing Copy**: [generated — headline, subheadline, value props, features, CTAs]
- **Social Posts**: Twitter thread (N tweets), LinkedIn post, PH tagline
- **SEO Metadata**: title, description, OG tags, N target keywords
- **Visuals**: OG image, Twitter card, PH thumbnail
- **Video**: 60s demo script with shot list
### Generated Files
- marketing/landing-copy.md
- marketing/social-posts.md
- marketing/seo-meta.json
- marketing/video-script.md
Known failure modes for this skill. Check these before declaring done.
| Failure Mode | Severity | Mitigation |
|---|---|---|
| Fabricating statistics, benchmarks, or testimonials | CRITICAL | Constraint 3: no fabrication — if no real stats exist, use honest placeholder copy |
| Generating copy before deploy verified live | HIGH | Constraint 2: deploy must be confirmed live before marketing runs |
| Copy not based on actual codebase features (invented value props) | HIGH | scout must run in Step 1 — features extracted from actual code, not assumptions |
| Missing SEO keyword analysis (no research call) | MEDIUM | Step 2: research call for keyword data is mandatory for SEO section |
| Files saved without user approval | MEDIUM | Step 7: present ALL assets to user, wait for approval before writing files |
| Counter-playbook without detection mechanism | HIGH | Every scenario needs a monitoring method — "watch for price drops" is useless without specifying WHERE to watch and HOW to automate |
| Counter-playbook with unrealistic response windows | MEDIUM | If response window is 24h but pre-built assets don't exist, the playbook will fail — either extend window or create assets NOW |
| Generating counter-playbook for blue ocean products | LOW | Skip Step 3.5 if no direct competitors — counter-strategies need someone to counter |
| Artifact | Format | Location |
|---|---|---|
| Brand voice contract | Markdown | marketing/brand-voice.md |
| Landing page copy | Markdown | marketing/landing-copy.md |
| Competitive response playbook | Markdown | marketing/counter-playbook.md |
| Social media posts | Markdown | marketing/social-posts.md |
| SEO metadata | JSON | marketing/seo-meta.json |
| SEO audit report | Markdown | marketing/seo-audit.md |
| Video demo script | Markdown | marketing/video-script.md |
~2000-5000 tokens input, ~1000-3000 tokens output. Sonnet for copywriting quality.
Scope guardrail: marketing generates assets based on actual product capabilities only — no aspirational copy, no fabricated stats.