Individual skill

jel-workflow

Use when deciding which jel-* sub-skill to invoke next, or when sequencing a survey/review article from topic selection through revision for a Journal of Economic Literature (JEL) submission. Routes — it does not replace — the specialized skills.

Journal-of-Economic-Literature-Skills/skills/jel-workflow/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,400
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# JEL Workflow Router (jel-workflow)

## Overview

This is the router. It tells you **which jel-* skill to use at the current stage** of a **survey or review article** aimed at the *Journal of Economic Literature* (JEL) — the **American Economic Association's** survey-of-record journal (founded 1969). JEL does **not** publish original empirical research. It publishes commissioned and peer-reviewed **syntheses of bodies of economic research**, book reviews, and maintains the **JEL classification system**. So the lifecycle is not "design → identify → estimate → defend"; it is **scope a synthesis-worthy field → propose it → read the whole literature → impose an organizing framework → synthesize comprehensively and even-handedly → land the JEL voice → submit and revise.**

Default assumption: unless the user says otherwise, treat the target as JEL and the artefact as a **survey**, not a primary-research paper. Operational tells that you are at JEL and not a sibling: the work **reviews other people's results** rather than reporting your own; the natural first step is a **~10-page proposal emailed to the editor** before a full draft (检索于 2026-06;以官网为准); there is **no identification strategy and no replication package of your own data** (you instead appraise the studies you cover); the contribution is an **analytical map of a field**, not a new estimate. If the user actually has original results, they want a primary-research journal (e.g. AER, QE), not JEL — say so.

## When to trigger

- The user asks "what should I do next?" on a survey/review
- A survey draft reads like an annotated bibliography and needs a spine
- Work is ping-ponging between coverage, framing, balance, and the proposal
- A JEL editor/referee letter arrived and the user needs to switch into revision mode
Back to top