SKILL

evidence-backed-analytical-writing

Write an evidence-backed analytical report — Chinese policy briefs, capability assessments, or technical arguments that combine supplied claims with retrieved sources — by classifying every load-bearing number, building an evidence map, and drafting a uniform claim → evidence → mechanism → limitation spine. Use when the deliverable is prose whose every figure must survive an audit. Not for citation mechanics (that is grounded-citations), social posts, changelogs, or any piece where the claims are already verified and only the wording needs work.

Target: Target not categorized. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • Evidence-backed analytical writing
  • Procedure
  • Negative findings and evidence backfill
  • Final-report sourcing style (简单出处)
  • Multi-model draft iterations
  • Always-on quality rules

Use this skill for Chinese analytical reports, policy briefs, capability assessments, and technical arguments that combine user-supplied claims with retrieved evidence. It complements grounded-citations: this skill governs claim hygiene, structure, and user-facing prose; grounded-citations governs the citation ledger and source rendering. 1. Normalize the brief. Extract the requested language, approximate length, section count, section symmetry, audience, required claims, and requested source recency. Preserve the requested point order and visible form: when the input uses “一是/二是/三是” analytical paragraphs, keep that numbered structure unless the user asks for a different format. Do not preserve an unsupported number as fact. Locate any project style contract (style/.md) before drafting and copy its bans into the QA checklist — contracts may forbid direct “我军” address (use 军队/相关力量) or require “要/应” imperatives in recommendation sections; contract wording overrides a prior draft's convention. 2. Set the recency boundary before searching. When the user asks for “最新/近期” data, establish a cutoff date, search current official releases first, and label older figures as trend baselines rat

This is an excerpt. Refer to the complete source and its current requirements.

Source repository
wxxb789/hoa
Source file
skills/evidence-backed-analytical-writing/SKILL.md
Fixed revision
beb1eca66d8fed7c3942dc3ef50990bf37837706
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: wxxb789/hoa · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T20:02:15.342Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.