OpenSkillIndex← back to search
claude-code

Brandedflow content-writer

Write SEO-optimized blog posts, email sequences, social captions, and landing page copy. Applies E-E-A-T principles and brand voice. Use when the user needs written content output.

install
source · Clone the upstream repo
git clone https://github.com/JenCW/brandedflow
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/JenCW/brandedflow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.cursor/skills/content-writer" ~/.claude/skills/jencw-brandedflow-content-writer-3d5c6b && rm -rf "$T"
manifest: .cursor/skills/content-writer/SKILL.md
source content

Content Writer

When to Use

  • Blog posts, articles, or long-form content
  • Email sequences (cold, nurture, onboarding)
  • Social media captions (LinkedIn, Instagram)
  • Landing page or website copy
  • Case studies or testimonials

Process

  1. Load brand voice — Read 
    foundation/identity/
    and 
    foundation/brand/
    for tone, audience, and positioning.
  2. Define the piece — Confirm: format, audience, goal, CTA, word count.
  3. Apply E-E-A-T — Experience + Expertise + Authoritativeness + Trust signals in every piece.
  4. Structure first — Outline before writing. H1 → H2s → body → CTA.
  5. Write — Draft full content. No filler. Every sentence earns its place.
  6. SEO check — Primary keyword in H1, meta description (150-160 chars), internal link opportunities.

Brand Voice (BrandedFlow Default)

  • Tone: Direct, confident, systems-minded. Not fluffy.
  • Audience: Custom home builders ($5M+ homes), Southern California.
  • Avoid: Jargon overload, corporate speak, vague promises.
  • Use: Specific outcomes, builder language, trust through specificity.

Email Sequence Structure

Email 1 (Day 0): Welcome / value delivery
Email 2 (Day 2): Problem + proof
Email 3 (Day 5): Case study or testimonial
Email 4 (Day 8): Objection handling
Email 5 (Day 12): Soft offer
Email 6 (Day 16): Urgency / hard close

Output Format

Deliver in markdown. Include:

  • Title / subject line (+ 2 alternatives)
  • Meta description (if web content)
  • Full body
  • CTA

End of Task

State: "END-OF-TASK: Directive [N/A]. Self-annealing [N/A]."