# English Article Body Writing

> Draft, expand, revise, and naturalize complete English SEO blog articles from an approved outline, search-intent or SERP notes, product-integration plan, FAQ questions, and confirmed facts. Use when the user asks for an English article body, English blog正文, 英文正文skill, an English SEO draft, a full article from a bilingual outline, or revision of an existing English article.

- Skill: `linsiyan780-droid/english-article-body-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add linsiyan780-droid/english-article-body-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/linsiyan780-droid/english-article-body-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: linsiyan780-droid (https://skillmd.com/u/linsiyan780-droid)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/linsiyan780-droid/english-article-body-writing

---


# English Article Body Writing

Turn an approved outline into a complete English article that answers search intent, supports reader decisions, integrates the required product naturally, and reads like clear human-written English. Use Chinese for pre-writing analysis and revision notes. Output the formal article body in English only, except for the required Chinese image-suggestion markers and bilingual alt text.

## Operating Mode

- Complete the full draft in one pass by default.
- Switch to staged drafting only when essential inputs are missing or the article is unusually long, complex, evidence-heavy, or structurally uncertain.
- When staging is necessary, explain the reason in Chinese and split work by coherent article modules rather than arbitrary word counts.
- If the user provides a writing sample, match its voice, rhythm, vocabulary, paragraph style, and punctuation where appropriate.
- Without a writing sample, use a clear, natural, credible conversational-professional voice, then adjust for the audience and subject.
- Do not force a specific regional English variant. Write normal, internally consistent English unless the user specifies a market or variant.
- Let total length follow the approved outline, search intent, topic difficulty, and the explanation needed. Do not impose a universal word count or pad the draft.

## Confirm Inputs

Use the information already provided:

- Article title and target keyword.
- Approved English or bilingual outline.
- Target reader and business context.
- Search intent and SERP learnings.
- Confirmed facts, constraints, and required terminology.
- Product or brand, URL, role, and insertion plan.
- FAQ or long-tail questions.
- User-provided or confirmed internal and external links.
- Desired tone, length, formatting, and other constraints.

Ask only for missing information that would materially change the article. If the article can be completed safely with a reasonable assumption, state the assumption briefly in Chinese and continue.

## Core Workflow

1. Identify the reader's primary problem, the immediate answer, and the decision or task the article must support.
2. Follow the approved outline, but merge, compress, relocate, or remove sections that would repeat the same answer. Do not preserve a heading solely because it appeared in the outline.
3. Write the primary intent first, then relevant secondary or latent needs such as definitions, differences, limitations, scenarios, risks, workflow, business choice, FAQ, and next steps.
4. Build useful tables, bullets, numbered steps, flows, and image suggestions where they improve scanning or understanding.
5. Integrate the required product only where the reader's problem naturally creates a need for its capability.
6. Complete the main-body close and FAQ without repeating the body.
7. Run content, language, humanization, structure, source, and formatting revisions before delivery.

## Article Structure

- Use one H1 only: the approved article title.
- Use H2s for main sections.
- Use H3s only for real subtopics or practical steps.
- Do not create a heading for one emphasized sentence; keep it in the paragraph.
- Preserve approved English headings when they remain accurate and natural.
- If a heading must change during drafting, keep its original intent, remove duplication, and maintain natural English. When the source outline came from the first-version English outline skill, preserve its confirmed heading constraints where feasible.
- Fold a simple definition into the direct-answer introduction when a standalone definition section would repeat the opening.
- Keep each paragraph focused on one main point. Vary paragraph and sentence length naturally.
- Do not add generic “Challenges,” “Future Outlook,” or “Conclusion” sections unless the topic and approved outline genuinely require them.

## Introduction

- Answer the core query quickly.
- For comparison, selection, or decision queries, give the decision shortcut or main distinction early.
- Establish only the context the reader needs to understand the answer.
- Do not begin with inflated importance, broad historical claims, generic scene-setting, “In today's fast-changing landscape,” or “Let's dive in.”
- Do not repeat the introduction as the first H2.

## Search Intent And Keywords

- Use the target keyword and close variants naturally.
- Use product names, API names, platform terms, standards, and industry terminology in their official English forms.
- Include relevant long-tail needs from the approved research or outline.
- Add business-intent terms such as pricing, limits, API, automation, CRM, software, tools, risk, compliance, and conversion only when relevant.
- Do not force every keyword into headings.
- Do not add Chinese keywords or Chinese FAQ questions to the formal English article.
- Do not repeat a keyword when a pronoun, natural synonym, or clear subject would read better. Avoid synonym cycling that makes the same subject sound inconsistent.

## Evidence, Claims, And Links

- Use confirmed facts. Never invent prices, platform limits, policies, regulations, statistics, product capabilities, tests, cases, quotes, or sources.
- Most articles do not need citations throughout. Do not create a citation plan or general source list unless the user asks for one.
- Ordinary, non-critical facts may omit external links when the user's format calls for clean copy.
- Keep an authoritative source link for important data, policies, prices, platform rules, or limitations that materially affect the reader's decision.
- Use a descriptive anchor link to the original or authoritative page when such a link has been provided or confirmed.
- If the user requests no external links, remove nonessential figures or rewrite the passage so it does not depend on an exact number or unsupported precise claim.
- Never retain an unverifiable precise statement after removing all supporting evidence.
- Use only links the user has provided or confirmed. Do not crawl a site or conduct a new internal-link search within this skill; route that work to the appropriate standalone internal-linking workflow.
- Competitor SERP content may guide coverage, but do not copy its wording, tables, examples, or paragraph logic.

## Tables, Bullets, And Flows

### Tables

- Include at least one genuinely useful table by default.
- Use a table for tool, plan, scenario, feature, advantage/disadvantage, requirement, risk, or decision-criteria comparisons when it scans better than prose.
- Keep tables compact and useful. Use clear English column labels.
- Explain only the important takeaway after a table; do not restate every cell in prose.
- If no table suits the topic, omit it and explain the reason briefly in Chinese outside the formal article.

### Bullets

- Use bullets when the content genuinely benefits from scanning.
- Good uses include key takeaways, three or more parallel scenarios, risks, benefits, limits, criteria, sub-items inside steps, checks, methods, and data findings.
- Do not use bullets for a cause-and-effect chain, a short example, a coherent argument, or only one or two points.
- Do not turn every H2 into a list or mechanically target a list density.
- Keep a bullet block internally parallel, but do not force every idea into a group of three.
- Avoid lists made of bold inline headers followed by generic explanations when ordinary prose is clearer.

### Steps And Flows

- Use numbered steps for processes the reader can follow.
- When a simple flow is central, express it as a concise sequence such as `Step 1 -> Step 2 -> Step 3 -> Result`.
- Explain decisions or conditions around the flow instead of treating the chain as a complete answer.

## Image Suggestions

- Include at least 1–2 high-value image suggestions by default.
- Add more when distinct ideas genuinely benefit from visualization. Do not add decorative images merely to increase the count.
- Provide suggestions only; do not generate images.
- Prefer comparison paths, decision trees, workflows, system relationships, scenarios, before/after states, dashboards, or essential interface screenshots.
- Do not suggest generic stock photos, decorative illustrations, logo walls, or images that merely repeat nearby prose or tables.
- Keep tables as native text rather than turning them into images.
- Place every suggestion exactly where it should appear in the article.
- Provide both English and Chinese alt text for every suggestion.
- Use this exact format:

  `[配图建议：图片类型；主要内容；帮助读者理解什么；英文 Alt 文本：……；中文 Alt 文本：……]`

- Write descriptive alt text that reflects the image's actual content and purpose. Do not stuff keywords or begin mechanically with “Image of.”
- If fewer than two relevant images exist, include the strongest one and explain in Chinese outside the formal article why additional images would be repetitive or decorative.

## Product Or Brand Insertion

Use this path:

1. Identify the reader's operational problem.
2. Explain the capability needed to solve it.
3. Present the product as one possible way to support that capability.
4. Show the workflow or outcome it enables.
5. Return to the reader's main task or decision.

Apply these rules:

- Insert the required product where the need first becomes natural.
- Mention only capabilities relevant to the current problem.
- Explain fit, workflow, limits, and next action rather than stacking features.
- State when a product complements existing tools or channels rather than replacing them.
- Do not create a standalone product H2 unless the approved outline or user explicitly requires one.
- Avoid “powerful,” “leading,” “all-in-one,” “seamless,” “revolutionary,” “perfect solution,” unsupported superiority, artificial pain points, and abrupt calls to action.
- Do not use “According to the official website...” as empty framing. State a verified capability directly when it is supported.

## FAQ And Extended Reading

- Answer questions readers may still have after the main body.
- Keep FAQ questions natural and close to how English-speaking searchers ask them.
- Give the direct answer first, then only the explanation needed.
- Remove any question already answered substantially in the body, table, bullets, product section, or close.
- Use adjacent long-tail needs such as safety, cost, account risk, missing features, setup, alternatives, and next-step tools only when relevant.
- Mention the product in an FAQ only when genuine product or solution intent supports it.
- Use only user-provided or confirmed links for extended reading.
- Prefer relevant English pages. Do not place Chinese anchor text in the formal English article.
- If new site research or internal-link discovery is required, leave that work to a standalone internal-linking workflow.

## Integrated Human-Writing Rules

Write and revise the article so it sounds human without changing its meaning or factual scope.

### Prefer

- Specific facts and concrete explanations over inflated significance.
- Simple constructions such as “is,” “has,” and active verbs when they are clearer.
- Varied sentence rhythm and paragraph length.
- Direct attribution to a named source when attribution is necessary.
- Natural uncertainty only where the evidence is genuinely uncertain.
- A neutral, plain voice for technical, legal, or reference material; more personality only when the subject and audience support it.

### Remove Or Rewrite

- Inflated symbolism, legacy claims, broader-trend filler, and claims that ordinary details are “pivotal” or “transformative.”
- Promotional language and empty superlatives.
- Superficial `-ing` clauses that pretend to add analysis.
- Vague attributions such as “experts say,” “industry reports show,” or “observers believe” without a specific basis.
- Formulaic “Despite these challenges...” sections and generic upbeat conclusions.
- Overused AI vocabulary such as “delve,” “crucial,” “pivotal,” “intricate,” “landscape,” “showcase,” “underscore,” “tapestry,” and “testament” when a simpler word is clearer.
- Copula avoidance such as “serves as,” “stands as,” “boasts,” or “represents” when “is” or “has” is more direct.
- Repeated “not only...but also,” “it's not just...,” tailing negations, and forced negative parallelism.
- Forced groups of three, false “from X to Y” ranges, synonym cycling, and excessive passive voice.
- Excessive boldface, emoji decoration, chatbot greetings, “I hope this helps,” “let me know,” knowledge-cutoff disclaimers, and servile praise.
- Filler such as “in order to,” “at this point in time,” “it is important to note,” and “has the ability to.”
- Excessive hedging, persuasive-authority phrases such as “the real question is,” and signposting such as “let's explore” or “here's what you need to know.”
- A heading followed by a one-line paragraph that merely restates the heading.
- Diff-style narration that describes what changed instead of explaining the subject as it is.

### Punctuation And Formatting

- Do not use em dashes or en dashes in the final article. Replace them with a period, comma, colon, parentheses, or a rewritten sentence.
- Avoid double hyphens used as em dashes.
- Use straight quotation marks unless the user's publishing format requires typographic quotes.
- Preserve approved heading capitalization. Otherwise prefer readable sentence case rather than mechanical Title Case for every heading.
- Use hyphens in compound modifiers when grammatically useful, but do not over-hyphenate predicate phrases.

## Whole-Article Deduplication

Compare meaning and expected takeaways across:

- Introduction and first H2.
- H2s and H3s.
- Tables and surrounding prose.
- Bullet blocks and paragraphs.
- Product passages and general recommendations.
- Main-body close and earlier sections.
- FAQ and the entire article.
- Different FAQ answers.

Merge, shorten, move, or remove repeated material. Keep brief recaps only when they support navigation, synthesis, or action, and do not repeat the same explanation, evidence, example, product claim, or recommendation at length.

## Draft And Revision Process

1. Draft the complete English article.
2. Audit content coverage, logic, repetition, product fit, table value, bullet use, images, FAQ, facts, and links.
3. Audit English spelling, grammar, agreement, articles, singular/plural forms, prepositions, tense, pronoun references, capitalization, punctuation, terminology, and consistency.
4. Audit the integrated human-writing patterns above.
5. Rewrite remaining AI-like, stiff, translated, promotional, vague, or repetitive passages.
6. Deliver only the polished final article unless the user asks to see the draft or audit. Give any pre-writing assumptions or revision summary in Chinese outside the formal English body.

## Final Checklist

- The opening answers the core query quickly.
- The article satisfies the approved outline and search intent without mechanical expansion.
- The formal body is English only, except for required Chinese image-suggestion markers and Chinese alt text.
- Total length matches the topic rather than a fixed quota.
- Headings form a complete, non-repetitive answer path.
- At least one useful table appears, or a Chinese note explains why no table fits.
- Bullets serve real scanning, evidence, method, or decision needs.
- At least 1–2 valuable image suggestions appear by default, with more when justified; every suggestion includes English and Chinese alt text in the exact required format.
- Product insertion follows a real reader need and does not sound like a landing page.
- FAQ does not duplicate the body.
- Important decision-changing claims retain authoritative support when needed.
- No unverifiable precise claim remains after links or sources are removed.
- Only user-provided or confirmed links are used.
- Spelling, grammar, terminology, and English usage are correct and consistent.
- The prose avoids the integrated AI-writing patterns, contains no em or en dashes, and reads naturally aloud.
- The article contains no fake facts, sources, tests, cases, quotes, product claims, or copied SERP wording.