Marketing
Marketing content creation and campaign planning framework. USE WHEN user says 'marketing', 'campaign', 'copy', 'headline', 'landing page', 'email sequence', 'social media', 'brand voice', 'AIDA', 'PAS', 'value proposition', or needs persuasive content.
What this skill does
# Marketing
Comprehensive marketing framework for content creation, copywriting, and campaign planning.
## Workflow Routing
| Workflow | Trigger | File |
|----------|---------|------|
| **Copy** | "write copy", "headline", "tagline" | `Workflows/Copy.md` |
| **Campaign** | "campaign", "launch", "promotion" | `Workflows/Campaign.md` |
| **Email** | "email sequence", "newsletter", "drip" | `Workflows/Email.md` |
| **Social** | "social media", "post", "thread" | `Workflows/Social.md` |
| **Landing** | "landing page", "sales page" | `Workflows/Landing.md` |
## Copywriting Frameworks
### AIDA (Attention-Interest-Desire-Action)
```
A - Attention: Hook with bold claim or question
I - Interest: Build curiosity with benefits
D - Desire: Create emotional connection
A - Action: Clear CTA with urgency
```
### PAS (Problem-Agitate-Solution)
```
P - Problem: Identify the pain point
A - Agitate: Amplify the consequences
S - Solution: Present your offering
```
### BAB (Before-After-Bridge)
```
B - Before: Current painful state
A - After: Desired future state
B - Bridge: Your product/service
```
### 4Ps (Promise-Picture-Proof-Push)
```
P - Promise: Big benefit headline
P - Picture: Vivid outcome description
P - Proof: Social proof/testimonials
P - Push: Urgency and CTA
```
### PASTOR (Problem-Amplify-Story-Transformation-Offer-Response)
```
P - Problem: Define the struggle
A - Amplify: What happens if unsolved
S - Story: Relatable narrative
T - Transformation: The change possible
O - Offer: Your solution
R - Response: Call to action
```
## Brand Voice Configuration
Define in `templates/brand-voice.yaml`:
```yaml
brand:
name: "Your Brand"
tagline: "Your tagline"
voice:
tone: professional | casual | playful | authoritative | empathetic
personality: [traits]
vocabulary:
use: [preferred terms]
avoid: [banned terms]
audience:
primary: "Description"
pain_points: [list]
desires: [list]
objections: [list]
```
## Content Types
### Headlines
- **Benefit-driven**: "Get [Benefit] Without [Pain Point]"
- **Curiosity**: "The Secret [Industry] Insiders Don't Want You to Know"
- **How-to**: "How to [Achieve Goal] in [Timeframe]"
- **List**: "[Number] Ways to [Achieve Result]"
- **Question**: "Are You Making These [Number] [Topic] Mistakes?"
### Email Subject Lines
- **Urgency**: "[Time] left to [benefit]"
- **Curiosity**: "I shouldn't be telling you this..."
- **Personal**: "[Name], quick question about [topic]"
- **Value**: "Free [resource] inside"
- **Social proof**: "[Number] people already [action]"
### Email Sequence Strategic Order (Critical)
Always structure nurture sequences in this progression — order matters for conversion:
1. **Email 1 — Welcome/Value Delivery**: Deliver promised resource, set expectations, quick win
2. **Email 2 — Social Proof/Case Study**: Establish credibility NOW while interest is high; specific customer result, certification, or data point
3. **Email 3 — Objections/FAQ/Deeper Positioning**: Address the 3–5 real reasons prospects don't buy; answer "why you over competitors"
4. **Email 4 — Direct Offer/Conversion CTA**: Hard close with specific offer, deadline, or next step — NOT a "reply with later" graceful exit
> ⚠️ Do NOT swap Email 2 and Email 3. Social proof must come before objection handling. Email 4 must drive a real conversion action.
### CTAs
- **Action-oriented**: "Start [Benefit] Now"
- **Benefit-focused**: "Get My Free [Resource]"
- **Low-commitment**: "See How It Works"
- **Urgency**: "Claim Your Spot Before [Deadline]"
- **Social proof**: "Join [Number] [Audience]"
### Buyer Objection Handling (Required for B2B/High-Consideration Copy)
When writing copy for any product or service, proactively identify and address realistic buyer objections with **specific proof points** — not vague references to "case studies" or "ROI calculators." Always provide substantive responses even without full product details by using placeholder specifics that demonstrate the pattern:
| Common Objection | Evidence-Based Response Pattern |
|-----------------|--------------------------------|
| **Switching costs / disruption** | "Onboarding takes X days; dedicated account manager handles transition; [specific guarantee]" |
| **Unknown supplier risk** | Lead with certifications (ISO, industry accreditations), years in operation, named clients or sectors served |
| **Price vs. competitors** | Total cost of ownership argument: "[Competitor] costs less upfront but [specific failure mode] costs £X; our [feature] prevents this" |
| **Qualification/lead time** | Specific turnaround data: "95% of quotes returned within 24 hours; standard orders ship in X days" |
| **Capacity concerns** | Concrete capacity metric: "X,000 sq ft facility, Y machines, Z shifts — current utilisation at N%" |
| **Quality uncertainty** | Named certifications + specific tolerance/accuracy claims + defect rate or rework stats |
> ✅ When generating objection-handling content, always write out the **actual counter-message copy**, not just the category name. Show the specific proof point in the response itself.
## Integration Points
| Skill | Integration |
|-------|-------------|
| **Blog** | Generate blog post outlines, headlines |
| **TiredEngineer** | Technical marketing with authentic voice |
| **Art** | Generate marketing visuals |
| **Research** | Competitive analysis, market research |
## Examples
**Example 1: Write headlines for a product launch**
```
User: "Write 5 headlines for our new project management tool launch"
→ Load brand voice from templates/brand-voice.yaml
→ Apply headline frameworks
→ Generate 5 variations using different formulas
```
**Example 2: Create an email sequence**
```
User: "Create a 5-email welcome sequence for new subscribers"
→ Invoke Workflows/Email.md
→ Structure: Welcome → Value → Story → Offer → Urgency
→ Output sequence with subject lines and body copy
```
**Example 3: Plan a product launch campaign**
```
User: "Plan a launch campaign for our SaaS product"
→ Invoke Workflows/Campaign.md
→ Output: Timeline, channels, content calendar, KPIs
```
**Example 4: Write landing page copy**
```
User: "Write copy for our landing page using PAS framework"
→ Invoke Workflows/Landing.md with framework=PAS
→ Output: Hero, benefits, proof, CTA sections
```
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".