improve-article

Use when improving an article or long-form draft for structure, clarity, coherence, flow, readability, or prose quality while preserving meaning, accuracy, intent, and voice.

SKILL.md

GitHub

Improve Article

Purpose

Improve structure, clarity, coherence, flow, readability, and prose quality while preserving factual meaning, core argument, technical accuracy, authorial intent, and voice.

Do not invent facts, add unsupported claims, remove important nuance, or turn the article into generic polished writing.

Workflow

  1. Review the full article first.

    Internally analyze section order, idea dependencies, unclear or unsupported claims, redundancy, gaps, transitions, tone drift, and readability problems.

  2. Before rewriting, show only a brief review:

    • Key Issues: at most 6 bullets
    • Proposed Rewrite Direction: at most 4 bullets
    • Questions: at most 3 bullets, only when needed

    If there are no blocking questions, write: No blocking questions. Share priority or tone adjustments; otherwise I’ll rewrite from this direction.

  3. After feedback, rewrite the full article in one pass.

    Use large coherent chunks only when length or accuracy makes one pass unsafe.

  4. Finish with a concise editorial summary:

    • structural changes
    • clarity improvements
    • remaining assumptions or unresolved issues, if any

Rewrite rules

  • improve clarity, coherence, and flow
  • preserve meaning, nuance, technical precision, and voice
  • remove redundancy
  • make implicit logic explicit
  • keep necessary technical terms
  • avoid unnecessary jargon
  • introduce concepts before using them
  • keep paragraphs concise, preferably under 400 characters
  • exceed 400 characters only when needed for accuracy or readability
  • avoid filler phrases such as "it is important to note", "as we all know", "in today’s world", "this article explores", and "various aspects"
  • avoid marketing tone unless the original article is clearly marketing-oriented
  • surface unclear, unsupported, ambiguous, or technically questionable claims instead of rewriting them as true
  • ask for clarification when a claim blocks an accurate rewrite; otherwise preserve uncertainty

Interaction rule

Use one feedback checkpoint before rewriting. Do not require outline approval or section-by-section approval unless the user asks or the article is too long or risky to revise accurately in one pass.