Agent skill

Content Writer

by ViryaZheng in ViryaZheng/recomby-geo

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines.

MITAuto-check passedWriting & Content

Install Content Writer

skills CLI
$ npx skills add ViryaZheng/recomby-geo --skill content-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ViryaZheng/recomby-geo content-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ViryaZheng/recomby-geo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/recomby-geo/skills/content-writer .claude/skills/content-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-writer
GitHub stars
458
Token cost
~2.4k tokens
SKILL.md length
1,017 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines.

  • Works in 6 steps: Determine the Job → Gather Context → Read the Guidelines → …
  • Asked to write a blog post
  • SKILL.md covers Step 1 — Determine the Job, Step 2 — Gather Context, Step 3 — Read the Guidelines and Step 4 — Research & Plan, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Content Writer is an agent skill from ViryaZheng/recomby-geo. 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…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/content-writing.md`).

It sits in Writing & Content, covering Blog and article writing, Landing pages and On-page SEO. The repository describes itself as: 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. The licence is MIT.

When your agent uses it

  • Asked to write a blog post
  • Create a landing page
  • Write content about X
  • Content for keyword X

Example prompts

  • “write a blog post”
  • “create a landing page”
  • “write content about X”
  • “/content-writer”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Determine the Job
  2. Gather Context
  3. Read the Guidelines
  4. Research & Plan
  5. Write
  6. Quality Gate

What it can do on your machine

Read from SKILL.md and the folder at commit 530d5e2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Writer loads about 2.4k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 178 tokens; SKILL.md has 1,017 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~178
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ViryaZheng/recomby-geo at commit 530d5e2, republished under its MIT licence (© ViryaZheng). 1,017 words, ~2,388 tokens.

Download SKILL.mdSave it as .claude/skills/content-writer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
content-writer
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.
argument-hint
<keyword, topic, or URL to improve>

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:

bash
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
  1. 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.

Show full SKILL.md (446 more words)Show less

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..." and "In our testing..." signal first-hand knowledge. If the site has its own data, weave it in.

Be concrete. Every recommendation includes the what, why, and how. "Add a sticky CTA bar — we saw a 23% increase on mobile" not "improve your CTAs."

Structure for scanning. Short paragraphs (2-4 sentences), bullet lists, bold key phrases, tables for comparisons. One idea per paragraph.

Keyword placement. Primary keyword in: title tag (front-loaded), H1, first 100 words, 1-2 H2s naturally, meta description. After that: synonyms and natural language. No stuffing.

Deliverables for blog posts:
  1. Full post in markdown with heading hierarchy (H1 → H2 → H3)
  2. SEO metadata: title tag (< 60 chars), meta description (120-160 chars), URL slug
  3. JSON-LD structured data (Article/BlogPosting + FAQPage if FAQ included)
  4. Internal linking plan (pages to link to and from)
  5. Publishing checklist
Deliverables for landing pages:
  1. Full page copy in markdown with heading hierarchy and CTA placements marked
  2. SEO metadata: title tag, meta description, URL slug
  3. Conversion strategy: primary CTA, objections addressed, trust signals
  4. JSON-LD structured data (Service/Product/LocalBusiness + FAQPage)
  5. Internal linking plan + navigation placement suggestion
  6. Publishing checklist
Deliverables for content improvement:
  1. Rewritten content in markdown (full replacement, not patches)
  2. Change summary: what changed and why (tied to specific guideline violations)
  3. Updated SEO metadata if needed
  4. Updated structured data if needed
Output Format
# [Content Type]: [Title]

## SEO Metadata
- **Title tag:** [< 60 chars]
- **Meta description:** [120-160 chars]
- **URL slug:** /[slug]
- **Target keyword:** [primary]
- **Secondary keywords:** [list]

## Content
[Full content in markdown with proper heading hierarchy]

## Structured Data
[JSON-LD ready to paste]

## Internal Linking Plan
- **Link TO this page from:** [existing pages + suggested anchor text]
- **This page links to:** [internal links in the content]

## Publishing Checklist
- [ ] Title tag and meta description set
- [ ] URL slug configured
- [ ] Structured data added
- [ ] Internal links placed (both directions)
- [ ] Open Graph image added
- [ ] Canonical URL set to self
- [ ] Mobile rendering verified

Step 6 — Quality Gate

Before delivering, verify against every check. Fix failures before presenting.

The "Last Click" Test

Would the reader need to search again? If yes, the content isn't done.

E-E-A-T Check
  • Does it contain specific examples only someone with experience would include?
  • Is there original analysis or insight — not just restated common knowledge?
  • Are claims backed by sources or data?
Anti-Pattern Check (from guidelines)
  • No keyword stuffing
  • No filler paragraphs (every paragraph earns its place)
  • No generic AI hedging ("it depends", "many factors" without committing)
  • No wall of text (headings, bullets, bold key phrases throughout)
  • No duplicate intent with existing pages on the site
Format Match

Does the content type match what Google shows for this query?

On-Page SEO (from guidelines checklist)

Title, meta description, H1, heading hierarchy, keyword placement, internal links, image alt text, URL slug — all present and correct.

Landing Page Extra Checks
  • Would you convert after reading this? What's missing if not?
  • Are vague claims replaced with specifics?
  • Is every major objection addressed?
  • Is the CTA immediately clear?

© ViryaZheng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/recomby-geo/skills/content-writer of ViryaZheng/recomby-geo.

  • SKILL.md
  • evals/evals.json
  • references/content-writing.md

Open the folder on GitHubat commit 530d5e2

Compare with similar skills

Content Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Writer this skillViryaZheng/recomby-geo458—~2.4kAutomated safety check: PassMIT
SEO Content Writerthatrebeccarae/claude-marketing161—~1.1kAutomated safety check: PassMIT
Content Writeraaron-he-zhu/aaron-marketing-skills2.9k—~3.6kAutomated safety check: PassApache-2.0
H1thedaviddias/Front-End-Checklist74k—~734Automated safety check: PassMIT
Webinar Content And Eventsmanojbajaj95/claude-gtm-plugin105—~3.5kAutomated safety check: PassMIT
Content Writerdageno-agents/geo-content-writer215—~1.2kAutomated safety check: PassMIT

Similar skills

  • SEO Content Writer

    thatrebeccarae/claude-marketing

    SEO-optimized content creation with brand voice analysis and platform-specific frameworks.

    161 GitHub stars~1.1k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • Content Writer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with…

    2.9k GitHub stars~3.6k tokensUpdated today
    Marketing & SEOAuto-check passed
  • H1

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.

    74k GitHub stars~734 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed
  • Webinar Content And Events

    manojbajaj95/claude-gtm-plugin

    This skill covers two related use cases: (1) Creating high-converting webinar registration and event landing pages, and (2) Repurposing webinar recordings into multiple content assets including blog…

    105 GitHub stars~3.5k tokensUpdated 22 days ago
    Writing & ContentAuto-check passed
  • Content Writer

    dageno-agents/geo-content-writer

    A skill your agent uses when the user wants to turn [Dageno](https://dageno.ai/?utmsource=github&utmmedium=social&utmcampaign=official) GEO opportunities into a real-fanout backlog and then write…

    215 GitHub stars~1.2k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Writing & ContentAuto-check passed

More from ViryaZheng/recomby-geo

  • Meta Tags Optimizer

    ViryaZheng/recomby-geo

    Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate.

    458 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Geo Review HTML

    ViryaZheng/recomby-geo

    Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer…

    458 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed
  • Internal Linking Optimizer

    ViryaZheng/recomby-geo

    A skill your agent uses when improving internal link structure, anchor text, orphan pages, crawl depth, site architecture, or link equity flow.

    458 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed
  • Keyword Research

    ViryaZheng/recomby-geo

    Discover, analyze, and prioritize keywords for SEO and GEO content strategies.

    458 GitHub stars~2.6k tokensUpdated 3 mo ago
    Auto-check passed
  • Content Quality Auditor

    ViryaZheng/recomby-geo

    A skill your agent uses when auditing content quality, E-E-A-T, publish readiness, or 内容质量/EEAT评分.

    458 GitHub stars~8k tokensUpdated 3 mo ago
    Auto-check passed
  • Geo Pipeline

    ViryaZheng/recomby-geo

    Entry point + orchestrator for the recomby-geo GEO (Generative Engine Optimization) workflow on OpenAI Codex CLI.

    458 GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Content Writer

What does Content Writer do?

Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines. Content Writer is an agent skill from ViryaZheng/recomby-geo. Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines.

When should I use Content Writer?

Content Writer fits situations like: asked to write a blog post; create a landing page; write content about X; content for keyword X.

How do I install Content Writer in Claude Code?

Run `npx skills add ViryaZheng/recomby-geo --skill content-writer -a claude-code`. Or copy the skill folder (plugins/recomby-geo/skills/content-writer in ViryaZheng/recomby-geo) into .claude/skills/content-writer in your project. Claude Code loads it when a task matches its description.

How do I install Content Writer in Codex?

Run `npx skills add ViryaZheng/recomby-geo --skill content-writer -a codex`. Or copy the skill folder (plugins/recomby-geo/skills/content-writer in ViryaZheng/recomby-geo) into .agents/skills/content-writer in your project. Codex loads it when a task matches its description.

Can I use Content Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ViryaZheng/recomby-geo --skill content-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-writer, .gemini/skills/content-writer, .github/skills/content-writer and .opencode/skills/content-writer in your project.

What does Content Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: Content Writer is instructions for the agent only.

Does Content Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Content Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Content Writer use?

Content Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Writer use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Content Writer?

Skills that share tags, products or a category with Content Writer: SEO Content Writer (thatrebeccarae/claude-marketing, 161 stars), Content Writer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), H1 (thedaviddias/Front-End-Checklist, 74k stars) and Webinar Content And Events (manojbajaj95/claude-gtm-plugin, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Writer?

ViryaZheng (a GitHub user) maintains it in ViryaZheng/recomby-geo, which has 458 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on July 4, 2026.

Source: ViryaZheng/recomby-geo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.