Skip to content
Development
Skill

/sota-copywriting

State-of-the-art marketing copywriting and content guidance (2026) covering positioning and value propositions, headlines and landing-page copy, CTAs and social proof, SEO content (search intent, E-E-A-T, Google spam policies), and the accuracy/legal layer — claim

From plugin
sota-skills
2843 skills5 commands4 hooks2 MCP

Claude Code

$ npx -y skills add martinholovsky/SOTA-skills --skill sota-copywriting --agent claude-code

SKILL.md

sota-copywriting.SKILL.md
name: sota-copywriting
description: >-
  State-of-the-art marketing copywriting and content guidance (2026) covering
  positioning and value propositions, headlines and landing-page copy, CTAs
  and social proof, SEO content (search intent, E-E-A-T, Google spam
  policies), and the accuracy/legal layer — claim substantiation, FTC
  Endorsement Guides (2023) and the Consumer Reviews Rule (2024), testimonial
  consent, dark-pattern avoidance, and email-marketing law (CAN-SPAM, GDPR
  consent). Use when writing or reviewing ANY outward-facing content —
  landing pages, marketing sites, product pages, launch announcements,
  app-store listings, newsletters, cold/lifecycle email — AND when auditing
  existing copy for conversion quality, honesty, and legal exposure. Trigger
  keywords: copywriting, marketing copy, landing page, headline, CTA, value
  proposition, positioning, tagline, SEO, meta description, E-E-A-T,
  testimonial, social proof, case study, newsletter, email marketing, app
  store listing, launch post, pricing page, brand voice.

SOTA Copywriting & Marketing Content

Purpose

Expert-level rules for the *words that face the market*: landing pages, product marketing, SEO content, launch posts, and lifecycle email. The core thesis: **conversion copy is a claim-making machine, and every claim is both a persuasion asset and a legal/trust liability — the craft is being specific enough to convince while staying provable.**

Boundaries: this skill owns outward-facing content. In-product interface text is [`sota-ux-writing`](../sota-ux-writing/SKILL.md); technical documentation is [`sota-docs-workflow`](../sota-docs-workflow/SKILL.md); the visual/layout layer of marketing pages is [`sota-frontend-design`](../sota-frontend-design/SKILL.md); consent and privacy-notice engineering is [`sota-privacy-compliance`](../sota-privacy-compliance/SKILL.md).

BUILD mode

When writing marketing/content copy:

1. **Define audience, awareness stage, and the one action** before drafting — a page without a single primary conversion goal is a brochure ([`rules/01`](rules/01-positioning-value-proposition.md)). 2. **Lead with the outcome the reader buys**, prove it with features and evidence — benefit → mechanism → proof, in that order ([`rules/01`](rules/01-positioning-value-proposition.md) §3). 3. **Draft headlines last, pick from ≥5 variants**, test against the 4 U's heuristic, and keep the above-fold contract: what it is, who it's for, what to do next ([`rules/02`](rules/02-headlines-landing-pages.md)). 4. **Run the accuracy gate before publishing** ([`rules/04`](rules/04-claims-legal-trust.md) §1): every objective claim substantiated, every superlative provable or cut, every testimonial consented and typical, every disclosure placed where it's seen. 5. For anything meant to rank: **match search intent and write people-first** — E-E-A-T signals on the page, no scaled low-value content ([`rules/03`](rules/03-seo-content.md)). 6. Before finishing, run each loaded rules file's **Audit checklist** against the draft.

AUDIT mode

**Coverage:** every `rules/` file's Audit checklist applies in AUDIT mode. Mark one *not applicable* only with its reason in the report — never skip a file because the thing it checks for is absent, since that absence may be the finding.

When reviewing existing marketing content:

1. Inventory the surface: landing pages, pricing page, comparison pages, blog/SEO content, email templates/sequences, app-store listings, social proof assets. 2. **Claims-first pass** ([`rules/04`](rules/04-claims-legal-trust.md)): list every objective claim, superlative, statistic, testimonial, and urgency device; demand the substantiation for each. Legal exposure outranks conversion polish. 3. **Conversion pass** ([`rules/01`](rules/01-positioning-value-proposition.md)–`02`): above-fold contract, message hierarchy, CTA quality, proof placement, scannability. 4. **SEO pass** ([`rules/03`](rules/03-seo-content.md)) where organic traffic matters: intent match, E-E-A-T, spam-policy exposure, title/meta/heading hygiene.

Severity conventions

  • **Critical** — legal/deception exposure: unsubstantiated objective claims,

fake or undisclosed-material-connection testimonials, fabricated reviews or social-proof counts, fake urgency (countdown timers that reset), missing unsubscribe/consent basis in email, dark patterns.

  • **High** — trust or ranking damage: superlatives without proof, "results

not typical" testimonials presented as typical, spam-policy-violating content (scaled/doorway), misleading comparison tables, meta/title bearing no relation to page content.

  • **Medium** — conversion damage: no clear above-fold value proposition,

feature-first copy with no benefit framing, generic CTAs ("Learn more"), proof present but unspecific, intent-mismatched SEO content.

  • **Low** — polish: weak headline variants, wall-of-text sections, missing

message match between ad and landing page, stale dates.

Finding format

`file:line | rule violated | severity | effort | fix` — for claim findings, state what substantiation would be sufficient; for copy findings, propose the rewritten line.

Rules index

| File | Read this when... | |---|---| | [`rules/01-positioning-value-proposition.md`](rules/01-positioning-value-proposition.md) | Deciding what the copy argues: audience and awareness stages, value-proposition structure, benefit-vs-feature discipline, message hierarchy, differentiation claims, evidence types, we-vs-you framing. | | [`rules/02-headlines-landing-pages.md`](rules/02-headlines-landing-pages.md) | Writing the page: headline craft and variants, above-fold contract, section flow (attention→interest→desire→action as a heuristic), scannability, CTA wording and placement, social-proof presentation, pricing-page honesty (incl. EU prior-price rule). | | [`rules/03-seo-content.md`](rules/03-seo-content.md) | Content meant to be

Read more
@martinholovsky
Ships withsota-skills

Make your AI coding assistant build and audit like your most senior engineer. Your assistant is brilliant — it just doesn't know your standards, and it forgets the ones it does know as the task grows long.

2843 skills2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
28
Star history of martinholovsky/SOTA-skills on GitHub, a chart by star-history.com

Other skills on sota-skills.

sota-c-cpp

sota-c-cpp

State-of-the-art C and C++ engineering rules that Claude applies when writing or auditing C/C++. Covers modern idioms (RAII,…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about sota-copywriting.

Which coding agents can use sota-copywriting?
sota-copywriting installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.