Skip to content

ericrisco/rsc-harness / skills/marketing

marketing

Verified

Use when the words span a marketing surface — value proposition, section copy, microcopy, launch and email sequences, channel adaptation, SEO-aware structure — grounded in the brand study, which it stops and builds if missing. NOT one conversion page (that is `landing-copy`), NOT tone rules (that is `brand-voice`), NOT pixels (that is `design`).

FileKindSize
SKILL.mdskill md15.2 KB
evals/README.mdmarkdown3.0 KB
evals/cases.yamlconfig7.0 KB
references/brand-grounding.mdmarkdown9.3 KB
references/campaigns-and-channels.mdmarkdown7.2 KB
references/copy-frameworks.mdmarkdown8.2 KB
references/landing-copy.mdmarkdown8.6 KB
references/seo-geo.mdmarkdown19.9 KB
scripts/seo_audit.pyexecutablescript5.6 KB
scripts/verify.shexecutablescript10.2 KB

evals/cases.yaml

View on GitHub
skill: marketing

# Prompts that MUST load the `marketing` skill. The skill owns the WORDS of a
# landing/web/launch surface: value prop, hero, section copy, microcopy, CTAs,
# email/launch sequences, channel adaptation, and SEO/GEO (technical SEO,
# JSON-LD spec, AI-engine citation). It does NOT own pixels (design) or the
# build (nextjs).
should_trigger:
  - prompt: "Write the hero and section copy for our new pricing page."
    why: "Section-by-section landing copy and hero headline are the skill's core conversion-copywriting job."

  - prompt: "Our homepage above-the-fold reads generic and sounds like every other AI startup — can you fix it?"
    why: "Rescuing copy that 'sounds like AI' / reads generic is an explicit trigger; the ban-list and brand-grounding exist for exactly this."

  - prompt: "Turn this feature list into something a customer would actually care about: SSO, audit logs, 99.9% uptime."
    why: "Translating features into benefits (FAB/JTBD, climbing feature -> benefit -> proof) is a named use, even though the user never says 'marketing' or 'copy'."

  - prompt: "We launch Tuesday — I need a 4-email sequence and a post for X and LinkedIn announcing it."
    why: "Launch email sequences plus per-channel adaptation are owned by the campaigns-and-channels part of the skill; user names channels, not the skill."

  - prompt: "How do I get our docs page cited by ChatGPT and Perplexity, and what JSON-LD schema should it have?"
    why: "GEO (getting cited by AI engines) and specifying JSON-LD schema are explicit SEO/GEO triggers owned by references/seo-geo.md (spec, not the React render)."

  - prompt: "What should the button say and what's the reassurance line under it on our signup CTA?"
    why: "Microcopy and CTAs (value on the button, friction-reducing reassurance) are an explicit copy job, phrased without naming the skill."

  - prompt: "Give me a one-line value proposition and subhead for a tool that previews every PR branch automatically."
    why: "Locking the value proposition via the canvas and producing the headline/subhead is the highest-leverage copy task the skill defines."

  - prompt: "Our meta titles and descriptions are a mess and the benefit is buried — can you sort out the on-page copy structure so we rank better?"
    why: "SEO-aware copy structure (one h1, query-answering subheads, title 50-60 / meta 120-160, benefit in first 160 chars) is owned here, not in design or nextjs."

# NEAR-MISS prompts that must NOT load `marketing`. Each routes to the genuinely
# correct sibling. The recurring trap: anything touching a "landing page" that
# is actually about pixels (design) or the build (nextjs), and anything that is
# article/blog content rather than a landing/launch surface.
should_not_trigger:
  - prompt: "Pick the type scale, color palette, and spacing for our landing page hero section."
    route_to: "design"
    why: "Type/color/spacing/layout is the pixels, explicitly delegated to design; marketing only owns the words inside the section."

  - prompt: "Implement the landing page hero in Next.js with the Metadata API and render the JSON-LD in the page."
    route_to: "nextjs"
    why: "Building the page in React/Next and rendering schema/Metadata in code is the build; marketing specifies the title/description/JSON-LD, nextjs renders it."

  - prompt: "Write a 2000-word blog post explaining how our deployment pipeline works."
    route_to: "none"
    why: "Long-form article with no landing/web/launch surface is a content job the skill explicitly stays out of; no sibling owns generic blogging, so it declines."

  - prompt: "Write a CHECK constraint and a partial index to enforce one primary CTA row per campaign in Postgres."
    route_to: "postgresdb"
    why: "Despite the word 'CTA', this is pure SQL schema/constraint work owned by postgresdb, not conversion copy."

  - prompt: "Add a honeypot field and rate-limit the newsletter signup endpoint to stop spam submissions."
    route_to: "security-audit"
    why: "Abuse prevention / input hardening on a form endpoint is a security concern, not the words on the page."

  - prompt: "Design the motion and scroll-reveal animations for the features section of our marketing site."
    route_to: "design"
    why: "Motion and section visual anatomy are design's domain; marketing owns the copy, not the animation."

# Concrete tasks the skill should guide, with a rubric to grade WITH vs WITHOUT
# the skill loaded. A correct skill-guided answer should hit most must_include
# points; an ungrounded answer typically misses the brand gate, specificity,
# and the QA discipline.
capability:
  - scenario: "Write the hero (headline + subhead + primary CTA) for a tool that spins up a live preview URL on every pull request. No brand study exists in the repo yet."
    must_include:
      - "STOPS on the brand-grounding gate first: notes there is no complete brand study under 02-DOCS/wiki/brand/ and interviews the user (ICP, positioning, voice samples) before writing — or, only if the user explicitly says draft rough, labels output 'DRAFT (ungrounded — not brand-checked)'."
      - "Headline built from the value-prop canvas using a concrete formula (outcome+timeframe, 'X without Y', or JTBD), e.g. specificity like '30 seconds' rather than adjectives."
      - "Passes the 5-second test: a stranger can tell what it is, who it's for, and why it's better."
      - "Specificity over adjectives — no 'fast/powerful/seamless'; uses a number or mechanism, and marks any unverifiable metric as [[NEEDS PROOF]] rather than inventing it."
      - "Exactly one primary CTA with value on the button ('Start free', not 'Submit'/'Learn more') plus friction-reducing reassurance microcopy ('No credit card required')."
      - "Avoids every ban-list word (revolutionary, game-changer, seamless, supercharge, unlock, etc.) and matches the brand's voice samples."
      - "Subhead names who it's for + how it works in one clause, keeping it SEO-aware (benefit in the first 160 chars)."

  - scenario: "Make our product page get cited by AI engines (ChatGPT, Perplexity, Gemini/AI Overviews) and rank better on Google. Tell us exactly what to change."
    must_include:
      - "Distinguishes SEO (rank in Google/Bing results) from GEO (get cited inside an AI answer) and states GEO sits on top of SEO — do both."
      - "Recommends the proven GEO moves: cite sources, add statistics, add quotations, authoritative tone — and warns keyword stuffing LOWERS AI citation."
      - "Specifies JSON-LD / schema and on-page structure (one <h1>, query-answering subheads, title 50-60 chars, meta description 120-160, benefit in first 160 chars) — as a spec, deferring the React/Metadata render to nextjs."
      - "Never fabricates the stat/quote that earns the lift; marks gaps [[NEEDS PROOF]] and asks the user to source them."
      - "Mentions crawler reality: search/citation bots (OAI-SearchBot, Claude-SearchBot, PerplexityBot) vs training crawlers (GPTBot, ClaudeBot) are controlled independently in robots.txt."
      - "Suggests an audit-first step (e.g. scripts/seo_audit.py on the URL) before prescribing changes."
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall