rje-submission
Use when running the final pre-submission preflight for The RAND Journal of Economics (RJE) via the Wiley Research Exchange portal — hard page caps (40/50 pp, double-spaced), the <=100-word abstract, the non-refundable submission fee, Word/LaTeX files, and RJE Style Guide compliance. Final checks; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rje-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.
# Submission Preflight (rje-submission) ## When to trigger - "Submitting tomorrow" — last check before pressing submit on Wiley Research Exchange - Unsure which files and limits RJE expects at initial submission - Confirming page caps, the 100-word abstract, and author-date style are RJE-compliant ## Process facts (verified 2026-06-01; re-confirm on rje.org) - RJE is owned/sponsored by the **RAND
What does the rje-submission skill do?
Use when running the final pre-submission preflight for The RAND Journal of Economics (RJE) via the Wiley Research Exchange portal — hard page caps (40/50 pp, double-spaced), the <=100-word abstract, the non-refundable submission fee, Word/LaTeX files, and RJE Style Guide compliance. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rje-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.