Agent skill · Code Review & Quality

phg-argument-synthesis

Use when turning a mapped literature into one cumulative argument for a Progress in Human Geography (PiHG) review essay — synthesizing many sources into a claim the field could not see from any one of them. Builds the synthetic spine; it does not gather sources (see phg-literature-positioning) or make the critical turn (see phg-critical-intervention).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill phg-argument-synthesis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Progress-in-Human-Geography-Skills/skills/phg-argument-synthesis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Argument Synthesis (phg-argument-synthesis) The single most important craft in a PiHG essay: **synthesis**. A review is not an ordered summary of what others found; it is an **argument the sources add up to but none of them made alone**. Reviewers and editors reject "annotated bibliography" pieces on sight. This skill turns a mapped literature (`phg-literature-positioning`) into a **cumulative claim** organized by your concept (`phg-theory-building`). ## When to trigger - You have the corpus and the concept, and must now build the spine - The draft reads as "A found X, B found Y, C found Z" — a list, not an argument - A reviewer said "this is descriptive," "where is the argument?," or "just a summary" - You cannot state the essay's thesis in one sentence ## Summary vs. synthesis (the core distinction) | Summary (reject) | Synthesis (PiHG) | |------------------|------------------| | Organized by **source** (paper by paper) | Organized by **your concept / claim** | | "X studied A; Y studied B" | "Across X and Y, the field has assumed Z — which fails because…" | | Coverage is the goal | An **argument** is the goal; coverage serves it | | Reader learns what exists | Reader learns **h

What's inside
Steps it walks through
  1. When to trigger
  2. Summary vs. synthesis (the core distinction)
  3. Build the cumulative spine
  4. The "one sentence" and "adds up" tests
  5. Reconcile, periodize, or adjudicate
  6. Checklist
  7. Anti-patterns
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the phg-argument-synthesis skill do?

Use when turning a mapped literature into one cumulative argument for a Progress in Human Geography (PiHG) review essay — synthesizing many sources into a claim the field could not see from any one of them. Builds the synthetic spine; it does not gather sources (see phg-literature-positioning) or make the critical turn (see phg-critical-intervention).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill phg-argument-synthesis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going