Agent skill

orgstud-literature-positioning

Use when staking the contribution of an Organization Studies (OS) manuscript against the specific theoretical conversation it joins — what the field knows, what it misses, and the precise gap this paper closes. Positions the argument; it does not build the theory (see orgstud-theory-development) or run analysis.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-literature-positioning --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Organization-Studies-Skills/skills/orgstud-literature-positioning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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

# Literature Positioning (orgstud-literature-positioning) ## When to trigger - The theory exists (from `orgstud-theory-development`) but the paper does not say *whose conversation* it advances or *what it changes* - The literature review is a catalogue ("X did A, Y did B, Z did C") with no argument - A reviewer says "this is well-known," "you're not engaging the right literature," or "what's new relative to [canonical OS work]?" - The framing claims to advance institutional/process/practice theory but cites it only in passing ## Positioning is an argument, not a survey At OS, the literature section is where you **earn the right to make a theoretical claim**. It is not a neutral map of prior work; it is a constructed account of a *specific conversation* that sets up exactly the gap your theory fills. OS reviewers — often the very scholars who built these conversations — judge whether you have (1) identified the *right* interlocutors, (2) read them accurately and generously, and (3) located a gap that is real, non-trivial, and closable with your evidence. The standard OS move: **synthesize the conversation into a tension or unresolved problem**, then show that existing accounts canno

What's inside
Steps it walks through
  1. When to trigger
  2. Positioning is an argument, not a survey
  3. Locate the conversation precisely
  4. Differentiate from sibling outlets in the framing
  5. Checklist
  6. Anti-patterns
  7. Worked vignette: from gap-spotting to tension (illustrative)
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the orgstud-literature-positioning skill do?

Use when staking the contribution of an Organization Studies (OS) manuscript against the specific theoretical conversation it joins — what the field knows, what it misses, and the precise gap this paper closes. Positions the argument; it does not build the theory (see orgstud-theory-development) or run analysis.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-literature-positioning --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 984 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