メニュー
Write SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作/内容优化
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rome-os/rome-apps --skill seo-content-writerコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use for creative/product/design work before implementation. Guides the guardian from rough idea to approved design spec.
Senior engineer code review workflow — whole-picture understanding, mandatory beyond-the-diff verification, architecture-level review (SSOT, Occam's razor), SOLID, security, performance, and code quality, with P0-P3 severity classification.
Fetch GitHub pull request diffs with gh CLI, including large-PR fallback strategies.
SKILL.md を表示中
| name | seo-content-writer |
| description | Write SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作/内容优化 |
| version | 6.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code ≥1.0, skills.sh marketplace, ClawHub marketplace, Vercel Labs skills ecosystem. No system packages required. Optional: MCP network access for SEO tool integrations. |
| homepage | https://github.com/aaron-he-zhu/seo-geo-claude-skills |
| metadata | {"author":"aaron-he-zhu","version":"6.0.0","geo-relevance":"medium","tags":["seo","content-writing","blog-writing","seo-copywriting","content-creation","featured-snippet-optimization","article-writing","landing-page","surferSEO-alternative","clearscope-alternative","SEO文章","博客写作","SEOライティング","SEO글쓰기","redaccion-seo"],"triggers":["write SEO content","create blog post","write an article","content writing","draft optimized content","write for SEO","SEO copywriting","blog writing","write me a blog post","write me an article","help me write about","draft an article about","I need a blog post","create content for my site","how do I write content that ranks","how to write SEO friendly content","what makes content rank well","SurferSEO alternative","Clearscope alternative","Jasper AI alternative for SEO","SEO文章写作","SEO内容创作","博客写作","内容优化","内容创作","帮我写文章","写一篇博客","排名上不去","帮我写SEO文章","写一篇SEO文章","SEOライティング","SEO記事作成","ブログ記事作成","SEOコンテンツ","SEO 글쓰기","블로그 작성","SEO 콘텐츠 작성","블로그 글 작성해줘","이 주제로 글 써봐","redacción SEO","escribir artículo SEO","contenido optimizado","redação SEO","escrever artigo SEO","SEO copywritting","writting SEO content"]} |
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This build skill follows the shared Skill Contract and State Model.
This skill creates search-engine-optimized content that ranks well while providing genuine value to readers. It applies proven SEO copywriting techniques, proper keyword integration, and optimal content structure.
System role: Build layer skill. It turns briefs and signals into assets that other skills can review, publish, and monitor.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs a shippable asset or transformation that should feed directly into quality review, deployment, or monitoring.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Write an SEO-optimized article about [topic] targeting the keyword [keyword]
Create a blog post for [topic] with these keywords: [keyword list]
Write a 2,000-word guide about [topic] targeting [keyword],
include FAQ section for featured snippets
Here's my content brief: [brief]. Write SEO-optimized content following this outline.
Expected output: a ready-to-use asset or implementation-ready transformation plus a short handoff summary ready for memory/content/.
memory/content/.CLAUDE.md, memory/decisions.md, and memory/open-loops.md.Next Best Skill below when the asset is ready for review or deployment.See CONNECTORS.md for tool category placeholders.
With ~~SEO tool + ~~search console connected: Automatically pull keyword metrics (search volume, difficulty, CPC), competitor content analysis (top-ranking pages, content length, common topics), SERP features (featured snippets, PAA questions), and keyword opportunities (related keywords, question-based queries).
With manual data only: Ask the user to provide:
Proceed with the full workflow using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
When a user requests SEO content:
Gather Requirements
Confirm or ask for:
### Content Requirements
**Primary Keyword**: [main keyword]
**Secondary Keywords**: [2-5 related keywords]
**Target Word Count**: [length]
**Content Type**: [blog/guide/landing page/etc.]
**Target Audience**: [who is this for]
**Search Intent**: [informational/commercial/transactional]
**Tone**: [professional/casual/technical/friendly]
**CTA Goal**: [what action should readers take]
**Competitor URLs**: [top ranking content to beat]
Load CORE-EEAT Quality Constraints
Before writing, load content quality standards from the CORE-EEAT Benchmark:
### CORE-EEAT Pre-Write Checklist
**Content Type**: [identified from requirements above]
**Loaded Constraints** (high-weight items for this content type):
Apply these standards while writing:
| ID | Standard | How to Apply |
|----|----------|-------------|
| C01 | Intent Alignment | Title promise must match content delivery |
| C02 | Direct Answer | Core answer in first 150 words |
| C06 | Audience Targeting | State "this article is for..." |
| C10 | Semantic Closure | Conclusion answers opening question + next steps |
| O01 | Heading Hierarchy | H1→H2→H3, no level skipping |
| O02 | Summary Box | Include TL;DR or Key Takeaways |
| O06 | Section Chunking | Each section single topic; paragraphs 3–5 sentences |
| O09 | Information Density | No filler; consistent terminology |
| R01 | Data Precision | ≥5 precise numbers with units |
| R02 | Citation Density | ≥1 external citation per 500 words |
| R04 | Evidence-Claim Mapping | Every claim backed by evidence |
| R07 | Entity Precision | Full names for people/orgs/products |
| C03 | Query Coverage | Cover ≥3 query variants (synonyms, long-tail) |
| O08 | Anchor Navigation | Table of contents with jump links |
| O10 | Multimedia Structure | Images/videos have captions and carry information |
| E07 | Practical Tools | Include downloadable templates, checklists, or calculators |
_These 16 items apply across all content types. For content-type-specific dimension weights, see the Content-Type Weight Table in [core-eeat-benchmark.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/core-eeat-benchmark.md)._
_Full 80-item benchmark: [references/core-eeat-benchmark.md](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/references/core-eeat-benchmark.md)_
_For complete content quality audit: use [content-quality-auditor](https://github.com/aaron-he-zhu/seo-geo-claude-skills/blob/main/cross-cutting/content-quality-auditor/SKILL.md)_
Research and Plan
Before writing:
### Content Research
**SERP Analysis**:
- Top results format: [what's ranking]
- Average word count: [X] words
- Common sections: [list]
- SERP features: [snippets, PAA, etc.]
**Keyword Map**:
- Primary: [keyword] - use in title, H1, intro, conclusion
- Secondary: [keywords] - use in H2s, body paragraphs
- LSI/Related: [terms] - sprinkle naturally throughout
- Questions: [PAA questions] - use as H2/H3s or FAQ
**Content Angle**:
[What unique perspective or value will this content provide?]
Create Optimized Title
### Title Optimization
**Requirements**:
- Include primary keyword (preferably at start)
- Under 60 characters for full SERP display
- Compelling and click-worthy
- Match search intent
**Title Options**:
1. [Title option 1] ([X] chars)
- Keyword position: [front/middle]
- Power words: [list]
2. [Title option 2] ([X] chars)
- Keyword position: [front/middle]
- Power words: [list]
**Recommended**: [Best option with reasoning]
Write Meta Description
### Meta Description
**Requirements**:
- 150-160 characters
- Include primary keyword naturally
- Include call-to-action
- Compelling and specific
**Meta Description**:
"[Description text]" ([X] characters)
**Elements included**:
- ✅ Primary keyword
- ✅ Value proposition
- ✅ CTA or curiosity hook
Structure Content and Write
Structure: H1 (primary keyword, one per page) > Introduction (100-150 words, hook + promise + keyword in first 100 words) > H2 sections (secondary keywords/questions) > H3 sub-topics > FAQ section > Conclusion (summary + keyword + CTA).
Apply On-Page SEO Best Practices
Follow the on-page SEO checklist (keyword placement, content quality, readability, technical elements) and the content writing template (H1 with keyword, hook, sections with H2/H3, FAQ, conclusion with CTA).
Reference: See references/seo-writing-checklist.md for the full on-page SEO checklist, content writing template, and featured snippet optimization patterns.
Key requirements while writing:
Add Internal/External Links
### Link Recommendations
**Internal Links** (include 2-5):
1. "[anchor text]" → [/your-page-url] (relevant because: [reason])
2. "[anchor text]" → [/your-page-url] (relevant because: [reason])
**External Links** (include 2-3 authoritative sources):
1. "[anchor text]" → [authoritative-source.com] (supports: [claim])
2. "[anchor text]" → [authoritative-source.com] (supports: [claim])
Final SEO Review and CORE-EEAT Self-Check
Score content across 10 SEO factors (title, meta description, H1, keyword placement, H2s, internal links, external links, FAQ, readability, word count) and produce an Overall SEO Score out of 10.
Then verify the 16 CORE-EEAT pre-write constraints (C01, C02, C06, C10, O01, O02, O06, O09, R01, R02, R04, R07, C03, O08, O10, E07) with pass/warning/fail status. List items needing attention.
For full 80-item audit, use content-quality-auditor
When the self-check reveals issues, classify and handle them:
Auto-correct (fix silently, then document in a ### Changes Made block after the final content):
Use this format for the Changes Made block:
### Changes Made During Self-Check
| Item | Original | Fixed |
|------|----------|-------|
| Meta description | 185 chars | 158 chars — removed non-essential qualifier |
| Keyword density | 2.4% | 1.8% — replaced 3 instances with semantic variants |
Needs your decision (ask before changing):
User: "Write an SEO-optimized article about 'email marketing best practices' targeting small businesses"
Reference: See references/seo-writing-checklist.md for the full example output demonstrating a complete SEO article with meta description, H1/H2/H3 hierarchy, statistics with citations, comparison tables, FAQ section, and conclusion with CTA.
The example output demonstrates: keyword in H1 and first 100 words, statistics with sources (DMA, Emarsys), comparison tables, bullet-point lists, pro tips, FAQ section with 40-60 word answers, and a clear CTA in the conclusion.
Write a how-to guide for [task] targeting [keyword]
Write a comparison article: [Option A] vs [Option B] for [keyword]
Write a list post: "X Best [Items] for [Audience/Purpose]" targeting [keyword]
Write an ultimate guide about [topic] (3,000+ words) targeting [keyword]
After delivering content or optimization output to the user, ask:
"Save these results for future sessions?"
If yes, write a dated summary to memory/content/YYYY-MM-DD-<topic>.md containing:
Gate check recommended: Run content-quality-auditor before publishing (PostToolUse hook will remind automatically).
If any findings should influence ongoing strategy, recommend promoting key conclusions to memory/hot-cache.md.