isr-writing-style — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited isr-writing-style (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
isr-submissionISR 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.
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. Multimethod papers should signpost transitions between methods and remind the reader how each piece serves the shared argument.
Use the INFORMS author-date reference style: references alphabetized by author, with in-text citations by author name and year. Files are double-spaced, at least 11-point font, with one-inch margins on all four sides. Keep the text double-anonymized: remove names, affiliations, and identifying acknowledgments, and word self-citations neutrally so the prose does not reveal authorship.
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.【Intro front-loading】contribution + bridge stated early? [...]
【Two-audience readability】intuition/definitions present? [...]
【Abstract】≤300 words, contribution-led? [...]
【Notation/construct consistency】[...]
【INFORMS style + format】author-date, spacing, margins: pass/fix
【Anonymization】pass/fix
【Next step】isr-submission~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.