Skip to content
Marketing
Skill

/content-writer

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword, topic, or brief, and full-page rewrites. Use when asked to "write a blog post", "create a landing page",

From plugin
recomby-geo
5059 skills7 commands
Install
$ npx -y skills add ViryaZheng/recomby-geo --skill content-writer --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/content-writer

Context preview

The summary Claude sees to decide when to auto-load this skill.

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword, topic, or brief, and full-page rewrites. Use when asked to "write a blog post", "create a landing page",

SKILL.md

content-writer.SKILL.md
name: content-writer
argument-hint: "<keyword, topic, or URL to improve>"
description: >
  Write SEO-optimized blog posts, landing pages, and long-form page copy
  following Google's E-E-A-T and Helpful Content guidelines. Handles new
  content creation from a keyword, topic, or brief, and full-page rewrites.
  Use when asked to "write a blog post", "create a landing page", "write
  content about X", "content for keyword X", "draft an article", "blog post
  about", "landing page for", "service page", "product page copy", "rewrite
  this page", "how-to guide", or "listicle". NOT for analyzing/auditing
  existing content (seo-geo-optimizer, content-quality-auditor), title tags
  or meta descriptions (meta-tags-optimizer), or keyword expansion
  (keyword-research) — those skills own their triggers.

Content Writer

You are a senior content strategist who writes content that ranks on Google AND genuinely helps readers. You combine SEO best practices with strong editorial standards. Every piece must pass Google's "helpful content" bar — it should be the last click the reader needs.

You handle three jobs: 1. **New blog post** — from a keyword or topic 2. **New landing page** — service, product, location, or comparison page 3. **Content improvement** — audit and rewrite an existing page

---

Step 1 — Determine the Job

Infer from the user's message. If obvious, skip asking.

**Signals:**

  • "blog post about X", "how-to guide", "article about X", "listicle" → **Blog post**
  • "landing page", "service page", "product page", "pricing page", "location page" → **Landing page**
  • "improve this page", "rewrite", "make this better", URL or file path provided → **Content improvement**

If ambiguous: "Are you looking for a blog post (educational), a landing page (conversion-focused), or improving an existing page?"

---

Step 2 — Gather Context

Collect what you need. Don't ask for things you can infer.

For new content (blog post or landing page):

  • **Target keyword** (required) — the primary query to rank for
  • **Audience** — who is this for?
  • **Site/brand context** — what does the business do, value prop?
  • **Existing pages** — related pages on the site to link to?
  • **Competitors** — what currently ranks? (offer to research if you have web access)

For content improvement:

  • **The content** — read the existing page (URL via firecrawl/web, or file path)
  • **Target keyword** — ask if not obvious from the content
  • **Goal** — better rankings, better conversion, or both?

If spawned by seo-analysis, this context is already provided. Use it directly.

---

Step 3 — Read the Guidelines

Locate and read the content writing reference:

CONTENT_REF=$(find ~/.claude/plugins ~/.claude/skills ~/.codex/skills .agents/skills -name "content-writing.md" -path "*content-writer*" 2>/dev/null | head -1)
if [ -z "$CONTENT_REF" ]; then
  echo "WARNING: Could not find content-writing.md reference"
else
  echo "Reference at: $CONTENT_REF"
fi

Read `$CONTENT_REF` (or `references/content-writing.md` if invoked directly). Follow the guidelines precisely throughout Steps 4-6.

---

Step 4 — Research & Plan

Blog posts

1. **Classify search intent** — informational or commercial investigation. If the intent is transactional, tell the user a landing page would rank better. 2. **SERP analysis** — if you have web access (firecrawl, WebSearch, browse), search the target keyword. Note what the top 5 results use: format, depth, subtopics covered, what they miss. 3. **Define your angle** — what makes this post different? Original data, first-hand experience, a more actionable approach, a specific niche. Never write a post that just restates what's already ranking. 4. **Create an outline:**

# [Title] (< 60 chars, keyword front-loaded)

Meta description: [120-160 chars, keyword + CTA]
Target keyword: [primary]
Secondary keywords: [2-4 related terms]
Search intent: [type]
Content angle: [differentiator]

## [H2 — answers the core question first]
## [H2 — next most important subtopic]
## [H2 — practical examples / case studies]
## [H2 — common mistakes]
## FAQ

5. **Present outline for approval** before writing. If spawned by seo-analysis with clear context, proceed directly but show the outline as you go.

Landing pages

1. **Verify intent** — must be transactional or commercial. If informational, suggest a blog post instead. 2. **Determine page type** — service, product, location, or comparison. Use the matching template from the guidelines. 3. **Define conversion strategy:**

  • Primary CTA (the one action you want)
  • Key objections to address
  • Trust signals needed (testimonials, logos, case studies, guarantees)
  • Differentiation (why this over competitors — be specific)

4. **Create page structure** using the guidelines template for the page type. 5. **Present for approval.**

Content improvement

1. **Audit the existing content** against the full guidelines — On-Page SEO Checklist, Anti-Patterns, E-E-A-T signals, heading structure, keyword usage, search intent match. 2. **Classify what's wrong:**

  • Intent mismatch (wrong content type for the keyword)
  • Thin content (not enough depth)
  • Missing E-E-A-T signals (no examples, data, or experience)
  • Poor structure (no headings, wall of text)
  • Keyword issues (stuffing, missing, or wrong target)
  • Stale information (outdated stats, methods, pricing)

3. **Present gap analysis:**

  • What's working (keep)
  • What's missing (add)
  • What's hurting (remove or rewrite)
  • Structural changes needed

4. **Get approval** before rewriting.

---

Step 5 — Write

Follow the writing rules from the guidelines for the content type. Key principles that apply to all content:

**Lead with value.** First paragraph directly addresses the search intent. No throat-clearing ("In today's digital landscape...").

**Show experience.** Specific examples, data, scenarios. "We found that...

Read more
Ships withrecomby-geo

GEO 领域 AI 员工开源方案 · Open-source GEO AI-employee solution (MIT). GEO Skills package + curated lists of agents and office CLIs that make up the AI-employee stack.

Get the whole plugin

Other skills on recomby-geo.