Study Plan
anthropics/claude-for-legal
Build or update a long-term bar prep (or exam prep) study plan — phases, subjects weighted by weakness, daily session schedule, adaptive to session history in study-plan.yaml.
Agent skill
Orgstud Theory Development
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution.
MITAuto-check passed
Install Orgstud Theory Development
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .claude/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .claude/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .agents/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .agents/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .cursor/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .cursor/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Organization-Studies-Skills/skills/orgstud-theory-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .gemini/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .gemini/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .github/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .github/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills orgstud-theory-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Organization-Studies-Skills/skills/orgstud-theory-development .opencode/skills/orgstud-theory-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orgstud-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Organization-Studies-Skills/skills/orgstud-theory-development into .opencode/skills/orgstud-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orgstud-theory-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orgstud-theory-development- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution.
- Building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism
- SKILL.md covers When to trigger, Theory is the deliverable at OS, Branch by contribution type and For inductive / grounded work, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Conceptual move that constitutes the contribution
What it does
Orgstud Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism
- Conceptual move that constitutes the contribution
Example prompts
- “/orgstud-theory-development”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Orgstud Theory Development loads about 1.5k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 704 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 704 words, ~1,491 tokens.
Download SKILL.mdSave it as
.claude/skills/orgstud-theory-development/SKILL.md (or your agent's skills folder).- name
- orgstud-theory-development
- description
- 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.
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:
- Name the actors and what they are doing (sensemaking, justifying, translating, resisting, categorizing, accounting, coordinating).
- Name the social structure they act within (institutional field, logic, hierarchy, network, category system, discourse, status order).
- Specify the generative logic: why does this actor, in this structure, produce this sequence or this outcome? For process work, specify the sequence and transitions (phases, feedback, turning points), not a static relationship.
- Specify boundary conditions and scope: where the mechanism holds, weakens, or reverses.
A test: can a reader predict a non-obvious implication — or re-see a familiar phenomenon — from your theory? If not, you have a label, not a contribution.
Branch by contribution type
| Contribution type | What "good" looks like at OS |
|---|---|
| New process model | Phases/turning points with explicit transition logic; a process figure; what each phase does that the prior one could not |
| Reconceptualization | An existing construct (e.g., legitimacy, identity, routine) redefined so that a puzzle dissolves or a new range of cases comes into view |
| Extending a tradition | A precise statement of what institutional/practice/sensemaking theory missed, and the specific amendment your evidence forces |
| Critical/reflexive | A theoretical account of how power, ideology, or taken-for-grantedness operates — critique that theorizes, not critique that only denounces |
| Theoretical synthesis / essay | Two conversations bridged into a usable new lens, with the move stated crisply enough to cite |
For inductive / grounded work
If theory is emergent, this skill still applies — in reverse. The mechanism and process model are the output, presented after the data structure (see orgstud-data-analysis). Still required: a named mechanism, a process model (usually a figure with phases and feedback), and an explicit statement of novelty relative to existing organization theory. A grounded theory can be the entire OS contribution — it need not be a stepping-stone to a later test. Avoid "theory by adjective" (calling a pattern "dynamic," "recursive," "emergent" without specifying the process).
Show full SKILL.md (246 more words)Show less
For deductive / quantitative work
Hypotheses must be derived, each with its own causal-logic paragraph tied to the same core mechanism — not an asserted "bag of hypotheses." Moderators must be theoretically motivated, not data-mined. Even here, lead with the organizational mechanism the design illuminates; the estimator is in service of the theory.
Engaging social theory
OS expects live engagement with social theory, used precisely. If you invoke institutional logics, Bourdieu's capital/field, Foucauldian discipline, Weickian sensemaking, or practice theory, deploy the concept's actual machinery — do not name-drop it as ornament. Misusing a borrowed framework is a fast reviewer pushback.
Checklist
- A named generative mechanism (actors + structure + logic), not just constructs/themes
- For process work: sequence, phases, and transition logic specified (not a static X→Y)
- Boundary conditions / scope stated (where it holds, weakens, reverses)
- The move yields a non-obvious implication or lets readers re-see a familiar phenomenon
- Borrowed social theory used with its real machinery, precisely, not as ornament
- Inductive: theory is output, with a planned process figure and explicit novelty
- Deductive: each hypothesis derived from the shared mechanism; moderators motivated
Anti-patterns
- Box-and-arrow or theme-list models with no mechanism ("constructs in search of a story")
- "Theory by adjective" — naming a pattern instead of explaining how it works
- Variance framing forced onto a process phenomenon (or vice versa)
- Critique that denounces without producing a theoretical account
- Name-dropping Bourdieu/Foucault/Weick without using the framework's actual logic
- A contribution stated as a finding ("we find X") rather than a usable theoretical move
Output format
【Contribution type】process model / reconceptualization / extension / critical / synthesis
【Core mechanism】actors + structure + generative/processual logic
【Process structure (if applicable)】phases + transition logic
【Boundary conditions】where it holds / weakens / reverses
【Social theory engaged】framework + how its machinery is used
【Novel move】the non-obvious implication or re-seeing
【Next skill】orgstud-literature-positioning© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Organization-Studies-Skills/skills/orgstud-theory-development of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Orgstud Theory Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orgstud Theory Development this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Study Plananthropics/claude-for-legal | 9.6k | 3 repos | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Study BuddyLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.5k | Automated safety check: Pass | MIT | |
| Integration Theoryparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~929 | Automated safety check: Notes | MIT | |
| Event Studybrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Portfolio Case Study Writerdavila7/claude-code-templates | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Study Buddy
LeoYeAI/openclaw-master-skills
When user asks to study, create flashcards, take a quiz, make notes, revise, set study timer, track study hours, create study plan, explain a topic, test knowledge, do spaced repetition, summarize a…
Integration Theory
parcadei/Continuous-Claude-v3
Problem-solving strategies for integration theory in measure theory
Event Study
brycewang-stanford/Auto-Empirical-Research-Skills
A skill your agent uses whenever the user wants to conduct an event study, create event study plots, test for parallel trends, implement difference-in-differences designs, or work with any panel…
Portfolio Case Study Writer
davila7/claude-code-templates
Transform resume bullets into detailed portfolio case studies with context, action, and outcome.
Statistical Theory Analysis
aiming-lab/AutoResearchClaw
Analyze theoretical properties of statistical methods under the formal formulation: identifiability, bias, variance, consistency, asymptotics, coverage, error bounds, robustness, and limitations.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Orgstud Theory Development
What does Orgstud Theory Development do?
A skill your agent uses when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution. Orgstud Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution.
When should I use Orgstud Theory Development?
Orgstud Theory Development fits situations like: building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism; conceptual move that constitutes the contribution.
How do I install Orgstud Theory Development in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a claude-code`. Or copy the skill folder (Organization-Studies-Skills/skills/orgstud-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/orgstud-theory-development in your project. Claude Code loads it when a task matches its description.
How do I install Orgstud Theory Development in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a codex`. Or copy the skill folder (Organization-Studies-Skills/skills/orgstud-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/orgstud-theory-development in your project. Codex loads it when a task matches its description.
Can I use Orgstud Theory Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-theory-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orgstud-theory-development, .gemini/skills/orgstud-theory-development, .github/skills/orgstud-theory-development and .opencode/skills/orgstud-theory-development in your project.
What does Orgstud Theory Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Orgstud Theory Development is instructions for the agent only.
Does Orgstud Theory Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Orgstud Theory Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Orgstud Theory Development use?
Orgstud Theory Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Orgstud Theory Development use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Orgstud Theory Development?
Skills that share tags, products or a category with Orgstud Theory Development: Study Plan (anthropics/claude-for-legal, 9.6k stars), Study Buddy (LeoYeAI/openclaw-master-skills, 2.2k stars), Integration Theory (parcadei/Continuous-Claude-v3, 3.9k stars) and Event Study (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orgstud Theory Development?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.