Individual skill
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.
Information-Systems-Research-Skills/skills/isr-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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