Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Organization Science

ASecurity

Use when targeting Organization Science (OrgSci) or deciding whether an organization theory / behavior / innovation manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgogitperformance

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill organization-science --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Organization Science?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Organization Science
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-organization-science/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-organization-science)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: organization-science
description: Use when targeting Organization Science (OrgSci) or deciding whether an organization theory / behavior / innovation manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Organization Science (organization-science)

## Journal positioning

Organization Science, published by INFORMS, is a leading multidisciplinary outlet for research on organizations — organization theory, organizational behavior, strategy, technology and innovation, and the science of how organizations are designed, behave, and change. Its hallmark is methodological pluralism in service of a theoretical contribution: it welcomes formal and computational modeling, simulation, qualitative and ethnographic work, lab and field experiments, and large-sample quantitative studies, provided each advances organization theory. The audience spans disciplines, so a paper must speak to a broad organizational-science conversation, not a narrow applied niche.

This skill is a **fit / venue-selection / re-framing** tool. It does not replace the journal's current official submission guidelines. Before submitting, re-check the live author instructions on the INFORMS / Organization Science site and the submission system.

## When to trigger

- The author names Organization Science (or the INFORMS organizational outlet / FT50 management elite) as the venue.
- A paper makes an organization-theory contribution using computational, qualitative, experimental, or quantitative methods.
- A modeling or simulation study about organizations needs a home that values formal methods with a theoretical payoff.
- The author needs OrgSci's desk-reject risks and a credible `administrative-science-quarterly` / `academy-of-management-journal` / `management-science` alternative list.

## Scope & topic fit

- Organization theory and design, organizational learning, knowledge, and adaptation; coordination, structure, and routines.
- Organizational behavior, identity, culture, networks, and decision-making within and across organizations.
- Technology, innovation, and the organization of R&D and digital work — a long-standing OrgSci strength.
- Multidisciplinary lenses (economics, sociology, psychology, computer science) applied to organizational questions.

## Method & evidence bar

- A clear theoretical contribution is required; method is chosen to fit the question, and all rigorous methods are on the table.
- Computational/simulation papers must justify model assumptions, demonstrate robustness to parameters, and deliver theoretical insight, not just a working model.
- Qualitative work needs transparent analysis and a credible data-to-theory path; quantitative work needs sound identification and measurement.
- Experiments require clean design and appropriate inference; mechanism and generalizability matter.

## Structure & house style

- The front end frames a theoretical problem in organization science and positions it across relevant disciplines.
- Method sections are detailed and transparent — for formal/computational work, assumptions and sensitivity analyses are expected up front.
- The discussion states the contribution to organization theory and connects it to the broader multidisciplinary conversation.
- OrgSci values clarity and rigor; exhibits should make the theoretical mechanism and results legible.

## Official-submission checklist

- Before giving submission-ready advice, read `../../resources/source-basis.md` and `../../resources/official-source-map.md`; start from the official source anchors for this journal family, then cite the current journal-specific page you checked.
- Search the live site for "Organization Science submission guidelines / author guidelines" (INFORMS) and follow the current version.
- Re-check word/length limits, abstract format, anonymization for double-blind review, reference style, and code/data and replication expectations for computational work.
- Re-check current open-science, data-availability, and AI-use disclosure policies, and any INFORMS-wide submission requirements.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating the contribution to organization theory.
- [ ] The chosen method (computational / qualitative / experimental / quantitative) is rigorous and fit to the question.
- [ ] For formal/computational work, assumptions, robustness, and the theoretical insight are explicit.
- [ ] The paper speaks to a broad, multidisciplinary organizational-science audience, not a narrow niche.
- [ ] Framing, references, and anonymization match the current OrgSci guide.

## Common desk-reject triggers

- A method or model with no organization-theory contribution (a working simulation or a clean effect is not enough).
- A narrow applied study with no broader theoretical or multidisciplinary relevance.
- Computational work without justified assumptions or sensitivity analysis; qualitative work without transparent analysis.
- An operations/optimization or pure-analytics paper with no organizational-theory payoff (belongs at an OM/OR venue).

## Re-routing decision

- Sociology-of-organizations craft at the highest selectivity → `administrative-science-quarterly`; theory-driven management empirics → `academy-of-management-journal`.
- Pure conceptual theory, no data → `academy-of-management-review`; integrative review → `academy-of-management-annals`.
- Strategy/firm-performance core → `strategic-management-journal`; European process/institutional/critical theory → `organization-studies`; interdisciplinary work-and-organization → `human-relations`.
- Optimization/analytics with no org-theory payoff → `management-science`; innovation/STI policy → `research-policy`; broad management empirics → `journal-of-management-en` or `journal-of-management-studies`.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Organization Science
[Topic tags] <2–3 closest topics>
[Method/evidence] <does the method deliver an organization-theory contribution at OrgSci's bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <submission system / length / references / code-data for computational work / AI disclosure>
[Re-route suggestion] <if not a fit, a better-matched venue>
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →