A skill your agent uses when running the final pre-submission preflight for a Journal of Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords…

MITAuto-check passed

Install Jhe Submission

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

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

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jhe-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-Health-Economics-Skills/skills/jhe-submission .claude/skills/jhe-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
jhe-submission
GitHub stars
1.2k
Token cost
~1.8k tokens
SKILL.md length
831 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 Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords…

  • Data-availability statement
  • SKILL.md covers When to trigger, Process facts (检索于…, Preflight checklist and How JHE submission differs…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • The no-length-limit/short-paper allowance

What it does

Jhe Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for a Journal of Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords, declarations, data-availability statement, and the no-length-limit/short-paper allowance. Final checks; it does not draft content.

Its SKILL.md is about 1.8k 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

  • Data-availability statement
  • The no-length-limit/short-paper allowance

Example prompts

  • “/jhe-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

Jhe Submission loads about 1.8k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 831 words of instructions outside code blocks.

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

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). 831 words, ~1,838 tokens.

Download SKILL.mdSave it as .claude/skills/jhe-submission/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
jhe-submission
description
Use when running the final pre-submission preflight for a Journal of Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords, declarations, data-availability statement, and the no-length-limit/short-paper allowance. Final checks; it does not draft content.

Submission Preflight (jhe-submission)

When to trigger

  • "Submitting tomorrow" — last check before pressing submit in Editorial Manager
  • Unsure which files, declarations, and statements the Elsevier submission expects
  • Confirming format, keywords, and the Data Availability Statement are JHE-compliant
  • Confirming the manuscript matches JHE's single-anonymized review (do NOT over-anonymize as for AEA double-blind)

Process facts (检索于 2026-06;以官网为准 — re-confirm on the JHE guide for authors)

  • JHE is Elsevier's field flagship for health economics (ISSN 0167-6296); submission is via Elsevier Editorial Manager (editorialmanager.com/jhlthec).
  • Review model: single-anonymized — referees see author identities; suitable papers go to ≥2 reviewers. There is no double-blind anonymization requirement, so stripping the manuscript of names is unnecessary (and removing acknowledgments/self-citations is not a desk requirement here).
  • Length: JHE publishes papers of any length and encourages short papers — there is no separate short-paper channel. Match length to content; do not pad.
  • Keywords: provide 1–7 keywords in English.
  • Data & code: Elsevier Research Data policy — authors are encouraged (not mandated) to deposit data and to state data availability at submission via a Data Availability Statement. This is softer than the AEA mandatory openICPSR gate; honest documentation is the standard (see jhe-replication-package).
  • Declarations: Declaration of Competing Interest, funding sources, and a Declaration of Generative AI in the writing process per Elsevier policy; AI cannot be an author. One paper under review at a time.
  • Volatile / 待核实: exact abstract word limit, JEL-code requirement, current editorial board, APC for the open-access option, and any structured-abstract or highlights requirement — re-check the live guide for authors before submitting.

Preflight checklist

Format & front matter
  • Manuscript in an accepted format (Word/LaTeX per Elsevier); pages numbered; sections clearly headed
  • 1–7 English keywords supplied; abstract within the journal's limit (待核实)
  • JEL codes included if required (待核实); affiliations and corresponding-author details complete
  • Not over-anonymized — single-anonymized review means author info is expected on the title page
  • References in the journal's house citation style (Elsevier author-date; re-check the guide)
Exhibits & appendix
  • Tables/figures legible; standard errors reported with clustering stated (stars optional)
  • Skewed-spending estimator and outcome definitions stated in notes
  • Online/supplementary appendix prepared and separate from the main paper
Data, declarations & policy readiness
  • Data Availability Statement drafted: names data, holder, access mechanism, realistic path/cost/wait
  • Code package ready to share even if data is restricted (jhe-replication-package)
  • Declaration of Competing Interest + funding statement complete
  • Declaration of Generative AI in writing prepared per Elsevier policy; no AI listed as author
  • Confirmed not under review elsewhere; ethics/IRB statement included where human-subjects or restricted health data is used
  • Cover letter states the health-economics contribution and the target audience within JHE's scope

How JHE submission differs from the AEA journals (do not import the wrong reflexes)

If your last submission was to AEJ: Applied, AER, or another AEA outlet, several habits will mislead you here:

  • Anonymization: AEA review is double-blind and demands a fully blinded file; JHE is single-anonymized — keep the title page with author details and do not scrub acknowledgments or self-citations.
  • Data/code: the AEA mandates an openICPSR package the Data Editor verifies before publication; JHE only encourages deposit and asks for a Data Availability Statement — so the burden shifts from a forced build to honest documentation of a (often restricted) access path.
  • Length: AEA outlets have working length norms; JHE explicitly takes any length and encourages short papers, so a tight result need not be inflated.
  • Stars: AEA permits significance stars; JHE/Elsevier also permits them, but SEs and clustering remain the load-bearing reporting object either way.
Show full SKILL.md (267 more words)Show less

Anti-patterns

  • Over-anonymizing for double-blind when JHE is single-anonymized (wasted effort, signals wrong target)
  • Padding a clean short paper to look like a full-length article when JHE encourages short papers
  • Submitting with "data available on request" instead of a specific Data Availability Statement
  • Omitting standard errors / clustering from exhibits, or notes that are not self-contained
  • Assuming the abstract limit, JEL requirement, or APC from memory instead of re-checking the live guide
  • Forgetting the Declaration of Generative AI or the competing-interest statement
  • Submitting while the same manuscript is under review at another journal (one-at-a-time rule)

Output format

【Portal】Editorial Manager (editorialmanager.com/jhlthec) ready? [Y/N]
【Review model】single-anonymized — NOT over-anonymized? [Y/N]
【Front matter】1–7 keywords + abstract (limit 待核实) + JEL if required? [Y/N]
【Exhibits】SEs + clustering shown, notes self-contained? [Y/N]
【Data Availability Statement】specific (data/holder/mechanism/path)? [Y/N]
【Declarations】competing interest + funding + GenAI; no AI author? [Y/N]
【Next step】submit via Editorial Manager → jhe-rebuttal after the decision

After you press submit

Editorial Manager will route the manuscript to a handling editor who decides whether it goes to review; suitable papers go to ≥2 health-economist referees (检索于 2026-06;以官网为准). There is no double-blind step to clear, so a desk decision turns on fit and credibility, not anonymization mechanics — which is why the upstream work (jhe-topic-selection for fit, jhe-identification for design) does the heavy lifting. Keep the response-letter machinery (jhe-rebuttal) ready; if the decision is an R&R, you will re-enter the pack at the owning skill for each binding concern before resubmitting here.

Supplementary resources

Handoff boundary

This is the final preflight; it checks the package is complete and policy-compliant, not whether the science is ready — that is the upstream specialists' job. If the preflight surfaces a substantive gap (a missing identification defense, an overclaimed welfare statement), do not submit: route back to the owning skill first. After submission, the next stop is jhe-rebuttal when the decision letter arrives.

© 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-Health-Economics-Skills/skills/jhe-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

Jhe 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.

Jhe Submission compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jhe Submission this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.8kAutomated 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 Jhe Submission

What does Jhe Submission do?

A skill your agent uses when running the final pre-submission preflight for a Journal of Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords…. Jhe Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for a Journal of Health Economics (JHE) manuscript via Elsevier Editorial Manager — single-anonymized review, keywords, declarations, data-availability statement, and the no-length-limit/short-paper allowance.

When should I use Jhe Submission?

Jhe Submission fits situations like: data-availability statement; the no-length-limit/short-paper allowance.

How do I install Jhe Submission in Claude Code?

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

How do I install Jhe Submission in Codex?

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

Can I use Jhe 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 jhe-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/jhe-submission, .gemini/skills/jhe-submission, .github/skills/jhe-submission and .opencode/skills/jhe-submission in your project.

What does Jhe Submission need to run?

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

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

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

About 1.8k tokens (SKILL.md is roughly 7.4k 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 Jhe Submission?

Skills that share tags, products or a category with Jhe 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 Jhe 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.