Awesome SEO Writing Skill

---
name: writer
description: SEO-friendly article writing, audit, and humanization workflow for Markdown content. Use when creating, outlining, editing, auditing, rewriting, or quality-checking blog posts, tutorials, comparisons, listicles, explainers, FAQ sections, excerpts, SEO titles, meta descriptions, tags, or Google-friendly content briefs that need clear topics, natural keyword use, on-page SEO review, reader-friendly prose, and iterative optimization.
---

# Writer

## Overview

Use this skill to produce and improve Google SEO-friendly articles that stay focused on one topic, use keywords naturally, and avoid invented facts or over-marketing. Default output language should match the user's request unless they specify another language.

When the requested destination is a Chinese WeChat Official Account (微信公众号、微信文章、公众号推文), load `wechat-writer/SKILL.md` and follow that workflow instead of applying this Google-first structure. When the destination is a LinkedIn Article, newsletter, LinkedIn long-form post, or LinkedIn thought-leadership package, use `linkedin-writer/SKILL.md`; its output contract overrides this file and stores the package under `linkedin-writer/output/<article-slug>/`. When the destination is Medium or another editorial third-party article, use `medium-writer/SKILL.md`; its output contract stores the package under `medium-writer/output/<story-slug>/`.

For a full reusable prompt and final article template, load `references/seo-article-template.md` when the user asks for a ready-to-copy prompt, a complete article, or a reusable writing template.

For article audits, existing-page reviews, or post-draft optimization, load `references/seo-audit-checklist.md`.

For fact-heavy articles, comparisons, product/category analysis, or style polishing, load `references/fact-check-and-style.md`.

After the SEO audit and audit-driven rewrite, load `references/humanization.md` for the final humanization pass. Preserve verified facts, search intent, required keywords, citations, code, URLs, and the author's voice while removing mechanical or overly AI-like writing patterns.

For deliverables that must be saved as files, use the output rules in this file and load `references/output-packaging.md`.

Cloudflare R2 is optional. Always create the article with local relative image paths first. If `writer/config/r2.config.json` exists and contains valid values, load `references/r2-image-upload.md`, upload the images, and replace the local paths with public URLs. If that local config is absent, keep the local image references and finish normally.

For Cloudflare R2 credential handling and leak-prevention rules, load `references/r2-security.md`.

## Article Task Card

Before outlining or writing, create or infer a task card in 10 lines or fewer:

- Target reader: beginner, industry practitioner, or potential customer.
- Article type: how-to, comparison, listicle, or explainer.
- Main keyword: one primary keyword.
- Supporting keywords: 3 to 5 related keywords unless the user provides more.
- Target length: usually 800 to 1500 words.
- Tone: objective, editorial, restrained, and low-hype.
- Must include: at least 3 subheadings, 1 conclusion, and 3 FAQ items.
- Must avoid: fake data, fake quotes, unsupported claims, and excessive sales language.
- Optional CTA: link and anchor text if provided.
- Output format: Markdown unless the user asks otherwise.

If critical inputs are missing, make conservative assumptions and show them in the task card. Ask a question only when the topic, audience, or article type is too ambiguous to proceed safely.

## Workflow