jmis-topic-selection
Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-topic-selection --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Topic Selection (jmis-topic-selection) ## When to trigger - You have an IS/technology phenomenon but cannot say what *managerial or economic* question it answers - The work might be a better fit for MISQ, ISR, JAIS, Management Science, or a CS venue and you need to decide before investing in theory - A reviewer or colleague says "this is a technical exercise" or "where is the management contribution?" - The dataset (platform logs, firm IT spend, e-commerce transactions, security incidents) is rich but the question is not yet sharp ## What makes a question JMIS-shaped JMIS rewards questions at the **technology–organization–economics nexus**: how information systems and technology are *managed*, *valued*, and *governed*, and how they reshape firms, markets, and platforms. The strongest JMIS topics make the **technology load-bearing in an economic or managerial mechanism** — not a backdrop. Use these tests: 1. **The IS-management hinge.** Does the answer change how a manager, firm, platform, or policymaker should act on technology? "We predict churn with a new model" is CS; "we show how a recommender's design shifts platform-side seller competition and revenue" is JMIS. 2. **The eco
- When to trigger
- What makes a question JMIS-shaped
- Decision table: route by what the question is really about
- JMIS vs. its neighbors at the topic stage
- Worked vignette: from a dataset to a JMIS question (illustrative)
- Pre-commit the fit decision before theory work
- Checklist
- Topics JMIS has historically rewarded
- Anti-patterns
- Stress-test the scope before you commit
- Hand off only when fit is settled
- Output format
What does the jmis-topic-selection skill do?
Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-topic-selection --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.