ci-submission
Use when running the final pre-submission preflight for Critical Inquiry (CI) via Editorial Manager — format selection, the 9,500-word limit (including discursive notes and all bibliographical information), Microsoft Word manuscript, Chicago (17th ed.) footnotes with no works-cited list, separate 300 ppi JPEG/TIFF images with author-secured permissions, and the no-simultaneous-submission rule. Final checks; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-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 (ci-submission) The last check before pressing submit on **Editorial Manager** (`editorialmanager.com/ci/`). CI's most common avoidable failures are a manuscript over the **9,500-word** cap (because notes were not counted) and images that are embedded, low-resolution, or uncleared. Verify volatile specifics on the official page before relying on them. ## When to trigger - "Submitting tomorrow" — last pass before upload - Unsure which files / format Editorial Manager expects - Confirming the chosen format's cap is met and images are prepared correctly ## Process facts (verify volatile items on the official page) - **Publisher:** University of Chicago Press (journal founded 1974). - **Portal:** **Editorial Manager** (`editorialmanager.com/ci/`); special-issue proposals may go to `cisubmissions[at]gmail.com`. - **Review model:** peer-reviewed; reviewed by the **editors-in-chief in consultation with the editorial team**. - **Formats & caps:** **Article ≤ 9,500 words** (**includes discursive notes and all bibliographical information**); **Critical Response ≤ 3,000 words**; **Review ≤ 500 words**. - **Manuscript file:** **Microsoft Word**. - **Citations:** footnote
- When to trigger
- Process facts (verify volatile items on the official page)
- Preflight checklist
- Format & length
- Citations & apparatus
- Images & permissions
- Policy & files
- Anti-patterns
- Submission readiness pass for Critical Inquiry
- Output format
- Supplementary resources
What does the ci-submission skill do?
Use when running the final pre-submission preflight for Critical Inquiry (CI) via Editorial Manager — format selection, the 9,500-word limit (including discursive notes and all bibliographical information), Microsoft Word manuscript, Chicago (17th ed.) footnotes with no works-cited list, separate 300 ppi JPEG/TIFF images with author-secured permissions, and the no-simultaneous-submission rule. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-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.