aaron-he-zhu/aaron-marketing-skills / seo-geo/implement/content-writer
content-writer
VerifiedUse 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 keywords, headers, snippets, and evidence boundaries; refresh scores decay, prioritizes update work, and produces a republish plan with GEO guidance. Not for AI-citation/GEO readiness scoring — use geo-content-optimizer; not for publish-gate scoring — use content-quality-auditor. SEO文章写作/内容更新/排名恢复
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.4 KB |
| references/content-decay-signals.md | markdown | 4.1 KB |
| references/content-structure-templates.md | markdown | 3.4 KB |
| references/instructions-detail.md | markdown | 4.5 KB |
| references/refresh-example.md | markdown | 3.3 KB |
| references/refresh-templates.md | markdown | 5.4 KB |
| references/seo-writing-checklist.md | markdown | 3.6 KB |
| references/title-formulas.md | markdown | 4.0 KB |
references/content-structure-templates.md
View on GitHub# Content Structure Templates
Compact blueprints for common SEO formats. Replace placeholders, keep the primary keyword in the H1 and first 100 words, and remove sections that do not match intent.
## Shared Build Rules
| Element | Include |
|---------|---------|
| Opening | Hook, problem, promise, primary keyword early |
| Proof | Data, examples, quotes, first-hand experience, or source/date citations |
| Structure | Clear H2/H3 hierarchy, short paragraphs, tables only for decisions |
| GEO | 40-60 word definition block, quotable takeaways, FAQ for long-tail retrieval |
| Links | 3-5 internal links and 2-3 authoritative external links unless format needs more |
| Ending | Recap, recommendation, and one next step or CTA |
## Blueprint Matrix
| Format | Goal | Required sections |
|--------|------|-------------------|
| Blog post | Informational ranking | H1, intro, definition, why it matters, main sections, mistakes, FAQ, conclusion |
| Comparison | Help reader choose | Quick verdict, comparison table, option summaries, category winners, pricing, final verdict |
| Listicle | Rank for `best [topic]` | Summary table, criteria, repeated item cards, comparison, top pick |
| How-to | Teach process | Tools/time/skill level, numbered steps, examples, troubleshooting, FAQ |
| Product review | Buyer decision | Testing context, overview, pros/cons, features, performance, pricing, competitor comparison, verdict |
| Pillar page | Cluster hub | TOC, fundamentals, subtopics, tactics, examples, FAQ, resources |
| FAQ page | Question ranking and FAQ rich results | Intro, grouped questions, direct answers, advanced questions, CTA |
## Copy-Start Matrix
| Format | Minimal starter |
|--------|-----------------|
| Blog post | `# [Keyword]: [Benefit]` -> hook -> `## What Is [Topic]?` -> 40-60 word definition -> main sections -> mistakes -> FAQ -> conclusion |
| Comparison | `# [A] vs [B]` -> quick answer -> feature/pricing tables -> category winners -> choose A/B criteria -> verdict |
| Listicle | `# [Number] Best [Items] for [Audience]` -> summary table -> criteria -> repeated item cards -> comparison -> top pick |
| How-to | `# How to [Goal]` -> tools/time/level -> steps -> examples -> troubleshooting -> FAQ -> next step |
| Product review | `# [Product] Review` -> testing context -> performance results -> pros/cons -> features -> pricing/competitors -> buyer fit -> verdict |
| Pillar page | `# [Topic]: Complete Guide` -> TOC -> fundamentals -> subtopics -> frameworks -> FAQ -> resources |
| FAQ page | `# [Topic]: Frequently Asked Questions` -> grouped questions -> concise answers -> comparison/pricing -> CTA |
## Section Blocks
| Block | Pattern |
|-------|---------|
| Definition | 40-60 words, direct answer, source/date when factual |
| Summary table | Key decision fields only; avoid decoration |
| Proof callout | `Key insight: [stat/claim + source/date]` |
| FAQ answer | 40-60 words; answer first, detail second |
| CTA | One next step tied to search intent |
## Implementation Checklist
- [ ] Replace placeholders and remove irrelevant sections.
- [ ] Put the primary keyword in H1 and first 100 words.
- [ ] Use secondary keywords naturally in H2/H3s.
- [ ] Add proof, examples, source/date citations, or data.
- [ ] Include FAQ and definition blocks when useful for GEO retrieval.
- [ ] Add internal/external links and descriptive image alt text.
- [ ] Include affiliate disclosure when applicable.
- [ ] Finish with meta title and description matching the final angle.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |