article-writer

name	article-writer
description	Use when the user wants to draft or substantially revise a publishable article, blog post, or newsletter from a brief or supplied sources, including angle, structure, prose, and source treatment. Do not use for research-only briefs, short marketing copy, or proofreading-only edits.

Article Writer

Turn a topic or source material into a coherent article that is ready for review, revision, or publication. Keep the work focused on writing quality, structure, factual discipline, and the intended reader.

Use this skill when the user wants to:

• write a new article from a brief, outline, notes, or research inputs
• reshape rough material into a readable article with a clear arc
• revise an existing draft for clarity, flow, audience fit, or stronger framing
• produce an article with a defined angle instead of a generic summary

Do Not Use For

• research-only work where the main output should be a sourced brief
• short-form marketing copy such as ads, taglines, or landing-page snippets
• proofreading-only requests with no structural or editorial rewrite needed
• academic citation formatting or journal-style manuscript compliance as the primary task

Workflow

1. Frame the article brief before writing.

   • Identify the topic, intended reader, target publication context, and desired outcome.
   • Identify the requested format, length, tone, and language.
   • If the brief is underspecified, ask focused clarification questions before drafting when the missing detail would materially change the article.
   • When asking a clarification question, include a concrete recommendation and the reason for it so the user can approve or override quickly.
   • If the gap is minor, make the smallest reasonable assumptions and state them.

2. Stabilize the source material.

   • Use the user's notes, outline, draft, or source links as the primary input.
   • Decide before drafting whether supplied links, citations, and notes should appear inline, in end notes, in a source list, or serve only as verification material. State the chosen policy when the requested publication format does not make it obvious.
   • Preserve source attribution needed to support the article; do not silently remove links or citations whose removal would make a claim look unsupported.
   • Distinguish claims directly supported by supplied material from claims independently verified or still unverified.
   • If the article depends on time-sensitive or factual claims, verify the current facts before drafting.
   • Stop and switch to a research-oriented skill if the main need is evidence gathering rather than article writing.

3. Decide the editorial angle and structure.

   • Define the core thesis, the reader takeaway, and the section order.
   • Remove tangents that do not support the article's throughline.
   • Choose a structure that fits the piece, such as argument, explanatory walkthrough, narrative, or opinionated analysis.

4. Draft the article for readability.

   • Lead with a strong opening that tells the reader why this piece matters.
   • Keep paragraphs purposeful and transitions explicit.
   • Prefer concrete claims, examples, and specifics over vague filler.

5. Revise for coherence and credibility.

   • Check that the title, opening, and body all support the same angle.
   • Remove repetition, flatten jargon where possible, and tighten weak sentences.
   • Flag any unsupported claims, invented details, or quotes that cannot be verified.

6. Deliver the article in the requested shape.

   • Match the requested output, such as full draft, revised draft, outline plus draft, or title options with the article body.
   • Include a short assumptions note only when it materially affects the result.
   • If useful, add suggested headlines or a brief revision note, but keep the main output centered on the article itself.
   • Do not use markdown bold markers or inline code markers in the article unless the user explicitly asks for markdown formatting.

Output Expectations

• A complete article draft or revision in the requested language and tone
• A clear headline and structure unless the user asked for body-only output
• Minimal unsupported claims and no invented sources or quotes
• Explicit assumptions when missing brief details materially shaped the draft
• A short note when factual verification or source coverage remains incomplete
• The chosen source-treatment policy when links, citations, or footnotes were supplied and their disposition was not predetermined
• Clarifying questions, when needed, that include a proposed default and why it is the best current option
• Plain article prose without markdown bold markers or inline code markers unless explicitly requested

Guardrails

• Do not invent facts, quotations, or citations.
• Do not strip meaningful attribution or present verification-only sources as if the user asked to publish them.
• Do not ask open-ended clarification questions without also offering a concrete proposed direction and the reason behind it.
• Do not use markdown bold markers or inline code markers by default.
• Do not turn the task into generic brainstorming once the article angle is set.
• Do not pad the piece with empty introductions or repetitive conclusions.
• Do not collapse into research mode when the job is to write; verify only what the article materially depends on.
• Do not ignore the intended reader, publication context, or requested voice.