Agent skill · Code Review & Quality

arecon-organizing-framework

Use when imposing an analytical structure or taxonomy on a literature for an Annual Review of Economics (ARE) review — the "spine" that turns a reading list into an argument about the field. Designs the framework; it does not gather the literature (arecon-literature-synthesis) or appraise evidence and balance (arecon-evidence-standards).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arecon-organizing-framework --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: Annual-Review-of-Economics-Skills/skills/arecon-organizing-framework/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

# Organizing Framework — the Review's Spine (arecon-organizing-framework) ## When to trigger - The evidence matrix is built but the draft would read like a list of papers - Sections are named after topics ("Empirical studies", "Theoretical work") rather than ideas - A reader could not predict what comes next or why papers are grouped as they are - You cannot state in one sentence the *argument* the review makes about the field ## Why the spine is the whole game at ARE The most-cited reason review articles fail is that they are **annotated bibliographies**: paper-after-paper summaries with no organizing idea. A great ARE review **imposes a structure the field did not have** — a taxonomy, a unifying framework, a sequence of questions, or a simple model — that makes scattered work legible to an economist from an adjacent field. The framework is the contribution; the citations are the evidence. ARE's accessibility mandate raises the bar further: the spine must be graspable by a *non-specialist* on one read. Choose it deliberately: | Spine type | Organizes the field by | Best when | |-----------|------------------------|-----------| | **Taxonomy** | mutually-exclusive categories of mech

What's inside
Steps it walks through
  1. When to trigger
  2. Why the spine is the whole game at ARE
  3. The test of a good framework
  4. Checklist
  5. Anti-patterns
  6. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the arecon-organizing-framework skill do?

Use when imposing an analytical structure or taxonomy on a literature for an Annual Review of Economics (ARE) review — the "spine" that turns a reading list into an argument about the field. Designs the framework; it does not gather the literature (arecon-literature-synthesis) or appraise evidence and balance (arecon-evidence-standards).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arecon-organizing-framework --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