Agent skill · Design & Presentation

isr-literature-positioning

Use when positioning an Information Systems Research (ISR) manuscript in the IS literature — naming the conversation(s) you join, bridging behavioral, economic, design-science, and organizational IS silos, and showing the intradisciplinary move that ISR prizes. Positions the work; it does not build the mechanism (isr-theory-development) or write the contribution statement (isr-contribution-framing).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isr-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: Information-Systems-Research-Skills/skills/isr-literature-positioning/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

# Literature Positioning (isr-literature-positioning) ## When to trigger - Your front end lists references but does not name a live IS conversation - The paper sits in one silo when an intradisciplinary framing was available - A reviewer says "this does not engage the IS literature" or "the contribution to IS is unclear" - You cite reference-discipline work (econ, psych, CS) but not the IS scholarship that owns the phenomenon ## Join a conversation, don't catalog a gap ISR reviewers reward work that **enters an ongoing IS conversation** and changes it, not work that merely spots an unfilled cell in a table. Identify the specific stream — e.g., platform competition, digital labor, IT and firm value, security economics, recommender/algorithmic systems, knowledge collaboration, digital transformation — and state what that stream currently believes, what tension or anomaly you address, and how your result moves it. ## Bridge IS silos — the intradisciplinary move ISR's defining mission is **intradisciplinary**: it prizes work that integrates **behavioral, design-science, economic, and organizational** perspectives rather than single-paradigm contributions. Positioning is where you make

What's inside
Steps it walks through
  1. When to trigger
  2. Join a conversation, don't catalog a gap
  3. Bridge IS silos — the intradisciplinary move
  4. Engage IS, not only the reference disciplines
  5. Checklist
  6. Anti-patterns
  7. Positioning pass for Information Systems Research
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the isr-literature-positioning skill do?

Use when positioning an Information Systems Research (ISR) manuscript in the IS literature — naming the conversation(s) you join, bridging behavioral, economic, design-science, and organizational IS silos, and showing the intradisciplinary move that ISR prizes. Positions the work; it does not build the mechanism (isr-theory-development) or write the contribution statement (isr-contribution-framing).

How do I install it?

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