Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when building or sharpening the theory for an Organization Science manuscript — articulating the organizational mechanism, bridging micro-macro levels, and deciding between a priori deductive theorizing and inductive grounded theory building. Develops the theory; it does not frame the contribution statement (orgsci-contribution-framing) or run the analysis (orgsci-data-analysis).
Use when sharpening the one-sentence theoretical contribution of an Organization Studies (OS) manuscript and the intro/discussion claims that carry it. Frames the contribution; it does not build the theory (see orgstud-theory-development) or run analysis.
Use when staking the contribution of an Organization Studies (OS) manuscript against the specific theoretical conversation it joins — what the field knows, what it misses, and the precise gap this paper closes. Positions the argument; it does not build the theory (see orgstud-theory-development) or run analysis.
Use when drafting the response to reviewers and the revision plan for an Organization Studies (OS) R&R — turning developmental, theory-level reviewer comments into a credible point-by-point reply and revised manuscript. Plans and drafts the response; it does not redo the underlying analysis (route back to the specialist skills).
Use when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution. Builds the argument; it does not select methods or run analysis.
Use for full-manuscript prose and the discursive European register of an Organization Studies (OS) manuscript — voice, theoretical texture, the argument's arc, and qualitative craft. Polishes the writing; it does not change the theory or analysis.
Use when articulating the contribution of an Operations Research (OR) manuscript — especially the mandatory cover-letter contribution statement (since 1 June 2023, fewer than 500 words) and the discussion's significance claims. Frames why the work matters to OR; it does not position against specific prior papers (ors-literature-positioning) or run experiments (ors-data-analysis).
Use when responding to an Operations Research (OR) decision letter — writing the point-by-point response, closing proof gaps, adding baselines/instances, and passing the ORJournal code/data reproducibility review across a revision cycle. Drafts the revision and response; it does not parse the decision in the first place (ors-review-process) or run the final preflight (ors-submission).
Use when formulating the model and stating results for an Operations Research (OR) manuscript — defining the optimization/stochastic/simulation model, assumptions, and the theorems, propositions, and lemmas that carry the contribution. Builds the mathematical object and its claimed results; it does not prove them in detail (ors-methods) or run the computational study (ors-data-analysis).
Use when polishing the prose and notation of an Operations Research (OR) manuscript — enforcing the equation-free introduction, the text-only abstract under 200 words, clean theorem-proof exposition, and INFORMS author-year house style. Polishes language and house style; it does not formulate the model (ors-theory-development) or run the submission preflight (ors-submission).