Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jais-review-process --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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .claude/skills/jais-review-process && 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 "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .claude/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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-the-Association-for-Information-Systems-Skills/skills/jais-review-processType 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 jais-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jais-review-process --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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .agents/skills/jais-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .agents/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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 jais-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jais-review-process --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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .cursor/skills/jais-review-process && 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 "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .cursor/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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-the-Association-for-Information-Systems-Skills/skills/jais-review-process--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 jais-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jais-review-process --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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .gemini/skills/jais-review-process && 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 "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .gemini/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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 jais-review-processInstalls 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 jais-review-process -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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .github/skills/jais-review-process && 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 "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .github/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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 jais-review-process -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 jais-review-process --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-the-Association-for-Information-Systems-Skills/skills/jais-review-process .opencode/skills/jais-review-process && 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 "jais-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process into .opencode/skills/jais-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jais-review-process", 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.
jais-review-processA skill your agent uses when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review…
Jais Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review; how the seven-category routing works; what a JAIS decision letter means; and when to engage the journal's developmental culture. Sets expectations and reads decisions; it does not draft the response (jais-rebuttal) or run the submission preflight (jais-submission).
Its SKILL.md is about 2.3k 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 Research & Science. 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.
Jais Review Process loads about 2.3k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 1,183 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,183 words, ~2,255 tokens.
.claude/skills/jais-review-process/SKILL.md (or your agent's skills folder).Like its Basket siblings, JAIS screens fit before it spends reviewer effort on quality — the Editor-in-Chief (or a deputy) assesses whether the paper belongs in JAIS and in the declared category before routing it for full review. This is why a technically excellent paper can be desk-rejected: not because the work is weak, but because the contribution is not a JAIS contribution, or the category is wrong. Practically, the fit screen rewards the upstream work in jais-topic-selection and jais-contribution-framing more than any amount of late polish. If you keep getting desk rejects, the problem is almost always fit or contribution, not execution.
JAIS runs a double-blind process: the Editor-in-Chief routes a submission, typically to a Senior Editor in the relevant category, who manages the review (commonly through an Associate Editor and reviewers). The distinctive feature is the journal's stated commitment to "developmental reviewing" with "an editorial board of eminent scholars engaging with authors on promising papers" — JAIS frames itself as trying to build good papers, not merely gate them. Practically: the SE's letter is the authoritative synthesis of where the paper stands and what it needs, and a developmental tone in the letter is a real signal that the editor sees promise.
The masthead changes: Monideepa Tarafdar is Editor-in-Chief (effective Sept 1, 2024); category Senior Editors (e.g., Literature Reviews — Gregory Vial; Research Perspectives — Dirk Hovorka; Foundational — Varun Grover; Policy and Impact — Roman Beck) are 待核实. Confirm at aisel.aisnet.org/jais.
Because JAIS has seven categories each with its own SE, the category you chose at submission determines who reviews you and against what bar. A Theory submission is read for generative theory; a Foundational submission for disciplined description of a novel phenomenon; a Literature Review for method and theoretical payoff. If a paper is mis-categorized, expect a fit challenge or a re-route before substantive review — which is why category selection (jais-topic-selection) is upstream of everything.
Each category's Senior Editor brings that genre's standards, so the identity of your handling editor is a clue to what your reviews will emphasize. A Theory submission routed to the Theory SE will be pressed hardest on construct novelty and generativity; a Literature Review under Gregory Vial on method and theoretical payoff; a Research Perspective under Dirk Hovorka on the strength and defensibility of the argument; a Foundational submission under Varun Grover on disciplined description of a genuinely novel phenomenon; a Policy and Impact paper under Roman Beck on the credibility of the research-to-policy bridge (SE names 待核实 — confirm before relying on them). If your paper would be stronger under a different category's bar, that is a topic-selection signal, not a review-process one.
| Decision | What it usually means | Your move |
|---|---|---|
| Desk reject | fit, theory, or contribution failed the editor's screen | re-diagnose fit/contribution; do not just resubmit |
| Reject (after review) | reviewers see a fundamental theory or design flaw | treat as terminal unless explicitly invited to resubmit |
| Major revision | promise is real but substantial work remains | the most common path to a JAIS paper — engage fully |
| Minor revision | the contribution is accepted; execution polish remains | address precisely; do not reopen settled debates |
A developmental SE letter on a major revision is closer to a roadmap than a verdict. Mine it for the editor's priorities; those, not reviewer word-count, set your revision plan.
JAIS, like its Basket siblings, runs a multi-round developmental process: an initial decision, then typically one or more rounds of major then minor revision before acceptance. Plan for this. A first-round major revision is the normal path to publication, not a near-miss; the work happens across rounds as the SE and reviewers engage the paper. Treat exact turnaround times, acceptance rates, and impact-factor figures as 待核实 — they move and vary by category — and do not let an optimistic timeline tempt you into a thin, rushed revision that squanders a developmental opening.
The Senior Editor owns the decision. When reviewers conflict, resolve in the direction the SE signals and say so. Reviewer points that the SE did not elevate still deserve a response, but the SE's synthesis is the spine of the revision. Reading the letter this way prevents the classic error of treating every reviewer comment as equally binding.
JAIS's "developmental reviewing" is a resource, not just a label. When an SE letter is constructive and specific, treat it as collaborative coaching: respond to the spirit of the editor's concern, not only its letter, and signal in the revision that you understood where the paper is trying to go. JAIS also runs activities that reflect this ethos (for example, theory-development engagement around the IS community); a paper whose authors treat reviewers as partners in building the contribution tends to fare better than one that litigates every point. This is a meaningful contrast with more gatekeeping-style processes elsewhere.
An SE writes: "All three reviewers find the phenomenon timely, but the theoretical contribution is not yet distinct from prior work; R2's identification concern is secondary to this." Read correctly, this is a developmental major revision whose single binding constraint is the theory contribution — not R2's identification point, which the SE has explicitly demoted. The revision plan should therefore lead with sharpening the construct/framework (route to jais-theory-development and jais-contribution-framing), then address identification proportionately. Spending the revision budget on robustness checks while leaving the theory thin would answer the loudest reviewer and miss the editor — the most common way a promising JAIS R&R fails.
【Journal】Journal of the Association for Information Systems (JAIS)
【Category SE / bar】who is managing and against what standard
【Decision read】desk reject / reject / major / minor
【SE priorities (ranked)】1… 2… 3…
【Reviewer conflicts】where, and resolution direction per SE
【Promise signal】developmental tone present / absent
【Source status】verified URL / 待核实 (SE names)
【Next skill】jais-rebuttal (on a revision invite)© 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-the-Association-for-Information-Systems-Skills/skills/jais-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Jais Review Process 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 |
|---|---|---|---|---|---|---|
| Jais Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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 calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review…. Jais Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental, Senior-Editor-led, double-blind review; how the seven-category routing works; what a JAIS decision letter means; and when to engage the journal's developmental culture.
Jais Review Process fits situations like: calibrating expectations for the Journal of the Association for Information Systems (JAIS) editorial process — the developmental; senior-Editor-led; double-blind review; how the seven-category routing works.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-review-process -a claude-code`. Or copy the skill folder (Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jais-review-process in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-review-process -a codex`. Or copy the skill folder (Journal-of-the-Association-for-Information-Systems-Skills/skills/jais-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jais-review-process 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 jais-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jais-review-process, .gemini/skills/jais-review-process, .github/skills/jais-review-process and .opencode/skills/jais-review-process in your project.
SKILL.md names no scripts, command-line tools or credentials: Jais Review Process 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.
Jais Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9k 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 Jais Review Process: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k 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.