jmis-writing-style
Use when the prose is the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — an abstract and introduction that land the IS-management contribution, and a body that reads for a method-literate but management-minded IS audience. Late-stage polish; do not invoke before the mechanism, identification, and contribution are settled.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style --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.
# Writing Style (jmis-writing-style) ## When to trigger - The mechanism, identification, and contribution are settled and the prose is the remaining gap - The abstract or introduction buries the contribution under setup or method - The paper reads like a reference-discipline manuscript (pure econ/CS) wearing an IS label - The abstract exceeds **150 words** or quietly slips in citations ## Lead with the IS-management contribution A JMIS reader is method-literate but management-minded. The introduction should reach the contribution fast: the technology, the managerial/economic question, what was not known, and what you show — stated for an IS audience, not buried under literature. The recurring failure is an intro that spends pages on background before the "we show that…" sentences. Get the IT artifact and the managerial stake on the first page. ## Write the 150-word, citation-free abstract last and tight JMIS requires an abstract of **up to 150 words** with **no citations**, plus a set of **keywords** indicating the paper's content. Draft it after the intro is stable. It should name the technology/setting, the question, the method and data, the headline result *with magnitude*, and
- When to trigger
- Lead with the IS-management contribution
- Write the 150-word, citation-free abstract last and tight
- Keep the technology and the managerial payoff visible throughout
- Match prose to JMIS's numbered-reference house style
- Tighten the prose
- A first-page test for the introduction
- Worked fix: an abstract that overruns and under-delivers (illustrative)
- Checklist
- Write so the double-blind file stays blind
- Anti-patterns
- Keep the IS vocabulary precise and consistent
- Polish last, and only once
- Output format
What does the jmis-writing-style skill do?
Use when the prose is the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — an abstract and introduction that land the IS-management contribution, and a body that reads for a method-literate but management-minded IS audience. Late-stage polish; do not invoke before the mechanism, identification, and contribution are settled.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style --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 909 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.