Stats
Actions
Tags
From isr-skills
Frames research results into an explicit contribution for ISR manuscripts and drafts the mandatory 500-word cover letter contribution statement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/isr-skills:isr-contribution-framingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Results exist but the "so what for IS?" is thin or implicit
Since June 1, 2023, ISR requires a ~500-word contribution statement in every cover letter. It must articulate the novel, rigorous, original contribution to IS — what the paper adds beyond existing literature and why it matters. Generic or missing statements are returned for revision, so this is not boilerplate; it is the first thing the EIC reads at the fit gate before a Senior Editor is assigned. Draft it to answer, concretely: What did we not know? What do we now know? Why does it matter for IS scholarship and for practice/policy/society?
ISR is sociotechnical and intradisciplinary, so the strongest contributions:
The cover-letter statement and the manuscript must agree. State the contribution explicitly in the introduction (the "we show that…" sentences) and revisit it in the discussion with implications for theory, for IS practice, and — where apt — for policy or society, plus honest boundary conditions and future work. Do not leave the contribution implicit for the reader to infer.
Run this as a concrete capability pass. First lock the digital artifact or system, user/firm behavior, identification or design evidence, and IS-theory contribution; then test whether the manuscript addresses IS reviewers who expect digital-technology theory, empirical or design leverage, and implications for organizations or markets.
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 statement (~500 words)】drafted? [...]
【IS conversation advanced】[...]
【Intradisciplinary bridge】[...]
【IT-artifact dependence】[...]
【Genre fit】insight / mechanism / artifact
【Intro & discussion alignment】[...]
【Next step】isr-tables-figures or isr-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin isr-skillsPositions ISR manuscripts in the IS literature by naming conversations, bridging silos (behavioral/economic/design-science/organizational), and engaging IS scholarship.
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.
Sharpens the theoretical contribution of a JAIS manuscript—states what the paper adds to IS knowledge, matches the contribution claim to the chosen category, and makes it legible to a theory-forward reviewer pool.