Career-Ops Job Search Center
career-ops-hq/career-ops
Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.
A skill your agent uses when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation…
Install Orgsci Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submission --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .claude/skills/orgsci-submission && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .claude/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submissionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .agents/skills/orgsci-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .agents/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .cursor/skills/orgsci-submission && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .cursor/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Organization-Science-Skills/skills/orgsci-submission--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .gemini/skills/orgsci-submission && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .gemini/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submissionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .github/skills/orgsci-submission && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .github/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgsci-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Organization-Science-Skills/skills/orgsci-submission .opencode/skills/orgsci-submission && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orgsci-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Science-Skills/skills/orgsci-submission into .opencode/skills/orgsci-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgsci-submission", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orgsci-submission- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 528 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation…
- Works in 2 steps: Cover-letter contribution case. The… → Fully anonymized main manuscript. The…
- Preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case
- SKILL.md covers When to trigger, Where and how, Submission-critical documents and Length and files, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Orgsci Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation, the all-inclusive ~50-page length norm, the separate standalone anonymized appendix, abstract/keyword and ORCID requirements, INFORMS formatting, transparency checklist, and the optional post-acceptance open-access option.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Resume and CV writing. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case
- Double-blind manuscript preparation
- The all-inclusive ~50-page length norm
- The separate standalone anonymized appendix
Example prompts
- “/orgsci-submission”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Cover-letter contribution case. The cover letter is viewed by the EIC and Senior Editor but
- Fully anonymized main manuscript. The submission guidelines require double-blind preparation
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Orgsci Submission loads about 1.3k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 528 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 528 words, ~1,294 tokens.
Download SKILL.mdSave it as
.claude/skills/orgsci-submission/SKILL.md (or your agent's skills folder).- name
- orgsci-submission
- description
- Use when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation, the all-inclusive ~50-page length norm, the separate standalone anonymized appendix, abstract/keyword and ORCID requirements, INFORMS formatting, transparency checklist, and the optional post-acceptance open-access option.
Submission Preflight (orgsci-submission)
When to trigger
- You are ready to submit and need a final checklist
- You are unsure what files Organization Science / ScholarOne expects
- You need to confirm anonymization and length before upload
Where and how
- Portal: ScholarOne Manuscripts at mc.manuscriptcentral.com/orsc.
- ORCID: required for the submitting author.
- Fees: there is no mandatory submission or publication fee. Open access is optional via the INFORMS Open Option (IOO), a post-acceptance APC of US$3,000 that has no bearing on the peer-review decision — never select it expecting to influence review.
Submission-critical documents
- Cover-letter contribution case. The cover letter is viewed by the EIC and Senior Editor but
not by reviewers. Use it to articulate the contribution to organization research in a concise block
that complements the abstract. Draft it with
orgsci-contribution-framing. - Fully anonymized main manuscript. The submission guidelines require double-blind preparation: remove names, affiliations, and acknowledgements, and write self-citations in the third person or in another neutral form.
Length and files
- Length norm: strive for under 50 pages of double-spaced 12-pt text (or 40 pages 11-pt), 1-inch margins, all-inclusive. No rigid universal hard cap, but editors may desk-reject excessively long submissions (with an option to resubmit shorter).
- Separate appendix: submitted as a separate anonymized standalone document "for review," meant for online supplementary posting, not main-text publication. Move heavy robustness material there.
- Abstract: ≤ 250 words.
- Format: INFORMS author-date citations; double-spaced; 1-inch margins; Garamond/Times-New-Roman-like fonts (no Helvetica Narrow); PDF or MS Word.
Transparency and integrity
- For submissions on or after 2025-08-01, certify compliance with Organization Science's Data and Methods Transparency Policy and upload the transparency checklist where required.
- Provide enough setting, data, methods, and analytic detail to permit replication.
- Quantitative and theoretical-code papers should be ready to share code upon editor request during review; accepted quantitative papers must publicly share data/code unless a documented exception and alternative transparency plan applies.
- Disclose AI/AI-assisted technology use, overlapping data or papers, COI, ethics/IRB issues, and any conference co-review status.
Show full SKILL.md (205 more words)Show less
Preflight checklist
- Cover-letter contribution case prepared and aligned with the abstract
- Main manuscript fully anonymized (names, affiliations, acknowledgements, self-cites)
- Separate anonymized standalone appendix prepared
- Within the all-inclusive ~50-page norm (12-pt, double-spaced, 1-inch margins)
- Abstract ≤ 250 words; 3-10 keywords supplied
- INFORMS author-date style; no Helvetica Narrow; PDF/Word
- ORCID linked for the submitting author
- Transparency checklist complete; data/code sharing or exception plan ready
- Open-access (IOO) understood as optional and post-acceptance only
Submission readiness pass for Organization Science
Use this as a second-pass capability check. First lock a level map, a mechanism paragraph, and the cover-letter contribution statement; then test whether the manuscript addresses interdisciplinary organization reviewers who ask whether the mechanism travels across levels of analysis.
- Primary move: Verify portal, article type, anonymity, declarations, files, data/code, and current source-map facts; return blockers before formatting advice.
- Decision ledger: return
claim / evidence / blocker / next editrows so the next pass can patch the manuscript directly. - Neighbor test: compare against AMJ for empirical management framing, ASQ for organization-theory depth, Management Science for formal/quantitative operations; if the neighboring outlet has the stronger audience claim, recommend re-routing before polishing.
- Submission-ready gate: before final advice, re-open
resources/official-source-map.mdfor upload-week rules and name the one live-check item that could change the recommendation.
Output format
【Portal】ScholarOne mc.manuscriptcentral.com/orsc; ORCID set
【Gating docs】cover-letter contribution case ✓ ; main ms anonymized ✓
【Length】≤ ~50 pp all-inclusive; heavy material in standalone anonymized appendix
【Abstract/format】≤250 words; 3-10 keywords; author-date; no Helvetica Narrow
【Transparency】checklist complete; code/data sharing or exception plan ready
【Next step】orgsci-review-process© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Organization-Science-Skills/skills/orgsci-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Orgsci Submission next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orgsci Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Career-Ops Job Search Centercareer-ops-hq/career-ops | 74k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~2k | Automated safety check: Pass | MIT | |
| Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool | 2.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Resume Tailoringvarunr89/resume-tailoring-skill | 769 | 1 repos | ~8.9k | Automated safety check: Pass | MIT | |
| Offer Negotiationreactive-resume/reactive-resume | 44k | — | ~10k | Automated safety check: Pass | MIT |
Similar skills
Reactive Resume Builder
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
Internship Project Preparation Tool
LiuMengxuan04/shushu-internship-tool
Turns a target internship job description into a resume-ready, interview-ready project by finding and auditing GitHub projects and drafting resume bullets and interview Q&A.
Resume Tailoring
varunr89/resume-tailoring-skill
A skill your agent uses when creating tailored resumes for job applications - researches company/role, creates optimized templates, conducts branching experience discovery to surface undocumented…
Offer Negotiation
reactive-resume/reactive-resume
Evaluates and negotiates job offers. An agent skill from reactive-resume/reactive-resume.
Good Story
Rimagination/good-story
A skill your agent uses when the user asks to find, sharpen, evaluate, rewrite, or explain the story in scientific or scholarly materials across disciplines, including manuscripts, grants, paper…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Orgsci Submission
What does Orgsci Submission do?
A skill your agent uses when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation…. Orgsci Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case, double-blind manuscript preparation, the all-inclusive ~50-page length norm, the separate standalone anonymized appendix, abstract/keyword and ORCID requirements, INFORMS formatting, transparency checklist, and the optional post-acceptance open-access option.
When should I use Orgsci Submission?
Orgsci Submission fits situations like: preparing the final Organization Science submission package — the ScholarOne preflight covering the cover-letter contribution case; double-blind manuscript preparation; the all-inclusive ~50-page length norm; the separate standalone anonymized appendix.
How do I install Orgsci Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a claude-code`. Or copy the skill folder (Organization-Science-Skills/skills/orgsci-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/orgsci-submission in your project. Claude Code loads it when a task matches its description.
How do I install Orgsci Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a codex`. Or copy the skill folder (Organization-Science-Skills/skills/orgsci-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/orgsci-submission in your project. Codex loads it when a task matches its description.
Can I use Orgsci Submission in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orgsci-submission, .gemini/skills/orgsci-submission, .github/skills/orgsci-submission and .opencode/skills/orgsci-submission in your project.
What does Orgsci Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Orgsci Submission is instructions for the agent only.
Does Orgsci Submission access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Orgsci Submission safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Orgsci Submission use?
Orgsci Submission is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Orgsci Submission use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Orgsci Submission?
Skills that share tags, products or a category with Orgsci Submission: Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars) and Resume Tailoring (varunr89/resume-tailoring-skill, 769 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orgsci Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.