Menu

Individual skill

isr-literature-positioning

0upvotes

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).

Information-Systems-Research-Skills/skills/isr-literature-positioning/SKILL.md

Read pinned source

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,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top