Individual skill
orgstud-methods
Use when choosing and justifying the research design for an Organization Studies (OS) manuscript — qualitative/ethnographic, process, historical, or quantitative — and setting the rigor bar OS reviewers expect. Designs the study; it does not run the analysis (see orgstud-data-analysis).
Organization-Studies-Skills/skills/orgstud-methods/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- design Derived category
- operations Derived category
- data Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,907 bytes
Read excerpt
# Methods & Research Design (orgstud-methods)
## When to trigger
- You are choosing between a qualitative/process design and a quantitative one
- The design is chosen but its *rigor and transparency* are not yet defensible to OS reviewers
- A qualitative study lacks a sampling logic, immersion account, or trustworthiness safeguards
- A quantitative study leads with the estimator instead of the organizational mechanism it reveals
## Method follows the theoretical question — and OS leans qualitative
At OS, **no method is privileged in principle**, but the journal's center of gravity is **qualitative, ethnographic, process, and historical** research, and such work is genuinely first-class here — not a tolerated minority. The non-negotiable is that the design fits the question (see `orgstud-theory-development`) and is executed with craft. A sophisticated estimator cannot rescue a thin theory, and a single immersive case can carry an OS paper if the theoretical insight is deep — a different bar from venues where a clean identification design is itself treated as the contribution. OS reviewers ask, above all, *does this design let you see the organizing process you claim to theorize?*
## Branch A — Qualitative / process / ethnographic / historical