A skill your agent uses 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…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .claude/skills/jmis-writing-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .claude/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .agents/skills/jmis-writing-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .agents/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .cursor/skills/jmis-writing-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .cursor/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .gemini/skills/jmis-writing-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .gemini/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .github/skills/jmis-writing-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .github/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-writing-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style .opencode/skills/jmis-writing-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jmis-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style into .opencode/skills/jmis-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-writing-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
jmis-writing-styleA skill your agent uses 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…
Jmis Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jmis Writing Style loads about 2k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 1,046 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 1,046 words, ~2,023 tokens.
.claude/skills/jmis-writing-style/SKILL.md (or your agent's skills folder).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.
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 the contribution — in plain sentences a busy editor can scan. Do not pad it with background or cite prior work. (检索于 2026-06；以官网为准.)
Because JMIS sits at the technology–organization–economics nexus, the prose should keep the IT artifact load-bearing and surface the managerial/economic implication as a first-class thread, not an afterthought paragraph. Translate statistical findings into managerial language where it helps (what a firm/platform should do), without overclaiming past the evidence. Define IS constructs precisely and use them consistently; explain reference-discipline machinery for an IS reader rather than assuming it.
JMIS uses numbered bracketed citations [9] with an alphabetized reference list, not author-date. Write so the argument reads cleanly with numeric cites (avoid "as Author (2020) argued" constructions that assume author-date), and confirm references are formatted to JMIS's numbered style before submission. (检索于 2026-06；以官网为准.)
Read only page one and ask: can a JMIS editor name the technology, the managerial/economic question, the gap, and what you show? If any is missing, the intro is too slow. A reliable JMIS opening moves in four beats: (1) a concrete IT/management phenomenon a reader cares about; (2) the tension or gap in the IS conversation; (3) "in this paper we show that…" with the contribution and its magnitude; (4) why it matters for IS theory and for managers/firms/platforms. Save the extended literature for the positioning section — do not make the reader earn the contribution.
Before: a 190-word abstract that spends three sentences on background, cites two papers, and ends "implications are discussed." After: a 140-word, citation-free abstract — "Using the staggered redesign of a marketplace's ranking algorithm, we show that personalization reduced marginal-seller retention by 6 percentage points, shrinking buyer-side variety; the effect is concentrated among supply-constrained categories, implying platforms should temper personalization where seller supply is thin" — plus four keywords. It states setting, method, result with magnitude, and the managerial contribution, and it obeys the ≤150-word, no-citation rule.
JMIS prose goes into a fully anonymized file, so the writing itself must not leak authorship. Phrase self-citations in the third person ("Prior work [12] shows…", not "In our earlier study we showed…"); avoid "as we have argued elsewhere"; keep acknowledgments, grant numbers, and institution names out of the draft; and do not name a proprietary dataset or platform in a way that fingerprints the author. These are stylistic habits, not just submission mechanics — building them into the prose now means the jmis-submission anonymization check finds nothing to fix.
IS readers are unforgiving about loose construct language. Decide on one term per construct and use it everywhere — do not drift between "IT capability," "digital capability," and "technology resource" for the same thing, or between "platform openness" and "API accessibility" if you mean one concept. Define each construct at first use and keep the definition stable through theory, measurement, and discussion. When you import a reference-discipline term (e.g., a specific elasticity, a game-theoretic equilibrium concept), gloss it for the IS reader rather than assuming fluency. Precision here is not pedantry: a referee who sees a construct shift names mid-paper will doubt the measurement and the theory.
Writing-style is the final pass, so run it only after the mechanism, identification, contribution, and exhibits are settled — polishing prose around a moving argument wastes effort and risks locking in sentences you will have to cut. When you do polish, make one full pass for argument flow (does each section advance the claim?), one for construct and citation consistency, and one for sentence-level economy. Then write the abstract last, against the finished intro.
【Intro】contribution on page 1? "we show that…" explicit? [Y/N]
【Abstract】≤150 words, citation-free, magnitude + keywords? [Y/N]
【IS-management thread】artifact load-bearing; managerial payoff visible? [Y/N]
【Citation style】reads with numbered cites; refs in JMIS numbered format? [Y/N]
【Next step】jmis-submission© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Jmis Writing Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jmis Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2k | Automated safety check: Pass | MIT | |
| Crim Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~975 | Automated safety check: Pass | None | |
| Est Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~798 | Automated safety check: Pass | None | |
| Jaar Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~760 | Automated safety check: Pass | None | |
| Jcf Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~669 | Automated safety check: Pass | None | |
| Joc Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~873 | Automated safety check: Pass | None |
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Criminology (ASC / Wiley) manuscript so it reads for an interdisciplinary criminology audience, follows the journal's APA-based style, and uses…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of a Journal of the American Academy of Religion (JAAR) article so it is clear, analytic, gender-neutral, and readable across the study…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Corporate Finance (JCF) manuscript — the ≤250-word abstract, 1–7 keywords, author-date (Harvard) in-text citations, and the…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35…
franklee16/academic-research-skills
A skill your agent uses when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Categories
A skill your agent uses 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…. Jmis Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Jmis Writing Style fits situations like: A body that reads for a method-literate but management-minded IS audience; tasks that involve Brand voice and tone.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a claude-code`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jmis-writing-style in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a codex`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jmis-writing-style in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-writing-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jmis-writing-style, .gemini/skills/jmis-writing-style, .github/skills/jmis-writing-style and .opencode/skills/jmis-writing-style in your project.
SKILL.md names no scripts, command-line tools or credentials: Jmis Writing Style is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Jmis Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jmis Writing Style: Crim Writing Style (franklee16/academic-research-skills, 223 stars), Est Writing Style (franklee16/academic-research-skills, 223 stars), Jaar Writing Style (franklee16/academic-research-skills, 223 stars) and Jcf Writing Style (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
