Use when auditing content quality, E-E-A-T, publish readiness, or 内容质量/EEAT评分. Runs 80-item CORE-EEAT scoring with veto checks and fix plan.
日本語の概要は準備中です。原文の説明を表示しています。
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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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:
Infer from the user's message. If obvious, skip asking.
Signals:
If ambiguous: "Are you looking for a blog post (educational), a landing page (conversion-focused), or improving an existing page?"
Collect what you need. Don't ask for things you can infer.
If spawned by seo-analysis, this context is already provided. Use it directly.
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.
# [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
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.
Article/BlogPosting + FAQPage if FAQ included)Service/Product/LocalBusiness + FAQPage)# [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
Before delivering, verify against every check. Fix failures before presenting.
Would the reader need to search again? If yes, the content isn't done.
Does the content type match what Google shows for this query?
Title, meta description, H1, heading hierarchy, keyword placement, internal links, image alt text, URL slug — all present and correct.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when auditing content quality, E-E-A-T, publish readiness, or 内容质量/EEAT评分. Runs 80-item CORE-EEAT scoring with veto checks and fix plan.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Entry point + orchestrator for the recomby-geo GEO (Generative Engine Optimization) workflow on OpenAI Codex CLI. Use when the user wants to run any stage of the GEO pipeline on a client folder — intake, visibility audit, content-gap analysis, content brief, draft production, distribution, or monthly re-audit — or asks to "run GEO", "audit AI search visibility", or "GEO this client". Codex has no bare slash commands, so this skill is how the 7 stages (that Claude Code runs as /01-intake … /07-reaudit) are driven on Codex. It routes to the per-stage specs in this plugin's commands/ and enforces the orchestration rules. Does not auto-fill expert content — the human-in-loop brief checkpoint is the moat.
日本語の概要は準備中です。原文の説明を表示しています。
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 staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in the browser instead of editing Markdown. Use when a brief or draft needs to go to a client/expert for review, or when building the briefs/index.html entry page for a client folder. The reviewer's input comes back as a JSON file that 04-content-brief Step 9 ingests. Visual quality is delegated to the frontend-design skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when improving internal link structure, anchor text, orphan pages, crawl depth, site architecture, or link equity flow. 内链优化/站内架构
日本語の概要は準備中です。原文の説明を表示しています。
Discover, analyze, and prioritize keywords for SEO and GEO content strategies. Identifies high-value opportunities based on search volume, competition, intent, and business relevance. Generates topic clusters and content calendars. Use when asked to "find keywords", "keyword research", "what should I write about", "keyword analysis", "find me topics to write", "search volume", "keyword difficulty", "content ideas", or any keyword discovery task.
日本語の概要は準備中です。原文の説明を表示しています。