Agent skill

misq-literature-positioning

Use when positioning a MIS Quarterly manuscript inside the right information-systems conversation — engaging canonical IS work, showing the IT artifact is central, and distinguishing the paper from adjacent IS venues (ISR, JMIS, JAIS) and from the parent reference disciplines (management, economics, computer science).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill misq-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: MIS-Quarterly-Skills/skills/misq-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 (misq-literature-positioning) ## When to trigger - Your front end reads as "no one has studied X" (gap-spotting) rather than joining a conversation - A reviewer says "this belongs in [a reference discipline] journal" or "the IS contribution is unclear" - You cite mostly non-IS work and little of the canonical IS literature - You cannot articulate what an IS scholar — versus a management, economics, or CS scholar — gains ## Join an IS conversation, do not just find a gap MISQ rewards problematization over gap-spotting: surface and challenge an assumption in the existing IS literature, then show why resolving it matters. State explicitly *which* IS conversation you join (e.g., technology adoption and use, IT value and productivity, digital platforms and markets, IS security and privacy, IS development and design, the future of work). Cite the canonical anchors of that conversation, not just recent adjacent papers. ## Keep the IT artifact central The positioning must make clear the IT artifact is theorized, not incidental. If your argument would survive deleting the technology, an editor will read it as a management, economics, or CS paper wearing IS clothing.

What's inside
Steps it walks through
  1. When to trigger
  2. Join an IS conversation, do not just find a gap
  3. Keep the IT artifact central
  4. Position against adjacent venues, not just within MISQ
  5. Position against the reference disciplines
  6. Checklist
  7. Anti-patterns
  8. Positioning pass for MIS Quarterly
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the misq-literature-positioning skill do?

Use when positioning a MIS Quarterly manuscript inside the right information-systems conversation — engaging canonical IS work, showing the IT artifact is central, and distinguishing the paper from adjacent IS venues (ISR, JMIS, JAIS) and from the parent reference disciplines (management, economics, computer science).

How do I install it?

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