Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
A skill your agent uses when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission.
Install Jru Referee Strategy
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-referee-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-referee-strategy --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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .claude/skills/jru-referee-strategy && 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 "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .claude/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategyType 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 jru-referee-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-referee-strategy --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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .agents/skills/jru-referee-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .agents/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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 jru-referee-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-referee-strategy --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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .cursor/skills/jru-referee-strategy && 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 "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .cursor/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy--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 jru-referee-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-referee-strategy --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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .gemini/skills/jru-referee-strategy && 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 "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .gemini/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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 jru-referee-strategyInstalls 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 jru-referee-strategy -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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .github/skills/jru-referee-strategy && 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 "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .github/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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 jru-referee-strategy -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 jru-referee-strategy --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-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy .opencode/skills/jru-referee-strategy && 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 "jru-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy into .opencode/skills/jru-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-referee-strategy", 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
jru-referee-strategy- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 859 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission.
- Works in 5 steps: Assign the paper to its two most likely… → For every objection, decide: already… → Move the evidence that disarms the top… → …
- Anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission
- SKILL.md covers When to trigger, Who reviews for JRU, and what…, How to wargame and The questions a JRU report…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jru Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission. Wargames the report a risk/uncertainty specialist would write; it does not invent evidence or citations.
Its SKILL.md is about 1.7k 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, covering Capture the flag, Peer review and Citation management. 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
- Anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission
- Tasks that involve Capture the flag
- Tasks that involve Peer review
Example prompts
- “/jru-referee-strategy”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Assign the paper to its two most likely referee types and write their harshest one-paragraph objection each.
- For every objection, decide: already answered (point to the section), answerable with existing data (add an exhibit), or a genuine…
- Move the evidence that disarms the top objection into the main text — do not leave your best defense in an appendix the referee may skim.
- Pre-write the limitations paragraph: the objections you cannot fully resolve, stated before the referee does.
- Hand off to jru-submission once the predictable objections are either answered or openly conceded.
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
Jru Referee Strategy loads about 1.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 859 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). 859 words, ~1,668 tokens.
Download SKILL.mdSave it as
.claude/skills/jru-referee-strategy/SKILL.md (or your agent's skills folder).- name
- jru-referee-strategy
- description
- Use when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission. Wargames the report a risk/uncertainty specialist would write; it does not invent evidence or citations.
Referee Strategy (jru-referee-strategy)
When to trigger
- The draft is nearly done and you want to pre-empt the objections a JRU referee will raise
- You are choosing what to put in the main text vs. the appendix to disarm predictable pushback
- The paper makes a strong EU-vs-alternatives claim and you expect a referee from the camp it challenges
- You suspect the elicitation or the VSL identification has a soft spot a specialist will find
Who reviews for JRU, and what they hunt for
JRU's reviewer pool is specialized — decision theorists, experimental risk researchers, and VSL/insurance empiricists, under a single-blind model typical of Springer econ journals (待核实). Each subculture has a signature objection. Wargame the report by reading the paper as each of these referees would.
| Referee type | Their reflex objection | Pre-empt by |
|---|---|---|
| Decision theorist | "The representation has no behavioral content / the reference point is fit, not fixed" | Stating one prediction the model forbids; fixing the reference point a priori (jru-theory-model) |
| Experimentalist | "The elicitation is not incentive-compatible / it confounds u and w" | Defending the mechanism's IC assumptions; a design that separates curvature from weighting (jru-identification) |
| VSL / empirical economist | "Selection into risky jobs / publication-selection bias is ignored" | Selection probes and engagement with the meta-analytic benchmark (jru-identification, jru-robustness) |
| EU loyalist | "A risk-averse EU agent with a pessimistic belief explains this" | Deriving a comparative static EU cannot produce; separating beliefs from preferences |
| Methods skeptic | "Functional form drives the result" | Showing the parameter is stable across CRRA/CARA/expo-power and EU/non-EU (jru-robustness) |
How to wargame
- Assign the paper to its two most likely referee types and write their harshest one-paragraph objection each.
- For every objection, decide: already answered (point to the section), answerable with existing data (add an exhibit), or a genuine limitation (state it candidly).
- Move the evidence that disarms the top objection into the main text — do not leave your best defense in an appendix the referee may skim.
- Pre-write the limitations paragraph: the objections you cannot fully resolve, stated before the referee does.
- Hand off to
jru-submissiononce the predictable objections are either answered or openly conceded.
The questions a JRU report almost always asks
Regardless of referee type, certain questions recur in this journal's reports. Have an answer ready for each:
- What exactly does your model predict that expected utility does not? — the single most common decision-theory probe.
- How do you separate utility curvature from probability weighting (or risk from ambiguity)? — the measurement probe.
- Is the elicitation incentive-compatible, and under what assumptions? — the experimental probe.
- Does the headline parameter survive a different functional form? — the methods probe.
- For VSL/insurance: is the effect a preference, or a belief / selection artifact? — the empirical probe.
If any of these has no crisp answer in the main text, fix the paper before the referee writes the report.
Worked second pass: choosing what to promote
After wargaming, rank the objections by lethality and move the one analysis that defuses the most lethal objection into a numbered main-text result, not a robustness footnote. A referee who finds the decisive check in Appendix C may still write "the authors do not address X" simply because they did not reach it. Promotion is cheap insurance in a single-blind specialist process where the referee's first impression carries weight.
Show full SKILL.md (319 more words)Show less
Checklist
- The two most likely referee types are named and their sharpest objection written out
- The decision-theorist's "no behavioral content" objection is pre-empted
- The experimentalist's incentive-compatibility / u-vs-w objection is pre-empted
- The EU-loyalist alternative explanation is addressed with a discriminating prediction
- For VSL/insurance: selection and publication-selection objections are met
- The best defense lives in the main text, not an appendix
- A candid limitations paragraph states what cannot be resolved
Suggesting and excluding reviewers
In a small specialist pool the reviewer suggestions carry weight:
- Suggest scholars who work on your exact primitive and method, including some who might disagree but would review fairly — a credible suggestion list signals you know the field.
- Exclude only genuine conflicts (advisors, recent coauthors, direct rivals with a stake) and say why briefly; a long exclusion list reads as fear of scrutiny.
- Anticipate that the editor may still pick a referee from the camp your paper challenges — write the paper to survive that draw, do not try to route around it.
Anti-patterns
- Writing only for a friendly referee and ignoring the camp the paper challenges
- Leaving the decisive robustness check in the appendix where a skimming referee misses it
- Treating "a referee might dislike non-EU" as unanswerable instead of giving EU its fair test
- Hiding a known limitation and hoping no specialist notices — they will
- Generic "reviewer 2" cynicism instead of mapping objections to this journal's actual subcultures
Worked vignette (illustrative)
A CPT-based experiment expects two referees: a decision theorist and an EU loyalist. The theorist's objection — "your reference point is chosen to fit" — is pre-empted by fixing it to the status quo a priori and showing the fit is not improved by freeing it. The loyalist's objection — "risk-averse EU with pessimism does the same" — is met by a treatment that varies probabilities at fixed outcomes, producing the inverse-S weighting that EU cannot generate. Both defenses are promoted into the main text before submission.
Output format
【Journal】Journal of Risk and Uncertainty
【Skill】jru-referee-strategy
【Verdict】defensible / patch / concede
【Likely referees】<two types>
【Top objection】<one paragraph> → answered / addable / limitation
【Best defense location】main text [Y/N]
【Limitations stated】[Y/N]
【Source status】verified / 待核实 / not asserted
【Next skill】jru-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
Files
Just SKILL.md in Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jru Referee Strategy 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 |
|---|---|---|---|---|---|---|
| Jru Referee Strategy this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Academic Research Suite for CodexImbad0202/academic-research-skills-codex | 12k | — | ~12k | Automated safety check: Pass | Custom licence | |
| Social Science Paper Writingfakerqwq/social-science-paper-writing-skill | 382 | — | ~7k | Automated safety check: Pass | None | |
| Review Papermaxwell2732/paper-replicate-agent-demo | 137 | 2 repos | ~1.1k | Automated safety check: Pass | None |
Similar skills
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
Social Science Paper Writing
fakerqwq/social-science-paper-writing-skill
Helps draft, diagnose, review and revise social science papers, from topic and research question to literature review, citation risks and pre-submission checks.
Review Paper
maxwell2732/paper-replicate-agent-demo
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
00 Academic Router
agentscope-ai/OpenJudge
A skill your agent uses when the user wants help with academic papers or citations but it's unclear which specific workflow fits — reviewing a paper, checking a BibTeX file for fake references, or…
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…
Related
Categories
Questions about Jru Referee Strategy
What does Jru Referee Strategy do?
A skill your agent uses when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission. Jru Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission.
When should I use Jru Referee Strategy?
Jru Referee Strategy fits situations like: anticipating likely referee objections for a Journal of Risk and Uncertainty (JRU) manuscript before submission; tasks that involve Capture the flag; tasks that involve Peer review.
How do I install Jru Referee Strategy in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-referee-strategy -a claude-code`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jru-referee-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Jru Referee Strategy in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-referee-strategy -a codex`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jru-referee-strategy in your project. Codex loads it when a task matches its description.
Can I use Jru Referee Strategy 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 jru-referee-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jru-referee-strategy, .gemini/skills/jru-referee-strategy, .github/skills/jru-referee-strategy and .opencode/skills/jru-referee-strategy in your project.
What does Jru Referee Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Jru Referee Strategy is instructions for the agent only.
Does Jru Referee Strategy 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 Jru Referee Strategy 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 Jru Referee Strategy use?
Jru Referee Strategy 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 Jru Referee Strategy use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Jru Referee Strategy?
Skills that share tags, products or a category with Jru Referee Strategy: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), Academic Research Suite for Codex (Imbad0202/academic-research-skills-codex, 12k stars) and Social Science Paper Writing (fakerqwq/social-science-paper-writing-skill, 382 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jru Referee Strategy?
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.