A skill your agent uses when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data…

MITAuto-check passed

Install Jfm Submission

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-submission -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-submission --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-Financial-Markets-Skills/skills/jfm-submission .claude/skills/jfm-submission && rm -rf skills-src

Use ~/.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/

Facts

Skill name
jfm-submission
GitHub stars
1.2k
Token cost
~2.1k tokens
SKILL.md length
1,003 words
Files
3
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data…

  • Running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set
  • SKILL.md covers When to trigger, Process facts (检索于…, Preflight checklist and Matching the data statement to…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • House formatting

What it does

Jfm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `templates/checklist.md` and `templates/manuscript_template.md`).

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

  • Running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set
  • House formatting

Example prompts

  • “/jfm-submission”

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

Jfm Submission loads about 2.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 1,003 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

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). 1,003 words, ~2,116 tokens.

Download SKILL.mdSave it as .claude/skills/jfm-submission/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
jfm-submission
description
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.

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-22;以官网为准; re-confirm on the JFM guide for authors before submitting)

  • JFM is an Elsevier journal (ISSN 1386-4181 print / 1878-576X online); submission is via Elsevier Editorial Manager (待核实 the exact portal link on the journal's guide-for-authors page).
  • Review model: double-blind reported by secondary sources (待核实 against the official guide). If double-blind, the manuscript file must be fully anonymized — no author names, no acknowledgments, no self-citation tells like "in our earlier work," no identifying file metadata; author details go on a separate title page.
  • Reference style, abstract word limit, and any structured-abstract / JEL requirements: 待核实 on the guide for authors. Elsevier finance journals typically use an author-date style; confirm the exact format.
  • Declarations (Elsevier-standard): Declaration of Competing Interest; funding sources; CRediT author-contribution statement; data-availability statement; statement on generative-AI use (AI may not be listed as an author). Verify the current required set.
  • Submission fee: JFM charges a US$170 submission fee for original and revised submissions; the manuscript is only considered once the fee is paid (verified 2026-06-22 via the Elsevier guide for authors; re-confirm live, and check the developing-country/limited-means waiver if relevant). Do not assume JFM is fee-free.
  • APC / open access: JFM offers subscription (no APC) and open-access routes; the OA APC is USD 3,040 excluding taxes (verified 2026-06-22, single source — treat as indicative and re-confirm the exact figure live before opting into open access).

Preflight checklist

Blinding & files
  • If double-blind: manuscript fully anonymized (text, acknowledgments, self-citations, file metadata)
  • Separate title page with all authors, affiliations, and corresponding-author contact
  • Main manuscript (PDF/Word per portal), exhibits embedded or per Elsevier convention
  • Internet Appendix / supplementary file uploaded as a separate item
  • Cover letter naming the microstructure contribution and why JFM (not JF/JFE/RFS)
Content & style
  • Abstract within the stated limit (待核实); keywords / JEL as required
  • Reference style matches the guide for authors (待核实)
  • Every liquidity measure defined; units consistent across exhibits; SE/clustering in table notes
  • Suggested reviewers prepared if the portal requests them (avoid conflicts/coauthors)
Declarations
  • Declaration of Competing Interest + funding statement
  • CRediT contribution statement
  • Data-availability statement (consistent with the proprietary-feed access path in the Internet Appendix)
  • Generative-AI use statement; AI not listed as author
  • Confirmed the paper is not under review elsewhere

Matching the data statement to reality

Elsevier requires a data-availability statement, and for microstructure papers this is where proprietary feeds create a trap. The statement must be truthful and consistent with the Internet Appendix access path: if the order-book data come from a licensed vendor that prohibits redistribution, say so and point to the access path, rather than checking "data available on request." An inconsistency between a permissive data statement and a paper that visibly uses a restricted feed is a credibility flag the editor can see at desk screen. Confirm the journal's current data-and-code policy and whether any deposit is required at submission vs. acceptance (待核实).

The blinding pass (if double-blind — 待核实)

Anonymization fails most often on subtle tells, so do an explicit pass: (1) strip author names, affiliations, emails, and acknowledgments (including grant-number thanks that name an author's institution); (2) neutralize self-citations — "we show in Smith (2022)" becomes "as shown in prior work (citation withheld for review)"; (3) clear document metadata (author field, file path, track-changes history) from the PDF/Word file; (4) remove links to a named personal/SSRN page that identifies the authors; (5) check figure source files and embedded code comments for names. A separate, fully attributed title page carries all the author information the editor needs.

Show full SKILL.md (386 more words)Show less

Cover letter craft

The cover letter is read by the handling editor as a triage signal. In a tight paragraph: state the microstructure contribution in one sentence with the headline magnitude; say why JFM specifically (the trading-process mechanism / specialist depth, not "we were rejected by JF"); name the data and identifying variation; and confirm the paper is not under review elsewhere. If suggesting reviewers, propose microstructure specialists with no coauthorship/advising conflict. A letter that pitches the paper as broad finance undercuts the desk-screen for a microstructure journal.

Suggested reviewers and conflicts

If the portal requests suggested reviewers, treat it as a real lever. Propose three to five microstructure specialists whose own work your paper engages, excluding recent coauthors, advisors/advisees, and same-institution colleagues — a conflicted suggestion is worse than none. The point is to signal which sub-field expertise the paper needs (information-based, market design, HFT), helping the editor route it well. If there are scholars who should be excluded for a genuine conflict, the portal usually allows that too; use it sparingly and only for real conflicts, since over-exclusion reads as gaming the process. None of this substitutes for the paper standing on its own at desk screen.

Anti-patterns

  • Uploading a non-anonymized manuscript when the model is double-blind (self-citation/metadata tells)
  • A data-availability statement that contradicts the replication package's access path
  • Forgetting the US$170 submission fee (due on original and revised submissions), or assuming a fixed word limit, without checking the live guide
  • A cover letter that pitches the paper as broad finance instead of microstructure
  • Treating any volatile fact above as settled when it is marked 待核实

Last-mile consistency checks

The cheapest rejections come from internal inconsistencies a careful pass would catch. Confirm: the title, abstract, and intro state the same headline magnitude; every liquidity measure is defined on first use and labeled identically across tables; units (bps/cents/shares/horizon) are consistent everywhere; table notes all name the clustering scheme; the data-availability statement matches the proprietary-feed access path documented in the Internet Appendix; and the reference list format matches the guide for authors (待核实). Run a final figure check that every event study shows pre-event leads. These take an hour and remove the most common avoidable desk-screen failures for a microstructure submission.

Output format

text
【Journal】Journal of Financial Markets (JFM)
【Skill】jfm-submission
【Blinding】anonymized for double-blind + separate title page? [Y/N]
【Files】manuscript + title page + Internet Appendix + cover letter ready? [Y/N]
【Style】abstract limit / reference style verified or 待核实
【Declarations】COI / funding / CRediT / data / AI all present? [Y/N]
【Cover letter】names microstructure contribution + why JFM? [Y/N]
【Source status】portal & policy verified or 待核实
【Next step】submit via Editorial Manager → jfm-referee-strategy for what to expect

Supplementary resources

© 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

SKILL.md and 2 other files in Journal-of-Financial-Markets-Skills/skills/jfm-submission of brycewang-stanford/Awesome-Journal-Skills.

  • SKILL.md
  • templates/checklist.md
  • templates/manuscript_template.md

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Jfm Submission 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.

Jfm Submission compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jfm Submission this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~2.1kAutomated safety check: PassMIT
Running CI PreflightPostHog/posthog40k—~1.5kAutomated safety check: PassCustom licence
Finalize Agent Promptgithub/awesome-copilot40k1 repos~224Automated safety check: PassMIT
Azure Deployment Preflightgithub/awesome-copilot40k1 repos~1.9kAutomated safety check: PassMIT
Implementation Final Reviewopenai/openai-agents-python30k—~2kAutomated safety check: PassMIT
Preflightopenwpm/OpenWPM1.4k—~670Automated safety check: PassCustom licence

Similar skills

  • Running CI Preflight

    PostHog/posthog

    Official

    Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.

    40k GitHub stars~1.5k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Finalize Agent Prompt

    github/awesome-copilot

    Official

    Finalize prompt file using the role of an AI agent to polish the prompt for the end user.

    40k GitHub starsUsed in 1 repo~224 tokens
    Auto-check passed
  • Azure Deployment Preflight

    github/awesome-copilot

    Official

    Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    DevOps & CloudAuto-check passed
  • Implementation Final Review

    openai/openai-agents-python

    Official

    Review completed implementation changes before final verification.

    30k GitHub stars~2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Preflight

    openwpm/OpenWPM

    Use BEFORE implementing code in a crosslink-tracked project — loads .crosslink/rules/global.md, the language rules for detected manifests, the project rules, and the active tracking-<mode.md.

    1.4k GitHub stars~670 tokensUpdated 6 days ago
    Auto-check passed
  • Preflight

    openfootmanager/openfootmanager

    Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.

    1.1k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Questions about Jfm Submission

What does Jfm Submission do?

A skill your agent uses when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data…. Jfm Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

When should I use Jfm Submission?

Jfm Submission fits situations like: running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set; house formatting.

How do I install Jfm Submission in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-submission -a claude-code`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jfm-submission in your project. Claude Code loads it when a task matches its description.

How do I install Jfm Submission in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-submission -a codex`. Or copy the skill folder (Journal-of-Financial-Markets-Skills/skills/jfm-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jfm-submission in your project. Codex loads it when a task matches its description.

Can I use Jfm Submission 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 jfm-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jfm-submission, .gemini/skills/jfm-submission, .github/skills/jfm-submission and .opencode/skills/jfm-submission in your project.

What does Jfm Submission need to run?

SKILL.md names no scripts, command-line tools or credentials: Jfm Submission is instructions for the agent only.

Does Jfm Submission 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 Jfm Submission 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 Jfm Submission use?

Jfm Submission 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 Jfm Submission use?

About 2.1k tokens (SKILL.md is roughly 8.5k 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 Jfm Submission?

Skills that share tags, products or a category with Jfm Submission: Running CI Preflight (PostHog/posthog, 40k stars), Finalize Agent Prompt (github/awesome-copilot, 40k stars), Azure Deployment Preflight (github/awesome-copilot, 40k stars) and Implementation Final Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jfm Submission?

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.