Agent skill · Data & Analytics

pom-submission

Use when running the pre-submission preflight for a Production and Operations Management (POM) manuscript on ScholarOne — Department Editor routing, 32-page limit, double-blind files, e-companion designation, 350-word abstract, same-data disclosure, and the no-resubmission-after-rejection rule. Preflights the submission; it does not interpret decisions (pom-review-process).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-submission --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Production-and-Operations-Management-Skills/skills/pom-submission/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Submission Preflight (pom-submission) ## When to trigger - You are ready to submit and need a final checklist - You are unsure which Department to route to or how to designate the e-companion - You need to confirm the manuscript clears double-blind and same-data requirements > Reopen the current POMS author instructions and the SAGE journal page before giving submission-ready advice. POM moved from Wiley to SAGE in January 2024, so older Wiley templates/guidance are outdated; submission, however, remains on the POMS-run **ScholarOne / Manuscript Central** at mc.manuscriptcentral.com/poms — not a SAGE portal. ## Route to a Department Editor POM's defining step: submit to **one named Department** (e.g., Behavioral Operations, Supply Chain Management, Healthcare Operations, Sustainable Operations, Operations Management Data Analytics, or an interface department). The cover letter must articulate the target department so the paper is routed correctly. Confirm the live roster (待核实) before selecting. ## Format and file checks - **32-page limit** for the main manuscript (original *and* revised), **including** abstract, tables, figures, appendices, and references; **1.5 spacing, size 11

What's inside
Steps it walks through
  1. When to trigger
  2. Route to a Department Editor
  3. Format and file checks
  4. Double-blind anonymization
  5. Cover letter: disclosures POM specifically requires
  6. The one-shot rule
  7. Checklist
  8. Submission readiness pass for Production and Operations Management
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the pom-submission skill do?

Use when running the pre-submission preflight for a Production and Operations Management (POM) manuscript on ScholarOne — Department Editor routing, 32-page limit, double-blind files, e-companion designation, 350-word abstract, same-data disclosure, and the no-resubmission-after-rejection rule. Preflights the submission; it does not interpret decisions (pom-review-process).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-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.

Keep going