---
name: justinbao19-seo-blog-writer
description: "Research, write, and edit natural English or Chinese SEO articles and directory collections for a specified website."
metadata:
  decimalai-skill-id: "3717f1f4-d504-484c-8c98-82d2ce915494"
  decimalai-version-id: "e67726bb-32b2-4c1a-b850-eebf5ed48d92"
  decimalai-version: "3"
  decimalai-body-sha256: "5f6e42f8451144ed1c2e3cd175f0441a4c1665759abcbad8d6fac8aadd2a7dc7"
  decimalai-name: "justinbao19/seo-blog-writer"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "marketing"
  decimalai-source: "https://app.decimal.ai/s/justinbao19-seo-blog-writer@3/SKILL.md"
---
# Researched SEO articles and collections

Turn a topic and target website into a fact-supported article or directory collection that answers a clear search intent. Use existing product context and the requested mode; infer routine editorial choices. Complete research, drafting, correction, and the requested local package without an automatic discovery/outline approval gate.

Write for a particular reader, publication, and language. Let the reader's question and the available evidence determine the article's shape; do not force keyword placement, word counts, FAQ sections, or a generic voice. For substantial English writing, study the target site's published work and, when useful, a few genre-matched editorial examples. Learn their editorial moves, not their sentences. For Chinese, write in natural Chinese from the underlying facts and reader need; when localizing an English draft, preserve meaning and evidence while rebuilding syntax and examples for the Chinese reader. Read [voice editing](references/voice-editing.md) before any full English or Chinese article or style revision.

For topic or brief-only requests, deliver that output. For full articles, continue to the final artifact and relevant QA. Ask only about consequential ambiguity, missing access, or an explicit review checkpoint. Use tools actually available in this session; do not assume an external agent runtime or change permissions to follow an example.

Keep factual evidence traceable. Do not invent keyword volumes, source quotations, competitor features, measured rankings, or traffic forecasts. Mark estimates and unresolved evidence. Blocked search or optional SERP tooling can reduce coverage without blocking a useful, accurately scoped result.

Save substantial research and draft milestones for resumption. After interruption, inspect existing artifacts and continue from what remains. Validate the finished artifact and changed areas; repair concrete failures, stopping after required checks pass. Do not run mechanical write/read cycles after every paragraph.

Choose references by the work needed; do not load all phases at once:

- Product context, search intent, or competitive discovery: [site research](references/site-research.md).
- Research brief or article specification: [brief](references/research-brief.md).
- Full drafting: [drafting](references/drafting.md).
- Brand voice, English prose, or Chinese localization: [voice editing](references/voice-editing.md).
- Article, evidence, and link checks: [quality checks](references/quality-checks.md).
- Files, schema, and delivery package: [delivery](references/delivery.md).
- Tool failures and unavailable sources: [recovery](references/recovery.md).
- Concrete format examples when needed: [examples](references/examples.md).

The existing blog format requires embedded images and cover assets to be genuine WebP files with valid references and descriptive text; preserve original source/provenance. Run that check when images or their references change and at final image QA. Respect a user-specified destination's different format contract.

Use the user/environment output directory when supplied; otherwise use `seo-output/<slug>/` in the task workspace. Drafting and packaging alone do not authorize publishing, external uploads, or recurring promotion. Report the actual validation and remaining limitations, without promising rankings or claiming a local package is published.