Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the…
Install Jpube Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .claude/skills/jpube-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .claude/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .agents/skills/jpube-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .agents/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .cursor/skills/jpube-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .cursor/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Public-Economics-Skills/skills/jpube-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .gemini/skills/jpube-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .gemini/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .github/skills/jpube-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .github/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpube-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Public-Economics-Skills/skills/jpube-review-process .opencode/skills/jpube-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jpube-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Economics-Skills/skills/jpube-review-process into .opencode/skills/jpube-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpube-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jpube-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 660 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the…
- You need to understand
- SKILL.md covers When to trigger, How JPubE review works…, Appeals (verified) and Planning implications, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers
What it does
Jpube Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Hendren–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy. Explains the process; for the final file check use jpube-submission.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Academic paper search. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- You need to understand
- Plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers
- The Editorial Manager workflow
- The Hendren–Kopczuk editorial leadership
Example prompts
- “/jpube-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jpube Review Process loads about 1.4k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 660 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 660 words, ~1,436 tokens.
Download SKILL.mdSave it as
.claude/skills/jpube-review-process/SKILL.md (or your agent's skills folder).- name
- jpube-review-process
- description
- Use when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Hendren–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy. Explains the process; for the final file check use jpube-submission.
Review Process (jpube-review-process)
When to trigger
- You want to know what happens after you press submit at JPubE
- You are deciding whether to post an SSRN preprint at submission
- You need to plan timelines and expectations around the review model
- A decision arrived and you are weighing whether to appeal
How JPubE review works (verified facts)
- Single anonymized review. Reviewers' identities are hidden from authors, but authors' identities are known to reviewers and editors. This is not double-anonymized — do not strip your name from the manuscript expecting blind review; write knowing referees see who you are. (Contrast: some venues use double-anonymized review.)
- Minimum of two reviewers. Suitable submissions are typically sent to at least two reviewers; expect substantive, specialist public-finance reports.
- Editorial leadership. The current ScienceDirect masthead lists Editors Nathaniel Hendren (MIT) and Wojciech Kopczuk (Columbia), supported by co-editors and advisory editors. A handling editor manages your manuscript and synthesizes the reports into the decision.
- Editorial Manager workflow. Submission and all correspondence run through Elsevier's Editorial Manager system; decisions (desk reject / reject / major or minor revision / accept) and revision uploads happen there.
- SSRN preprint option. At submission you may opt to have the manuscript posted publicly on SSRN after initial quality checks; this choice has no effect on the editorial process or outcome, so it is a free dissemination option, not a strategic lever.
- Generative-AI disclosure is required at submission and is part of the editorial-integrity screen.
Appeals (verified)
- Formal appeals are permitted under Elsevier's Appeal Policy, but only one appeal per submission is considered. Treat the appeal as a scarce, one-shot instrument: use it only for a clear factual or procedural error in the handling of the paper, with a calm, evidence-based case — not to relitigate taste. (See
jpube-rebuttalfor crafting the substance.)
Planning implications
- Write for named, specialist referees who can see your identity — frame contribution and self-citations accordingly.
- Do not over-invest in anonymization; invest in a transparent design two specialist reviewers can endorse.
- Decide the SSRN option deliberately (visibility vs. preferring to wait), knowing it does not change your odds.
Checklist
- Manuscript written for single-anonymized (identity-visible) specialist review
- Expect ≥ 2 reviewers; address the obvious public-finance objections pre-emptively
- Editorial Manager account and metadata ready
- SSRN preprint decision made deliberately
- AI-use disclosure prepared
- Appeal reserved for a clear error, used at most once
Show full SKILL.md (276 more words)Show less
Anti-patterns
- Stripping author identity expecting double-blind review (JPubE is single anonymized)
- Treating the SSRN option as if it improved acceptance odds
- Burning the single appeal on a taste disagreement instead of a factual/procedural error
- Ignoring AI disclosure requirements during submission
Decision pathways after submit
What lands in your inbox, and what each outcome implies for a public-finance paper.
| Outcome | What it means | Your move |
|---|---|---|
| Desk reject | Editor judged fit/contribution below bar before review | Re-route (jpube-topic-selection) or strengthen welfare framing |
| Reject after review | Specialists found a design or welfare gap | Appeal only on a clear error; else resubmit elsewhere |
| Major revision | Contribution viable; identification/welfare needs work | Route fundamentals to identification/data skills, then rebuttal |
| Minor revision | Close; clarifications and exhibits | Tighten, document, return promptly |
| Accept | — | Confirm data-availability and final source files |
Worked vignette: deciding whether to appeal (illustrative)
A bunching paper is rejected; two specialist reports agree the excess-mass counterfactual is the weak point, while one aside claims "the elasticity (e = 0.4, illustrative) is implausibly high." The author wants to appeal the second remark. The review-process read: the binding objection is the counterfactual, which is a substantive design judgment, not a factual or procedural error — so it is not appeal-eligible. The single appeal is reserved; the better path is to rebuild the counterfactual and resubmit (or send elsewhere), not to spend the one-shot appeal contesting taste.
Calibration anchors
- Plan for named, specialist referees who see your identity: pre-empt the obvious public-finance objection (counterfactual, pre-trends, sufficient-statistic assumption) in the manuscript itself.
- Calibration: short-paper-track targets are published separately from the standard track; do not infer a fixed turnaround time for ordinary submissions from the short-paper 4-6 week target.
Output format
【Review model】single anonymized (identity visible), ≥2 reviewers — understood? [Y/N]
【Editorial Manager】account + metadata ready? [Y/N]
【SSRN preprint】opt-in decision: [yes/no]
【AI disclosure】prepared? [Y/N]
【Appeal status】reserved for clear error, ≤1 use — noted? [Y/N]
【Next step】jpube-submission© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Journal-of-Public-Economics-Skills/skills/jpube-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jpube Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jpube Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Perplexity Web Searchdavila7/claude-code-templates | 33k | 11 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT |
Similar skills
Perplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Jpube Review Process
What does Jpube Review Process do?
A skill your agent uses when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the…. Jpube Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when you need to understand or plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers, the Editorial Manager workflow, the Hendren–Kopczuk editorial leadership, SSRN preprint option, and the one-appeal policy.
When should I use Jpube Review Process?
Jpube Review Process fits situations like: you need to understand; plan around the Journal of Public Economics (JPubE / JPubEc) editorial process — single anonymized review with a minimum of two reviewers; the Editorial Manager workflow; the Hendren–Kopczuk editorial leadership.
How do I install Jpube Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a claude-code`. Or copy the skill folder (Journal-of-Public-Economics-Skills/skills/jpube-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jpube-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Jpube Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a codex`. Or copy the skill folder (Journal-of-Public-Economics-Skills/skills/jpube-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jpube-review-process in your project. Codex loads it when a task matches its description.
Can I use Jpube Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jpube-review-process, .gemini/skills/jpube-review-process, .github/skills/jpube-review-process and .opencode/skills/jpube-review-process in your project.
What does Jpube Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Jpube Review Process is instructions for the agent only.
Does Jpube Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Jpube Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jpube Review Process use?
Jpube Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jpube Review Process use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jpube Review Process?
Skills that share tags, products or a category with Jpube Review Process: Read arXiv Paper (karpathy/nanochat, 59k stars), Perplexity Web Search (davila7/claude-code-templates, 33k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars) and Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jpube Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.