arecon-submission
Use when running the final delivery preflight for a commissioned Annual Review of Economics (ARE) review via the Annual Reviews production system — disclosure statements, reference/format compliance, figure permissions, and the transparency/reproducibility of any meta-analysis the review itself contains. Final checks; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arecon-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Delivery Preflight (arecon-submission) ## When to trigger - "Delivering soon" — last check before handing the commissioned review to Annual Reviews - Unsure which files, declarations, and permissions the production system expects - Confirming reference style, format, and figure specs are Annual Reviews-compliant - Verifying transparency obligations for any quantitative synthesis (meta-analysis)
What does the arecon-submission skill do?
Use when running the final delivery preflight for a commissioned Annual Review of Economics (ARE) review via the Annual Reviews production system — disclosure statements, reference/format compliance, figure permissions, and the transparency/reproducibility of any meta-analysis the review itself contains. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arecon-submission --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.