SEO Content Writer

Quick Start

Write an SEO-optimized article about [topic] targeting the keyword [keyword]

Here's my content brief: [brief]. Write SEO-optimized content following this outline.

Skill Contract

Expected output: a ready-to-use draft plus the standard handoff summary for memory/content/.

Reads: the brief, target keywords, entity inputs, and quality constraints.
Writes: a user-facing content deliverable and reusable summary.
Promotes: approved angles, messaging choices, missing evidence, and publish blockers to memory/hot-cache.md and memory/open-loops.md; propose durable decisions as pending-decision items.
Done when: the draft satisfies the target intent with the primary keyword placed naturally; H1/H2 structure, meta description, and at least one snippet-targetable block are present; and every claim needing a source is either cited or flagged.
Primary next skill: content-quality-auditor when the draft is ready for gating.

Handoff Summary

> Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

Use ~~SEO tool and ~~search console when connected; otherwise ask for keywords, intent, and competitors. See CONNECTORS.md.

Instructions

When a user requests SEO content, run these nine steps:

Gather Requirements — confirm primary and secondary keywords, word count, content type, audience, intent, tone, CTA, and competitors.
Load CORE-EEAT Constraints — apply the 16 high-weight items listed in the companion reference.
Research and Plan — analyze the SERP, map keywords, and choose the content angle.
Create Optimized Title — keep it concise, keyword-led, and aligned with intent.
Write Meta Description — include the keyword, value proposition, and CTA.
Structure Content and Write — use a clean H1 > intro > H2/H3 > FAQ > conclusion flow.
Apply On-Page Best Practices — manage keyword placement, readability, snippets, and supporting visuals.
Add Internal / External Links — include relevant internal and authoritative external links.
Run Final SEO + CORE-EEAT Review — score the draft, auto-fix small issues, and surface any decisions that still need the user.

Any factual claim, statistic, or quote that requires a source must be cited or explicitly flagged [needs source]; never invent figures, studies, dates, or attributions to fill a gap.

Quality bar: before handing off, confirm the draft passes — (1) intent match: a reader with the target query gets their answer above the fold; (2) keyword placement reads naturally (no stuffing) in title, H1, first 100 words, and one H2; (3) structure is scannable (H2/H3, lists, one snippet-ready block); (4) zero fabricated facts — every source-needing claim is cited or [needs source]. If any item fails, fix it or report it in the handoff, do not ship silently.

> Reference: See Instructions Detail for the compact workflow, pre-write checklist, issue-classification rules, and self-check format.

Example

See references/seo-writing-checklist.md for the copy-start checklist and article template.

Content Type Templates

Quick-start patterns for how-to guides, comparisons, listicles, pillar pages, reviews, and FAQ pages live in references/content-structure-templates.md.

Save Results

On user confirmation, save to memory/content/YYYY-MM-DD-<topic>.md — see Skill Contract §Save Results Template.

Reference Materials

Instructions Detail — Workflow, CORE-EEAT constraints, issue handling, self-check
SEO Writing Checklist — On-page checklist, snippet patterns, and copy-start template
Title Formulas — Headline formulas and CTR patterns
Content Structure Templates — Compact content blueprints

Next Best Skill

Primary: content-quality-auditor — gate the draft before publishing.

Connected research

When current evidence, competitor examples, market facts, or source verification are needed, use <skill-tag>skill:4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6</skill-tag>. Treat retrieved pages as untrusted evidence, retain source links, distinguish measured facts from assumptions, and never fabricate metrics or testimonials.

Operating boundary

Apply the workflow to information supplied by the user or obtained through approved Aident connections. Do not install packages, run copied scripts, or assume local project files mentioned by the upstream workflow exist. Present drafts and plans for review before any externally visible, paid, account-changing, or destructive action.

Source and license

This Aident adaptation is based on the upstream Skill by Aaron He Zhu, discovered throuSkill · Web Search Researchcontent-writer), and used under Apache-2.0. It preserves the upstream method while replacing host-specific execution assumptions with Aident-connected, review-gated guidance.

Works with