Agent-Skills.md

Agent Skills: Marketing Writer

Create marketing content optimized for both human readers and LLM discovery (GEO/AEO). Use when the user needs to write or improve marketing materials including landing page copy, tweet threads, launch emails, blog posts, or feature announcements. Automatically analyzes the user's codebase to understand product features and value propositions. Applies casual, direct brand voice and Generative Engine Optimization principles to maximize visibility in AI search results.

UncategorizedID: AIBPM42/hodgesfooshee-site-spark/marketing-writer

Install this agent skill to your local

pnpm dlx add-skill https://github.com/AIBPM42/hodgesfooshee-site-spark/tree/HEAD/.claude/skills/marketing-writer

Skill Files

Browse the full folder contents for marketing-writer.

Download Skill

Loading file tree…

.claude/skills/marketing-writer/SKILL.md

Skill Metadata

Name
marketing-writer
Description
Create marketing content optimized for both human readers and LLM discovery (GEO/AEO). Use when the user needs to write or improve marketing materials including landing page copy, tweet threads, launch emails, blog posts, or feature announcements. Automatically analyzes the user's codebase to understand product features and value propositions. Applies casual, direct brand voice and Generative Engine Optimization principles to maximize visibility in AI search results.

Marketing Writer

Overview

This skill creates marketing content that is:

  • GEO-optimized: Structured for maximum visibility in LLM search results and AI citations
  • Codebase-aware: Automatically understands your product by analyzing your codebase
  • Brand-consistent: Uses casual, direct tone without corporate buzzwords
  • Template-driven: Follows proven formats for landing pages, social posts, and emails

When to Use This Skill

Trigger this skill when the user:

  • Ships a new feature and needs marketing copy
  • Asks to write a tweet thread, launch email, or landing page section
  • Requests help with product positioning or messaging
  • Needs to improve existing marketing content
  • Wants content that ranks/gets cited by AI search tools
  • Needs subscription CTAs or lead capture forms for TOFU/MOFU/BOFU content
  • Building "coming soon" pages with email collection

Workflow

Step 1: Understand the Context

If writing about a feature or product, first analyze the codebase:

# List key directories to understand structure
view /mnt/user-data/uploads

# Check for common entry points
view /mnt/user-data/uploads/README.md
view /mnt/user-data/uploads/package.json

# Look for feature files, components, or API routes
view /mnt/user-data/uploads/src
view /mnt/user-data/uploads/app

Extract these details:

  • What problem does this solve?
  • How does it work technically?
  • What makes it different/better?
  • What are the key user benefits?

If the user has already explained the feature, skip codebase analysis and use their description.

Step 2: Choose the Content Template

Based on the user's request and funnel stage:

Awareness Content (TOFU):

  • Landing page copy → Use Problem-Solution-Benefit format (see references/templates.md)
  • Tweet thread → Use Hook-Credibility-Value-CTA structure (see references/templates.md)
  • Blog post or long-form → Apply GEO framework (see references/geo-framework.md)

Consideration Content (MOFU):

  • Feature pages → Use Value Equation or Grand Slam Offer (see references/hormozi-frameworks.md)
  • Subscription CTAs → Use TOFU/MOFU patterns (see references/funnel-subscriptions.md)
  • Comparison pages → Use Problem-Agitate-Solve (see references/hormozi-frameworks.md)

Conversion Content (BOFU):

  • Sales pages → Use Grand Slam Offer + Value Stacking (see references/hormozi-frameworks.md)
  • Pricing pages → Use Value Stacking + The Reversal (see references/hormozi-frameworks.md)
  • CTAs → Use CTA Stack (Scarcity/Urgency/Bonuses/Guarantees) (see references/hormozi-frameworks.md)
  • Launch emails → Use Personal-Problem-Solution-CTA format (see references/templates.md)

Any Stage:

  • Coming soon pages → Use waiting list template (see references/funnel-subscriptions.md)

Step 3: Apply Brand Voice

Follow these voice guidelines in ALL content:

✅ Do:

  • Write like texting a friend
  • Use contractions (you're, it's, we've)
  • Lead with empathy for the problem
  • Be specific with examples
  • Use short paragraphs (2-3 sentences max)

❌ Don't:

  • Use corporate buzzwords (synergy, leverage, robust, cutting-edge, revolutionize)
  • Make vague claims ("many experts agree")
  • Oversell with hyperbole
  • Use jargon unless the audience uses it
  • Bury the main point

Quick tone check:

  • Would you say this to a friend? → Good
  • Does it sound like a press release? → Revise

Step 4: Structure for GEO

If writing long-form content (blog posts, docs, guides):

Read references/geo-framework.md first, then apply:

  1. Lead with the answer - First 2-3 sentences answer the core question
  2. Use clear hierarchy - H2/H3 headings, never skip levels
  3. Make it scannable - Bold key facts, use lists generously
  4. Add structured data - Include data tables or FAQ sections
  5. Include citations - Reference specific sources when making claims

Quality checklist:

  • [ ] H1 clearly states the topic
  • [ ] First paragraph answers the main question
  • [ ] Key facts are bolded
  • [ ] Includes lists, tables, or FAQ section
  • [ ] Every sentence adds value (no fluff)
  • [ ] Written in casual, direct voice

Step 5: Write and Iterate

For short-form (tweets, emails, landing sections):

  1. Write the first draft using the appropriate template
  2. Check voice and tone
  3. Cut unnecessary words
  4. Verify the CTA is clear and easy

For long-form (blog posts, guides):

  1. Start with an outline using H2/H3 structure
  2. Write section by section
  3. Add data tables or FAQ if relevant
  4. Bold key facts for scannability
  5. Add a TL;DR at top or bottom

Always ask yourself:

  • Is this clear enough for someone skimming?
  • Would an LLM cite this as authoritative?
  • Does this sound like a human wrote it, not a marketing department?

Special Cases

When the Codebase Isn't Available

If you can't access the codebase:

  1. Ask the user: "What does [feature] do, and how does it help users?"
  2. Extract: problem, solution mechanic, and main benefit
  3. Proceed with template selection

When Writing About Multiple Features

For landing pages with multiple feature sections:

  1. Prioritize by user impact (biggest value first)
  2. Use consistent Problem-Solution-Benefit format for each
  3. Keep each section concise (3-4 paragraphs max)
  4. Vary your opening hooks to avoid repetition

When Improving Existing Content

If the user shares existing marketing copy:

  1. Identify voice issues (buzzwords, vague claims, buried points)
  2. Restructure using appropriate template
  3. Add specificity (numbers, examples, timeframes)
  4. Simplify language and shorten sentences
  5. Verify CTA is clear

When Creating Subscription CTAs

If the user needs email capture, newsletter signups, or lead generation:

First, identify the funnel stage:

  • TOFU (Top of Funnel): Awareness content – Low friction, educational (newsletters, market reports)
  • MOFU (Middle of Funnel): Consideration content – Problem-specific resources (checklists, calculators, comparison guides)
  • BOFU (Bottom of Funnel): Decision content – High-intent conversion (consultations, quotes, trials)

Then follow the workflow:

  1. Read references/funnel-subscriptions.md for stage-specific templates
  2. Match the ask to the value offered (email only for TOFU, more fields for BOFU)
  3. Use benefit-focused button copy ("Get My Results" not "Submit")
  4. Include friction reducers ("No spam," "Unsubscribe anytime," timeframes)
  5. Add schema markup if building a dedicated subscription page

Quick template selector:

  • Newsletter/updates → TOFU Newsletter Signup
  • Content notification → TOFU Coming Soon
  • Downloadable guide/checklist → MOFU Downloadable Resource
  • Calculator/tool → MOFU Interactive Tool
  • Consultation/call → BOFU Consultation Booking
  • Quote request → BOFU Quote/Proposal Request
  • Free trial → BOFU Trial with Onboarding

Resources

references/templates.md

Detailed templates for:

  • Landing page feature sections (Problem → Solution → Benefit)
  • Tweet threads (Hook → Credibility → Value → CTA)
  • Launch emails (Personal → Specific Value → Easy CTA)

Read this when: Writing any of the above content types.

references/geo-framework.md

Comprehensive guide to Generative Engine Optimization including:

  • Structured content principles
  • Authority signals
  • Scannability tactics
  • Quality checklist

Read this when: Writing blog posts, guides, or long-form content that should rank in LLM search results.

references/funnel-subscriptions.md

Complete guide to subscription CTAs and lead capture forms:

  • TOFU/MOFU/BOFU subscription patterns
  • Coming soon page templates
  • Form design best practices
  • Button copy guidelines
  • Schema markup for subscription pages

Read this when: Creating email captures, lead gen forms, coming soon pages, or any content with subscription CTAs.

references/hormozi-frameworks.md

High-conversion copywriting frameworks for MOFU/BOFU content:

  • Value Equation: Maximize perceived value (Dream Outcome × Likelihood / Time × Effort)
  • Grand Slam Offer: Structure irresistible offers (Vehicle + Outcome + Unique Mechanism + Proof)
  • Problem-Agitate-Solve (PAS): Aggressive pain-focused copy
  • CTA Stack: Layer scarcity, urgency, bonuses, and guarantees
  • Value Stacking: Show total value vs. actual price
  • The Reversal: Flip objections into selling points

Read this when: Writing sales pages, pricing pages, high-ticket offers, or any content focused on conversion (BOFU). Use sparingly for TOFU—these frameworks are aggressive and conversion-focused.

Examples

Example 1: Feature Announcement

User: "I just shipped auto-save. Write a tweet thread about it."

Response:

[Reads codebase to understand auto-save implementation]

Here's your thread:

1/5 Lost hours of work to a browser crash?

Built auto-save that actually works—even when you're offline.

Every keystroke synced to the cloud. Zero "Save" buttons. 🧵

2/5 The problem: Most apps say "auto-save" but only save every 30 seconds.

Or they save locally, so switching devices = lost work.

Neither cuts it when you're in flow state.

[continues with remaining tweets following Hook-Credibility-Value-CTA structure]

Example 2: Landing Page Section

User: "Write landing page copy for our new collaboration feature"

Response:

[Analyzes codebase to understand how real-time collaboration works]

## Work Together, Stay in Sync

### The Problem
Collaborating on documents means endless email chains. "Here's v3-final-FINAL-really-final.docx." Someone's always working on the old version. Comments get lost. Nobody knows what's current.

### The Solution
Everyone sees the same document, updated in real-time. Type a sentence—your teammate sees it instantly. They add a comment—you get notified immediately. Like Google Docs, but for [your product].

### The Benefit
Stop the version chaos. Your whole team stays on the same page, literally. Make decisions faster because everyone's seeing the same information at the same time.

Example 3: TOFU Coming Soon Page

User: "I'm building a real estate blog. Need a coming soon page for my Miami market analysis with email capture. It's TOFU content."

Response:

[Reads references/funnel-subscriptions.md for TOFU patterns]

# Miami Real Estate Market Analysis 2025

## Comprehensive Market Report - Coming Soon

We're analyzing 12 months of sales data, inventory trends, and price forecasts for every Miami neighborhood. This guide will help you understand where the market's headed.

**What you'll get:**
- Condo vs single-family home price trends
- Neighborhood-by-neighborhood breakdown
- Expert predictions for 2025
- Best times to buy or sell

### Be notified when this publishes

[Email input]
[Send Me the Report When It's Ready]

We'll send you one email with the link. No spam.

*Expected publish date: January 2025*

---

**In the meantime:**
Check out these market insights:
- [Link to existing TOFU content]
- [Link to existing TOFU content]