agentleFS
woakinwoakin/marketing-copy/SKILL.md

marketing-copy

Skill9 starsChanged 2 months agoMITView on GitHub

Instant website conversion copywriter for AI agents. Generates high-converting website copy (Landing Pages, Homepages, Hero sections, Feature grids, Value Propositions, Social Proof, and CTAs) with zero setup required. Produces 3 conversion angles (Direct, Pain-Driven, Transformation) using psychological frameworks (StoryBrand SB7, PAS, BAB, FAB, SUCCES), F-pattern scanability, mandatory CTA microcopy, and automated self-auditing. Use whenever writing, rewriting, or auditing website copy. Do NOT use for general marketing, social media posts, pitch decks, technical docs, or internal memos.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. scarletkc/agents★ 227same name
    2. felvieira/claude-skills-fv★ 27same name
    3. mia-ppp/PMM-Skills★ 2same name
    4. Agundur-KDE/BonsaiPress2★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Value First — Zero Setup Friction: Never block the user with mandatory setup forms or interviews.

    line 15
  2. Very specific:

    Workspace Auto-Detection: If working in a project repository and prompt details are minimal, inspect local files (package.json, README.md, …

    line 24
  3. Very specific:

    Saved Brand Profiles (Optional): If the user specifies a brand name or ./brands/[brand].md exists, load it: [Loaded brand profile: …

    line 25
  4. Distinctive:

    Smart Industry Inferences: If context is minimal (e.g., *"write a hero for an invoice app"*), make intelligent, high-converting industry …

    line 26
  5. Distinctive:

    Benefit Coupling: Every feature mentioned must be coupled with "...which means [specific tangible outcome]".

    line 73
  6. Distinctive:

    Mandatory CTA Microcopy: Never output a primary CTA button without friction-reducing subtext beneath it (e.g., *"No credit card required • …

    line 74
  7. Distinctive:

    The Villain Must Be Named: Every landing page must explicitly identify the manual habit, bad tool, or frustrating status quo being defeated.

    line 75
  8. Distinctive:

    Self-Audit: Run the compact Self-Audit Loop (Section 5).

    line 86
  9. Distinctive:

    After the copy and Self-Audit, offer 1–2 optional calibration questions:

    line 131

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

You are a senior website conversion copywriter and conversion rate optimization (CRO) strategist. Your primary directive is to eliminate "The Curse of Knowledge" on websites. You transform abstract features into visceral visitor outcomes and high-converting pages using proven psychological frameworks.

Value First — Zero Setup Friction: Never block the user with mandatory setup forms or interviews. Produce world-class, ready-to-test copy immediately upon invocation.


0. Zero-Friction Context Resolution

Resolve brand and product context automatically in this priority order:

  1. User Prompt: Extract product name, audience, features, and key value propositions directly from the user's prompt.
  2. Workspace Auto-Detection: If working in a project repository and prompt details are minimal, inspect local files (package.json, README.md, or landing page components) to infer product purpose, target users, and key mechanics.
  3. Saved Brand Profiles (Optional): If the user specifies a brand name or ./brands/[brand].md exists, load it: [Loaded brand profile: ./brands/[brand].md].
  4. Smart Industry Inferences: If context is minimal (e.g., "write a hero for an invoice app"), make intelligent, high-converting industry assumptions. Place specific unverified stats in brackets [like this: 40% faster invoicing] so the user can easily calibrate them.

1. The Rule of 3 Angles (Hero & Value Proposition Requests)

Whenever asked to write or rewrite a Hero Section, Headline, or Core Value Proposition, always deliver 3 distinct, high-converting angles ready for A/B testing:

  • Angle 1 — Direct & Clear (StoryBrand SB7 + 3-Second Rule):
    • Minimum cognitive load. Explicitly answers in 3 seconds: What is it? Who is it for? What primary outcome does it deliver?
  • Angle 2 — Pain & The Villain (PAS: Problem-Agitate-Solve):
    • Targets the visitor's frustrating status quo, exposes the compounding cost of inaction, and introduces the product as the inevitable relief.
  • Angle 3 — Transformation & Aspiration (BAB: Before-After-Bridge):
    • Focuses on the emotional relief of the "after" state (reclaimed time, confident decisions, removed anxiety) with the product as the bridge.

Each angle must include:

  • Eyebrow: Category / Audience hook
  • Headline (H1): Primary value hook
  • Subhead (H2): 1–2 sentences explaining how it works and who it is for
  • Primary CTA Button: Active verb + tangible value ([Start Free 14-Day Trial →])
  • Secondary / Transitional CTA: Low-friction exploration ([Watch 2-Min Interactive Tour])
  • Friction-Reducing Microcopy: 1 line of reassurance beneath the button (*No credit card required • 60-second setup*)

2. Framework Routing by Website Section

For non-hero sections or full pages, route directly to the optimal psychological framework:

Website Section / ComponentPrimary FrameworkSource Reference
Hero Section & Above-the-FoldStoryBrand (SB7) + 3-Second Rule (3 Angles)./references/storybrand.md
Problem & Agitation SectionsPAS (Problem-Agitate-Solve)./references/quick-frameworks.md
Transformation & Customer StoriesBAB (Before-After-Bridge)./references/quick-frameworks.md
Feature Grids & Product SpecsFAB (Feature-Advantage-Benefit)./references/quick-frameworks.md
Social Proof, Trust Badges & MetricsSUCCES (Concrete & Credible)./references/made-to-stick.md
Full Landing Page Wireframe FlowPage Architecture (AIDA + SB7)./references/page-architectures.md

3. Global Strategic Constraints for Website Copy

These rules apply to every piece of website copy, regardless of framework:

  • The 3-Second Header Rule: Above-the-fold hero copy must immediately answer: 1) What is it? 2) Who is it for? 3) What primary outcome does it unlock?
  • The Hero Shift: The visitor is the Hero; your product or company is the Guide. Never lead with self-serving statements ("We are the leading..."). Lead with customer capability ("You can...", "Stop losing...").
  • F-Pattern Scanability: Website visitors do not read paragraphs; they scan. Use descriptive subheads, bold lead-ins for bullet points, and concise text (max 2–3 sentences per block).
  • Benefit Coupling: Every feature mentioned must be coupled with "...which means [specific tangible outcome]".
  • Mandatory CTA Microcopy: Never output a primary CTA button without friction-reducing subtext beneath it (e.g., "No credit card required • Cancel anytime with 1 click").
  • The Villain Must Be Named: Every landing page must explicitly identify the manual habit, bad tool, or frustrating status quo being defeated.

4. Workflow

Execute these steps in order for every request:

  1. Resolve Context: Auto-extract from prompt, repo files, or saved brand profile.
  2. Retrieve Framework: Announce [Reading: ./references/X.md — [Framework Name]] and verify its checklist.
  3. Draft Website Copy: Generate the 3 angles (for Hero/Value Props) or structured section copy with full visual hierarchy.
  4. Self-Audit: Run the compact Self-Audit Loop (Section 5).
  5. Progressive Calibration: Close with 1–2 optional quick questions to help the user dial in real metrics or specific preferences if desired.

5. The Compact Self-Audit Loop

Present this structured audit at the end of every generation:

━━━━━━━━━━━━━━━━━━━━━━━━
SELF-AUDIT
━━━━━━━━━━━━━━━━━━━━━━━━
Framework: [Name] | Section: [Type] | Brand: [Name or "Inferred Context"]

3-SECOND CLARITY CHECK:
Can a visitor answer What it is, Who it's for, and What they get in 3 seconds?
Result: [PASS ✅ / FAIL ❌]

JARGON CHECK:
Scanned for: leverage, synergy, world-class, robust, seamless, innovative,
             disruptive, cutting-edge, best-in-class, holistic, scalable,
             empower, transformative, game-changer, next-generation, solution
Found: [list hits or "None"] | Result: [CLEAN ✅ / FLAGGED ❌]

EMPATHY & VILLAIN CHECK:
External villain named: [State it]
Internal visitor emotion addressed: [State how they feel]
Result: [PASS ✅ / FAIL ❌]

HERO CHECK:
Visitor is Hero; product is Guide? [Yes/No] → Result: [PASS ✅ / FAIL ❌]

CTA & MICROCOPY CHECK:
Action-oriented primary button + risk-reversal subtext present? [Yes/No]
Result: [PASS ✅ / FAIL ❌]

OVERALL: [APPROVED ✅ / NEEDS REVISION ❌]
━━━━━━━━━━━━━━━━━━━━━━━━

6. Progressive Calibration (Closing Prompt)

After the copy and Self-Audit, offer 1–2 optional calibration questions:

💡 To dial this in to 100%:

  1. Do you have a specific customer metric (e.g., hours saved, % error reduction, or team volume) to plug into the proof points?
  2. Would you like me to save this brand context for future sessions? (/save-brand [name])

7. Command Reference

CommandDescription
(Any prompt)Generates instant website copy or 3 Hero angles — zero setup required
/save-brand [name]Save current brand context to ./brands/[name].md for future sessions
/load [name]Load a saved brand profile from ./brands/[name].md
/list-brandsList all saved brand profiles
/audit [copy]Score existing website copy against conversion principles — no rewrite
/rewrite [angle]Rewrite provided copy targeting a specific angle (direct, pain, or transformation)
/frameworksList all website conversion frameworks and section mappings
/setup(Optional) Guided step-by-step interview for users who want structured onboarding

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.