jbv-submission
Use when preparing to submit a Journal of Business Venturing (JBV) manuscript through Elsevier Editorial Manager — double-anonymized preparation, required declarations (competing interest, CRediT, generative-AI when used), flexible first-submission references, the Option C data availability statement, open-access/APC choice, and optional Data in Brief / MethodsX co-submission. Handles the submission preflight; it does not write the paper (jbv-writing-style) or manage the review (jbv-review-process).
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-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 (jbv-submission) ## When to trigger - The manuscript is final and you are about to upload - You need the Editorial Manager checklist for JBV - You are unsure how to anonymize, what to declare, or whether to pay the APC - You want to co-submit a data/methods artifact ## Where and how - **Portal**: Elsevier **Editorial Manager** (editorialmanager.com/jbvi). Submission is fully online, with stepwise file upload from the ScienceDirect submission link. - **First submission format**: provide editable source files; submit a separate title page and a fully anonymized manuscript for double-anonymized review. Strict reference formatting is not required at initial submission if every reference is complete and the style is consistent. - **Current masthead**: ScienceDirect lists **Sophie Bacq** and **Simon Parker** as Co-Editors-in-Chief; manuscripts route through the current area-editor / handling-editor structure. ## Double-anonymized preparation (required) Review is **double-anonymized**, so prepare an anonymized manuscript: - Remove author names, affiliations, and acknowledgements from the manuscript file. - Cite your own prior work in the third person; remove identif
- When to trigger
- Where and how
- Double-anonymized preparation (required)
- Required declarations
- Abstract & metadata
- Fees / open access
- Co-submission (optional)
- Checklist
- Anti-patterns
- Submission-stage failure modes and the fix
- Worked micro-example: a one-pass preflight (illustrative)
- Calibration anchors (hedged)
- Output format
What does the jbv-submission skill do?
Use when preparing to submit a Journal of Business Venturing (JBV) manuscript through Elsevier Editorial Manager — double-anonymized preparation, required declarations (competing interest, CRediT, generative-AI when used), flexible first-submission references, the Option C data availability statement, open-access/APC choice, and optional Data in Brief / MethodsX co-submission. Handles the submission preflight; it does not write the paper (jbv-writing-style) or manage the review (jbv-review-process).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-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.