Individual skill
orgstud-theory-development
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.
Organization-Studies-Skills/skills/orgstud-theory-development/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- 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,409
- 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
- engineering 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,011 bytes
Read excerpt
# Theory Development (orgstud-theory-development)
## When to trigger
- You have a rich phenomenon (from `orgstud-topic-selection`) but no theoretical machinery that *organizes* it
- Your "theory" is a set of labeled themes or a box-and-arrow diagram with no generative mechanism
- A reviewer says the theory is "thin," "descriptive," "a relabeling of the data," or "doesn't engage the literature it claims to advance"
- You must decide whether the contribution is a new construct, a process model, a reconceptualization, or a boundary condition
## Theory is the deliverable at OS
This is the load-bearing skill in the pack. At OS the **theory itself is the contribution** — more so than the dataset or the estimator. The journal's European, sociologically-rooted tradition means process and interpretive theorizing are fully legitimate as the *main* claim (a different default from variance-template journals). Your job is to produce a **generative theoretical move** readers elsewhere can pick up and use.
State the **mechanism / process logic**, not just constructs: