Skills / Departments / Marketing / Skills / Copywriting / Rmbc Advertorial
All skills

/ skill

rmbc-advertorial

Departments/Marketing/Skills/copywriting/rmbc-advertorial.md

Generate a long-form advertorial - story-led page that sits between Ad and VSL/PDP. Editorial-feeling rather than sales-pitch-feeling.

Open as raw file

Run this skill

Heads up — this skill doesn’t have a structured form yet, so type the full prompt with all decisions baked in (the subprocess can’t answer follow-up questions). Edit me if needed.

Runs with bypassPermissions — local dev only.

rmbc-advertorial

RMBC Stage 4 deliverable. Advertorial.

Use case

Pre-sell page in 'Ad -> Advertorial -> VSL -> Checkout' funnel; lead-gen in healthcare-ed.

Pre-flight

  1. brief_path exists and Brief 2.0 has all 25 sections filled (status: reviewed or approved).
  2. Read brand context: Brands/{brand_slug}/BrandContext.md, voice-profile.md, compliance.md.
  3. Read the canonical Claude Project system prompt at References/rmbc/claude-projects/04-advertorial.md - that's the load-bearing prompt. Follow it.
  4. Read PLAYBOOK.md sections 5 (VSL Structure) / 7 (Asset Matrix) for length / shape conventions.

Procedure

Follow the procedure in claude-projects/04-advertorial.md exactly. The skill blueprint here is the wrapper - that file is the substantive prompt.

Asset-specific rules

  • Editorial voice - looks like a 3rd-party article or 'discovery' story, not a sales page.
  • Hook + tease the UMP nickname in the first 200 words.
  • Native-ad shape - heavy on story, light on direct-offer language.
  • CTA to the VSL or PDP at the natural narrative climax, not at the top.

Output

Path: Brands/{brand_slug}/Marketing/drafts/{date}-advertorial-{slug}.md

Frontmatter:

---
type: copy-draft
brand: {brand_slug}
asset_type: advertorial
brief_ref: "<a class="wikilink wikilink-broken" href="#">{brief_path}</a>"
status: draft
created: YYYY-MM-DD
---

Body: outline (if asset >= medium length, request approval first) -> full draft -> editing notes (voice fit, compliance flags, specificity gaps, alternates).

Log entry

Append to Wiki/Log.md via the standard format. Include the asset type and brief reference.

Hard rules

  • No copy without an approved Brief. Period.
  • Never fabricate. If the Brief is missing data, surface the gap.
  • Cite library evidence in the editing notes when libraries were queried.

Failure modes

  • Brief sections missing or marked TBD - abort, route back to rmbc-brief.
  • Brand voice-profile / compliance still placeholder - surface as blocker.
  • Output truncated - ask user "continue"; never compress.