Expect
millionco/expect
A skill your agent uses when editing .tsx/.jsx/.css/.html, React components, pages, routes, forms, styles, or layouts.
A skill your agent uses when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate…
MITAuto-check passed
Install Jmis Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .claude/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .claude/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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-Management-Information-Systems-Skills/skills/jmis-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 jmis-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .agents/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .agents/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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 jmis-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .cursor/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .cursor/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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-Management-Information-Systems-Skills/skills/jmis-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 jmis-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .gemini/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .gemini/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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 jmis-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 jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .github/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .github/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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 jmis-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 jmis-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-Management-Information-Systems-Skills/skills/jmis-review-process .opencode/skills/jmis-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 "jmis-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process into .opencode/skills/jmis-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jmis-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.
Facts
- Skill name
jmis-review-process- GitHub stars
- 1.2k
- Token cost
- ~2k tokens
- SKILL.md length
- 982 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate…
- Calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led
- SKILL.md covers When to trigger, How JMIS review actually runs, Read the decision letter for… and What the EIC-led model means…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Double-anonymized review by Associate Editors and expert referees
What it does
Jmis Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing. Sets expectations and revision posture; it does not draft the response letter (jmis-rebuttal).
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.
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.
When your agent uses it
- Calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led
- Double-anonymized review by Associate Editors and expert referees
- Likely decision types
Example prompts
- “/jmis-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jmis Review Process loads about 2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 982 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 982 words, ~1,966 tokens.
Download SKILL.mdSave it as
.claude/skills/jmis-review-process/SKILL.md (or your agent's skills folder).- name
- jmis-review-process
- description
- Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing. Sets expectations and revision posture; it does not draft the response letter (jmis-rebuttal).
Review Process (jmis-review-process)
When to trigger
- Before submitting, to understand who decides and how long it takes at JMIS
- A decision letter arrived and you need to read its severity correctly before responding
- You are weighing JMIS against MISQ/ISR/JAIS on process and turnaround
- You want to know what a desk-reject vs. a review-and-reject signals
How JMIS review actually runs
JMIS is an Editor-in-Chief-led journal: founding and current EIC Vladimir Zwass receives submissions directly by email and steers the process. Papers are refereed in a double-anonymized process by internationally recognized expert referees and by Associate Editors on the Editorial Board. Practically, this means:
- The EIC is the first gate. A paper that is out of scope (not an IS-management/economics question), over length, or not anonymized can be returned or desk-rejected before external review. Fit is judged against JMIS's management/economics-of-IS identity, not generic IS breadth.
- AEs and referees carry the substantive review. Expect method-literate referees who will press on identification (empirical), assumptions and insight (analytical), measurement and CMB (behavioral), and utility-vs-baselines (design-science) — and on whether the contribution matters for IS management.
- Decisions typically span reject, major revision, minor revision, and (rarely on a first round) accept. A major revision is an opportunity, not a soft reject; a reject-and-resubmit is distinct from a revision and resets the clock. (检索于 2026-06；以官网为准.)
Read the decision letter for what it is asking
| Signal in the letter | What it usually means | Posture |
|---|---|---|
| "Contribution to IS is unclear / incremental" | A framing problem, possibly fatal if the question is not IS-management-shaped | Revisit jmis-contribution-framing; consider fit |
| "Identification / endogeneity" (empirical) | Reviewers doubt the causal claim | Strengthen design/analysis before reframing |
| "Construct validity / common-method bias" (behavioral) | Measurement is not trusted | Fix measurement model; re-test CMB |
| "Robustness / generalizability" | Effect believed but not yet solid | Add robustness; bound the claim |
| Desk return for length/anonymization | Process, not substance | Fix and resubmit per jmis-submission |
What the EIC-led model means for you, concretely
Because intake is the EIC's email and the EIC steers assignment, two things follow that a portal-driven journal would not surface. First, scope discipline is front-loaded: the EIC can return a paper that is not an IS-management/economics question before it ever reaches a referee, so the time you spend at jmis-topic-selection and jmis-contribution-framing is the cheapest insurance against a fast return. Second, the AE is your interlocutor on the substance: the AE synthesizes the referees and signals the editorial direction, so when you eventually respond (jmis-rebuttal) you are persuading the AE that concerns are resolved, not just answered. Read the AE letter as the decision; read the referee reports as the evidence the AE is weighing.
Match the review style to your evidence type
The substantive pressure differs by archetype, and anticipating it shortens the cycle:
| Archetype | Where referees press hardest |
|---|---|
| IT-value / firm econometrics | endogeneity of IT investment; whether the design supports a causal verb |
| platform / e-commerce | selection on platform data; whether the network mechanism is identified, not assumed |
| behavioral survey / experiment | construct validity, discriminant validity, common-method bias, manipulation realism |
| analytical / economic model | the assumptions, and whether the insight survives relaxing them |
| design-science / ML | utility vs. credible baselines and managerial relevance, not algorithmic novelty |
Calibrate timing and expectations
JMIS is a quarterly with a single EIC and a board of AEs; turnaround depends on referee availability, so plan for a multi-month first round and budget real time for a major revision. Exact current turnaround statistics are 待核实 — check the journal page or recent author reports rather than assuming. Treat a major-revision invitation as a genuine path to acceptance if you can answer the substantive concerns, and do not confuse it with a reject.
Show full SKILL.md (384 more words)Show less
Checklist
- You know the decision type (desk return / reject / reject-resubmit / major / minor / accept) and what resets the clock
- The binding concern is classified (fit / identification / measurement / robustness / process)
- You have separated fatal framing problems from fixable evidence gaps
- Expectations on timing are realistic for an EIC-led quarterly
- Any quoted turnaround/acceptance statistic is marked 待核实 unless sourced
- The revise-vs-reroute decision rule has been applied to the binding concern
- The AE letter, not the raw referee reports, is read as the decision signal
Anti-patterns
- Reading a major revision as a polite rejection (or vice versa)
- Responding before classifying whether the core problem is fit, evidence, or process
- Assuming a fast portal-style turnaround — this is an EIC-led email process
- Treating a desk return for length/anonymization as a substantive rejection
- Quoting acceptance rates or review times as fact without a source
- Revising a paper whose core problem is fit, on sunk-cost grounds, instead of rerouting
- Treating the referee reports as the decision rather than the AE's synthesizing letter
- Underestimating how front-loaded scope discipline is in an EIC-managed intake
Decide whether to revise or reroute
Not every revision invitation is worth taking, and a clean reject sometimes signals a fit problem better solved by rerouting. Use a simple decision rule: if the binding concern is fit/contribution and the question is not really an IS-management/economics question, a revision will likely fail again — reconsider whether MISQ, ISR, JAIS, or an economics/CS venue is the true home before reinvesting. If the binding concern is evidence (identification, measurement, robustness) and you can plausibly produce the missing analysis within the revision window, a major revision is a genuine path to acceptance. If it is process (length, anonymization, scope-of-claims), fix and resubmit. Sunk-cost reasoning — "we already emailed it to JMIS" — is not a reason to revise a paper whose question belongs elsewhere.
Set author expectations before the wait
Tell coauthors what an EIC-led quarterly looks like so silence is not misread: a multi-month first round is normal, a major revision is the most common positive first-round outcome at a top journal, and the AE's letter — not the harshest referee — sets the agenda for the revision. Decide up front who will own which class of revision (identification, measurement, exhibits, prose) so that when the letter arrives the team moves into jmis-rebuttal without relitigating roles.
Output format
【Decision type】desk-return / reject / reject-resubmit / major / minor / accept
【Binding concern】fit / identification / measurement / robustness / process
【Fatal vs. fixable】[...]
【Timing expectation】realistic horizon (statistics 待核实)
【Next step】jmis-rebuttal (if revision) or revisit earlier skill (if framing/fit)© 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
Files
Just SKILL.md in Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jmis 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 |
|---|---|---|---|---|---|---|
| Jmis Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~2k | Automated safety check: Pass | MIT | |
| Expectmillionco/expect | 3.6k | — | ~988 | Automated safety check: Pass | MIT | |
| CLI Anything CalibreHKUDS/CLI-Anything | 52k | — | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| RuView Room Calibrationruvnet/RuView | 97k | — | ~320 | Automated safety check: Pass | MIT | |
| Trust Calibratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Information Security Manager Iso27001davila7/claude-code-templates | 32k | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
CLI Anything Calibre
HKUDS/CLI-Anything
Command-line interface for Calibre - A stateful CLI harness for e-book library management, metadata editing, and format conversion wrapping the real Calibre tools (calibredb, ebook-convert…
RuView Room Calibration
ruvnet/RuView
Run the ADR-151 per-room calibration pipeline — baseline → enroll → extract → train → a bank of small specialists…
Trust Calibrator
sickn33/agentic-awesome-skills
One sentence - what this skill does and when to invoke it. An agent skill from sickn33/agentic-awesome-skills.
Information Security Manager Iso27001
davila7/claude-code-templates
Senior Information Security Manager specializing in ISO 27001 and ISO 27002 implementation for HealthTech and MedTech companies.
Implementing Iso 27001 Information Security Management
mukul975/Anthropic-Cybersecurity-Skills
Guides implementation of an ISO/IEC 27001:2022 Information Security Management System (ISMS) end to end: gap analysis and scoping, risk assessment methodology, Annex A control selection, Statement…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
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…
Aaag Literature Positioning
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…
Aaag Rebuttal
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…
Aaag Research Design
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…
Aaag Review Process
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…
Aaag Submission
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…
Questions about Jmis Review Process
What does Jmis Review Process do?
A skill your agent uses when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate…. Jmis Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led, email-intake, double-anonymized review by Associate Editors and expert referees, likely decision types, and timing.
When should I use Jmis Review Process?
Jmis Review Process fits situations like: calibrating expectations for the Journal of Management Information Systems (JMIS) editorial process — the EIC-led; double-anonymized review by Associate Editors and expert referees; likely decision types.
How do I install Jmis Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-review-process -a claude-code`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jmis-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Jmis Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-review-process -a codex`. Or copy the skill folder (Journal-of-Management-Information-Systems-Skills/skills/jmis-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jmis-review-process in your project. Codex loads it when a task matches its description.
Can I use Jmis Review Process in Cursor, Gemini CLI or GitHub Copilot?
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-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/jmis-review-process, .gemini/skills/jmis-review-process, .github/skills/jmis-review-process and .opencode/skills/jmis-review-process in your project.
What does Jmis Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Jmis Review Process is instructions for the agent only.
Does Jmis Review Process access the network?
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.
Is Jmis Review Process safe to install?
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.
What licence does Jmis Review Process use?
Jmis 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.
How many tokens does Jmis Review Process use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jmis Review Process?
Skills that share tags, products or a category with Jmis Review Process: Expect (millionco/expect, 3.6k stars), CLI Anything Calibre (HKUDS/CLI-Anything, 52k stars), RuView Room Calibration (ruvnet/RuView, 97k stars) and Trust Calibrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jmis Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.