Higher Order Article Writer

Higher Order Article Writer

Overview

Use this skill to transform an existing article into a sharper, higher-level standalone article. Digest the source deeply, but do not expose the scaffolding or describe what the source article said unless the user explicitly asks for critique. The final article should read like an original piece: concise, focused, source-backed, and centered on one clear thesis.

Default to Chinese output unless the user explicitly asks for another language.

Workflow

1. Collect the source material.

   • If the user gives a URL, fetch and read the page. If browsing is needed, use current web sources and cite links.
   • If the user gives article text or a local file, use that as the primary source.
   • If the source is paywalled, inaccessible, or too sparse, state the limitation and proceed only with the available text.

2. Digest the source before writing.

   • Extract 3-7 core claims.
   • For each claim, identify the foundational assumption, supporting data, case evidence, and reasoning chain.
   • Compress the old article into one concise internal conclusion that includes: assumptions, claims, evidence, cases, and logic.
   • Do not start the new article until this extraction is coherent.

3. Audit the source logic internally.

   • Find unsupported leaps, hidden premises, causality/correlation confusion, missing counterexamples, stale data, selection bias, false dichotomies, and incentive blind spots.
   • Separate "the article is wrong" from "the article is incomplete under changed assumptions".
   • Keep useful claims when their assumptions still hold.

4. Rebuild with first principles.

   • Identify the most fragile or incomplete foundational assumption in the source.
   • Replace it with a new foundational assumption grounded in observable mechanisms.
   • Derive the new thesis from constraints, incentives, resource flows, balance sheets, user behavior, technology limits, policy rules, or other primary mechanisms relevant to the topic.
   • Make the new viewpoint explicit, not merely "more balanced".
   • Select 2-4 points that best support the thesis; cut secondary points unless they are necessary.

5. Support the new thesis.

   • Use authoritative current sources when facts, numbers, policies, market data, company data, or public figures may have changed.
   • Prefer primary sources: official statistics, filings, annual reports, central bank or government data, academic papers, standards, product docs, and direct company materials.
   • Use secondary media only to contextualize or compare interpretations.
   • Cite sources with Markdown links.

6. Check "逻辑三洽".

   • 自洽: Definitions, assumptions, and causal chains do not contradict each other.
   • 他洽: The thesis can explain the source article's valid observations, important counterexamples, and known external facts.
   • 续洽: The thesis can generate future observable signals. If time-based proof is not possible, use derivation-style reasoning and list future signals that would confirm or falsify the thesis.

7. Write the final Markdown article and save it.

   • Create or reuse markdown/ under the current project.
   • Save the file with a descriptive slug and date when useful.
   • Write a clean standalone article. Do not include sections named "旧文真正说了什么", "旧逻辑的关键漏洞", "如果基石假设崩塌", "逻辑三洽检验", or similar analysis scaffolding unless the user explicitly asks for an audit-style output.
   • Treat the source article as internal raw material. Do not write "原文认为", "原文提到", "原文实验说明", "旧文指出", "作者说", "source article", or similar phrases in the final article unless the user asks for an audit, critique, or comparison.
   • Include at least one useful visual. Prefer one Mermaid diagram for structure or flow. Add inline SVG only when it explains a concept better than text or Mermaid; do not add decorative visuals.
   • Keep the article compact. For ordinary blog/news rewrites, target about 900-1,600 Chinese characters of body text before references unless the user asks for a long article.