Running CI Preflight
PostHog/posthog
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
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…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-submission --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-Financial-Markets-Skills/skills/jfm-submission .claude/skills/jfm-submission && 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 "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .claude/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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-Financial-Markets-Skills/skills/jfm-submissionType 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 jfm-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-submission --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-Financial-Markets-Skills/skills/jfm-submission .agents/skills/jfm-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .agents/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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 jfm-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-submission --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-Financial-Markets-Skills/skills/jfm-submission .cursor/skills/jfm-submission && 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 "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .cursor/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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-Financial-Markets-Skills/skills/jfm-submission--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 jfm-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jfm-submission --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-Financial-Markets-Skills/skills/jfm-submission .gemini/skills/jfm-submission && 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 "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .gemini/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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 jfm-submissionInstalls 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 jfm-submission -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-Financial-Markets-Skills/skills/jfm-submission .github/skills/jfm-submission && 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 "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .github/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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 jfm-submission -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 jfm-submission --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-Financial-Markets-Skills/skills/jfm-submission .opencode/skills/jfm-submission && 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 "jfm-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Financial-Markets-Skills/skills/jfm-submission into .opencode/skills/jfm-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jfm-submission", 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.
jfm-submissionA 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. 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
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.
.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.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 (待核实).
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.
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.
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.
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.
【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 expecttemplates/checklist.md — submission self-checktemplates/manuscript_template.md — lightweight manuscript scaffold../../resources/official-source-map.md — official URLs and volatile facts© 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
SKILL.md and 2 other files in Journal-of-Financial-Markets-Skills/skills/jfm-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jfm Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Running CI PreflightPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Finalize Agent Promptgithub/awesome-copilot | 40k | 1 repos | ~224 | Automated safety check: Pass | MIT | |
| Azure Deployment Preflightgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Implementation Final Reviewopenai/openai-agents-python | 30k | — | ~2k | Automated safety check: Pass | MIT | |
| Preflightopenwpm/OpenWPM | 1.4k | — | ~670 | Automated safety check: Pass | Custom licence |
PostHog/posthog
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
github/awesome-copilot
Finalize prompt file using the role of an AI agent to polish the prompt for the end user.
github/awesome-copilot
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.
openai/openai-agents-python
Review completed implementation changes before final verification.
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.
openfootmanager/openfootmanager
Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.
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…
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…
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…
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…
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…
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…
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Jfm Submission is instructions for the agent only.
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.
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.
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.
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.
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.
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.