Agent skill · Design & Presentation

orgsci-methods

Use when choosing and defending the research design for an Organization Science manuscript — matching one of the journal's eclectic methods (qualitative/inductive, quantitative/archival, experimental, computational/simulation, formal-analytical) to the question and level of analysis, and justifying design without requiring causal identification.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-methods --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Organization-Science-Skills/skills/orgsci-methods/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

# Research Design & Methods (orgsci-methods) ## When to trigger - You are choosing a method, or a reviewer says the method does not fit the question - A reviewer demands causal identification you cannot obtain - Your level of analysis and your data source do not line up - You are mixing methods and need to justify the combination ## Match the method to the question — the journal is pluralistic Organization Science is **methodologically eclectic**: it publishes qualitative and inductive fieldwork, quantitative and archival studies, experiments, computational/simulation models, and formal-analytical theory, and it does not privilege one. The design must **fit the theoretical contribution and the level of analysis**, not signal methodological fashion. | Theoretical goal / data structure | Design that fits | |-----------------------------------|------------------| | Build a new process or construct from the field | Inductive qualitative (grounded theory, ethnography, comparative cases) | | Test a cross-level mechanism in nested data | Multilevel / HLM with explicit composition or contextual logic | | Trace organizational founding/failure over time | Event-history / survival; panel | |

What's inside
Steps it walks through
  1. When to trigger
  2. Match the method to the question — the journal is pluralistic
  3. Causal inference is valued but not required
  4. Design quality that reviewers check
  5. Execution bridge (StatsPAI / Stata MCP)
  6. Anti-patterns
  7. Methods pass for Organization Science
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the orgsci-methods skill do?

Use when choosing and defending the research design for an Organization Science manuscript — matching one of the journal's eclectic methods (qualitative/inductive, quantitative/archival, experimental, computational/simulation, formal-analytical) to the question and level of analysis, and justifying design without requiring causal identification.

How do I install it?

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