jmis-submission
Use when running the final pre-submission preflight for a Journal of Management Information Systems (JMIS) manuscript — the email-to-EIC intake, full anonymization for double-blind review, the ≤50-page and 150-word-abstract limits, the numbered bracketed reference style, and the cover-letter/attachment package. Final checks; it does not draft content.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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 (jmis-submission) ## When to trigger - "Submitting tomorrow" — last check before emailing the manuscript to the EIC - Unsure exactly what files, anonymization, and formatting JMIS expects - Confirming the paper is double-blind-ready and inside the page/abstract limits - The team assumed a ScholarOne/T&F portal and needs the actual intake route ## Process facts (source map re
What does the jmis-submission skill do?
Use when running the final pre-submission preflight for a Journal of Management Information Systems (JMIS) manuscript — the email-to-EIC intake, full anonymization for double-blind review, the ≤50-page and 150-word-abstract limits, the numbered bracketed reference style, and the cover-letter/attachment package. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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.