From misq-skills
Frames results or artifacts as explicit MIS Quarterly contributions — naming the IS knowledge produced (mechanism, design principles, effect, or process), why it matters for theory and practice, and justifying the page budget.
How this skill is triggered — by the user, by Claude, or both
Slash command
/misq-skills:misq-contribution-framingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Results exist (or the artifact is evaluated) but the "so what for IS" is thin
MISQ judges contribution within whichever IS tradition the paper occupies. Name what kind of knowledge you produced.
| Tradition | The contribution is... | Make it explicit by stating... |
|---|---|---|
| Behavioral | A new or revised mechanism about IT use/impact | What we now understand about why the IT effect occurs and when it reverses |
| Design science | Generalizable design knowledge | The design principles that transfer beyond this artifact, plus their justificatory theory |
| Economics of IS | A causal/economic effect or mechanism of IT | The identified effect, its magnitude, and what it implies for markets/platforms/policy |
| Organizational | A process/variance theory of IT in context | The new construct, relationship, or contextual condition the case reveals |
MISQ values managerial, organizational, and societal relevance. After the theory contribution, state implications for managers, designers, platform/policy decisions, or users — and for the societal impact of IT where relevant. A contribution that advances theory but ignores practice (or vice versa) reads as half a MISQ paper.
Because the page limit counts everything and over-length manuscripts are returned, the contribution must be large enough to warrant the category you chose. If the "so what" fits a Research Note, do not pad it into a Research Article. Conversely, a genuine theory advance may belong in Theory Development or a Theory-Generative Research Synthesis.
Draft, for the intro and the discussion, sentences of the form: "We contribute to [named IS conversation] by showing/designing/identifying [X], which changes [prior understanding/assumption] because [mechanism/evidence]." Avoid "to the best of our knowledge, the first to..." as the whole claim.
Use this as a second-pass capability check. First lock the IS phenomenon, artifact/platform, theory mechanism, design or empirical warrant, and managerial implication; then test whether the manuscript addresses information-systems reviewers who expect strong IS theory, digital artifact or platform grounding, and evidence with organizational consequence.
claim / evidence / blocker / next edit rows so the next pass can patch the manuscript directly.resources/official-source-map.md for volatile rules and name the one unresolved fact that could change the recommendation.【Contribution type】mechanism / design principles / economic effect / process theory
【To which IS conversation】...
【Theory implication】... 【Practice/societal implication】...
【Justifies category/length?】yes / rescope
【Next step】misq-tables-figures or misq-writing-style
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin misq-skillsFrames results as an explicit contribution to a JMIS manuscript by articulating the advance to IS-management/economics conversation with theoretical and managerial implications, then aligning the introduction and discussion.
Frames research results into an explicit contribution for ISR manuscripts and drafts the mandatory 500-word cover letter contribution statement.
Positions an MIS Quarterly manuscript within the appropriate IS conversation by engaging canonical work, centralizing the IT artifact, and distinguishing from ISR, JMIS, JAIS, and reference disciplines.