isr-writing-style
Use when polishing the prose, structure, abstract, and notation of an Information Systems Research (ISR) manuscript — front-loading the IS contribution, writing for a sociotechnical and intradisciplinary readership, keeping the 300-word abstract and double-anonymized text, and following INFORMS author-date style. Late-stage polish; do not invoke while the contribution or identification/proof is still unsettled.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isr-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 (isr-writing-style) ## When to trigger - The argument is sound but the prose buries it, is jargon-heavy, or is passive - The abstract is over length or does not state the contribution - Notation is inconsistent (analytical papers) or constructs drift (behavioral papers) - You need a final pass before `isr-submission` ## Front-load the IS contribution ISR readers span behavioral, economic, design-science, and organizational backgrounds, so the introduction must make the **contribution to IS** legible to all of them quickly: the phenomenon, why the IT artifact makes it an IS question, the gap/tension in a named IS conversation, what you do, and what you find. Do not make a reviewer reverse-engineer the point from the results. Because ISR is intradisciplinary, name the bridge you build (e.g., an economic lens on a behavioral phenomenon) early and in plain language. ## Write for two audiences without losing either In an analytical paper, give the **intuition before the algebra** — every key result should have a one-sentence plain-language reading so behavioral readers can follow it. In a behavioral paper, define constructs precisely and avoid undefined formalism. Multim
- When to trigger
- Front-load the IS contribution
- Write for two audiences without losing either
- Abstract, notation, and consistency
- INFORMS style and double-anonymization
- Checklist
- Anti-patterns
- Style execution pass for Information Systems Research
- Output format
What does the isr-writing-style skill do?
Use when polishing the prose, structure, abstract, and notation of an Information Systems Research (ISR) manuscript — front-loading the IS contribution, writing for a sociotechnical and intradisciplinary readership, keeping the 300-word abstract and double-anonymized text, and following INFORMS author-date style. Late-stage polish; do not invoke while the contribution or identification/proof is still unsettled.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isr-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.