Agent skill · Data & Analytics

ors-submission

Use when running the final pre-submission preflight for an Operations Research (OR) manuscript — INFORMS Author Portal/ScholarOne, area selection, recommending Associate Editors and reviewers, soft double-anonymous anonymization, the mandatory contribution statement, page-tier limits, and the code/data deposit plan. Checks readiness to submit; it does not handle the post-decision response (ors-rebuttal).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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: Operations-Research-Skills/skills/ors-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

# Pre-Submission Preflight (ors-submission) ## When to trigger - "We're submitting this week" — the last check before hitting submit. - Unsure what the INFORMS Author Portal / ScholarOne requires for *Operations Research*. - Verifying area routing, anonymization, the contribution statement, and page limits. > Always re-verify current limits and required files on the official OR > submission-guidelines page and the Code and Data Disclosure Policy before submitting — > specifics change. As of 2026-06-20 the key specs below were corroborated; items marked > 待核实 / re-confirm should be checked on the live page. ## Verified OR specs (confirm current values) - **Submission system:** ScholarOne Manuscripts via the **INFORMS Author Portal**. - **Review model:** **soft double-anonymous** — omit author names from the submission; reviewers cannot see authors; the Area Editor and Associate Editor can; authors **can** see the handling **Area Editor's** name but not the AE or reviewers. - **Area routing:** select the correct **editorial area** so it reaches the right Area Editor (confirm the current area list and Area Editors' Statements — 待核实 names). - **Nominations:** recommend **3 Associate Ed

What's inside
Steps it walks through
  1. When to trigger
  2. Verified OR specs (confirm current values)
  3. Pre-submission checklist
  4. Anonymization (soft double-anonymous)
  5. Article type, area & nominations
  6. Format & files
  7. Cover letter & policies
  8. Anti-patterns
  9. Output format
  10. Resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ors-submission skill do?

Use when running the final pre-submission preflight for an Operations Research (OR) manuscript — INFORMS Author Portal/ScholarOne, area selection, recommending Associate Editors and reviewers, soft double-anonymous anonymization, the mandatory contribution statement, page-tier limits, and the code/data deposit plan. Checks readiness to submit; it does not handle the post-decision response (ors-rebuttal).

How do I install it?

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