jfm-submission
Use when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data statement, and house formatting. Final checks; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-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 (jfm-submission) ## When to trigger - "Submitting this week" — last check before uploading to Editorial Manager - Unsure which files and declarations the Elsevier submission form expects - Confirming the manuscript is correctly blinded for the review model - Verifying competing-interest, data, and AI-use statements are in place ## Process facts (检索于 2026-06，费用项再核实于 2026-06-2
What does the jfm-submission skill do?
Use when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data statement, and house formatting. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-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.