Clean Data
Aperivue/medsci-skills
A skill your agent uses when a clinical CSV/Excel dataset needs profiling and cleaning before analysis (missing values, outliers, duplicates, type mismatches).
A skill your agent uses when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks…
Install Wber Referee Strategy
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-referee-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .claude/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .claude/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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/World-Bank-Economic-Review-Skills/skills/wber-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 wber-referee-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .agents/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .agents/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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 wber-referee-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .cursor/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .cursor/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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 World-Bank-Economic-Review-Skills/skills/wber-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 wber-referee-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .gemini/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .gemini/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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 wber-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 wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .github/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .github/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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 wber-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 wber-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/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy .opencode/skills/wber-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 "wber-referee-strategy" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/World-Bank-Economic-Review-Skills/skills/wber-referee-strategy into .opencode/skills/wber-referee-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wber-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
wber-referee-strategy- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 875 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks…
- Policy relevance) and writing the cover letter
- SKILL.md covers When to trigger, Who referees WBER — and what…, The predictable WBER… and The cover letter, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Resume and CV writing
What it does
Wber Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks (external validity, identification, data quality, policy relevance) and writing the cover letter. Plans defenses; it does not run new analysis.
Its SKILL.md is about 1.8k 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 Business, Finance & HR, covering Resume and CV writing, Peer review and Data cleaning. 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
- Policy relevance) and writing the cover letter
- Tasks that involve Resume and CV writing
- Tasks that involve Peer review
Example prompts
- “/wber-referee-strategy”
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
Wber Referee Strategy loads about 1.8k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 875 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). 875 words, ~1,776 tokens.
Download SKILL.mdSave it as
.claude/skills/wber-referee-strategy/SKILL.md (or your agent's skills folder).- name
- wber-referee-strategy
- description
- Use when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks (external validity, identification, data quality, policy relevance) and writing the cover letter. Plans defenses; it does not run new analysis.
Referee Strategy (wber-referee-strategy)
When to trigger
- The paper is near submission and you want to surface objections before a referee does
- You are writing the cover letter and choosing how to frame the contribution to the editor
- You suspect one referee will be a hard-identification economist and another a policy reader
- You want to decide which robustness checks to pre-load in the paper vs. hold for the response
- You are unsure whether the framing will survive the "is this a World Bank paper?" reflex
Who referees WBER — and what they punish
WBER's review is single-anonymized (referees are anonymous; your name is on the title page), and editors (Eric Edmonds and Nina Pavcnik, Dartmouth, 检索于 2026-06；以官网为准) draw on a development-economics referee pool that overlaps heavily with JDE, AEJ: Applied, and the AEA journals. Expect two referee archetypes and write for both:
- The identification referee — sophisticated about staggered-DiD bias, weak IV, RD manipulation, attrition, spillovers. Punishes asserted exclusion restrictions, TWFE on staggered timing, and overreach beyond the estimand.
- The policy/development referee — asks "so what for development policy?", "does this generalize?", "what about general equilibrium and cost?". Punishes project-report framing and results with no scale-up relevance.
A paper that satisfies only one archetype is the canonical WBER R&R-or-reject. Pre-empt both.
The predictable WBER objections (pre-empt in the paper)
| Likely objection | Pre-emption to build in before submitting |
|---|---|
| "This is a project report, not general-interest" | Frame around a transferable mechanism; state external validity explicitly (wber-topic-selection, wber-identification) |
| "Identification rests on an untested assumption" | Show the diagnostic that could have failed; report design-specific sensitivity (wber-identification, wber-robustness) |
| "Developing-country data quality is suspect" | Measurement-error and coverage checks against an alternative source (wber-robustness) |
| "The LATE won't survive scale-up" | Discuss complier-vs-population, GE channels, fiscal cost (wber-identification) |
| "Why WBER and not JDE / World Development?" | One intro sentence on the policy-audience contribution (wber-literature-positioning) |
| "Not reproducible" | Have the data/code package and DOI-linked DAS ready (wber-replication-package) |
The cover letter
- Name the development question and the policy decision in the first two sentences — give the editor the "why this journal" instantly.
- State the contribution as a claim with a magnitude, and the identification in one line.
- Pre-empt the sibling question: one sentence on why this is WBER, not JDE/World Development/Research Observer.
- Note the data/code package is prepared and the data availability statement is in place.
- Suggest reviewers honestly (if the portal asks) across both archetypes; flag genuine conflicts.
- Keep it under a page; do not restate the abstract verbatim.
Pre-load vs. hold in reserve
Not every check belongs in the submitted paper. Decide deliberately:
- Pre-load in the paper: the design diagnostic the identification referee will demand first (balance/pre-trends/density/first-stage), the headline robustness, and the external-validity/cost paragraph. These are cheap insurance against a fast reject.
- Hold in reserve (ready to run): exotic robustness a referee might ask for, alternative estimators that would bloat the main text, and extended heterogeneity. Have the code ready so you can produce them in one round if asked, without padding the 40 pages now.
The judgment call: anything a competent referee would certainly ask goes in the paper; anything they might ask is held, code-ready, for the response letter.
Show full SKILL.md (359 more words)Show less
Checklist
- Both referee archetypes (identification + policy) explicitly addressed in the paper
- Each predictable objection has a pre-emption already in the text, not held in reserve
- External validity / scale-up / cost is in the paper, not only the cover letter
- The "why WBER not a sibling" sentence is in both the intro and the cover letter
- Data/code package and DOI-linked DAS ready before submission
- Cover letter names the policy decision in the opening lines and states a magnitude
- Suggested reviewers (if requested) span both archetypes; conflicts disclosed
Anti-patterns
- Writing only for the identification referee and ignoring the policy reader (or vice versa)
- Holding back the obvious robustness check, hoping no one asks — they will
- A cover letter that restates the abstract and never says "why WBER"
- Leaving external validity entirely to the cover letter instead of the paper
- Assuming single-anonymized review hides the authors — your name is on the title page; reputation and self-citation are visible
- Suggesting only friendly reviewers from one camp
Self-citation and the single-anonymized reality
Because WBER review is single-anonymized, referees can see who you are — so the usual double-blind tricks do not apply and can backfire. Do not over-cite yourself to signal authority; do not strip your own relevant prior work to feign novelty (a referee who knows your record will notice). Cite your prior work where it is genuinely the right reference, in the third person, and let the contribution stand on the new result. Treat the referees as informed colleagues who may well know your earlier papers better than you expect.
Worked vignette (illustrative)
Before submitting an RD evaluation of a subsidy, the authors war-game two reports. The identification referee will challenge manipulation at the eligibility score; they pre-load a Cattaneo–Jansson–Ma density test and a donut check. The policy referee will ask whether a local-at-cutoff effect justifies a national change; they add a paragraph on the complier population and a back-of-envelope fiscal cost at scale. The cover letter opens: "Governments spend billions on means-tested subsidies but lack credible estimates of marginal effects; using [country]'s eligibility threshold we estimate a 5pp enrollment gain at $90 per enrollee." Both archetypes are answered before review begins.
Output format
【Identification referee】top objection + pre-emption in paper
【Policy referee】top objection + pre-emption in paper
【External validity / cost】in the paper? [Y/N]
【Why-WBER sentence】in intro AND cover letter? [Y/N]
【Package readiness】data/code + DOI DAS ready? [Y/N]
【Cover letter】names policy decision + magnitude in opening? [Y/N]
【Next step】wber-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 World-Bank-Economic-Review-Skills/skills/wber-referee-strategy of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wber 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 |
|---|---|---|---|---|---|---|
| Wber Referee Strategy this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Clean DataAperivue/medsci-skills | 333 | — | ~2k | Automated safety check: Pass | MIT | |
| Authoritative Data Harvesteryushui2022/MathModel-Skill | 454 | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Research Data Feasibility and Leakage ChecksLight0305/Light-skills | 640 | — | ~4.9k | Automated safety check: Pass | MIT | |
| ReviseAperivue/medsci-skills | 333 | — | ~6.7k | Automated safety check: Pass | MIT | |
| Submission Guidebrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~3.6k | Automated safety check: Pass | Custom licence |
Similar skills
Authoritative Data Harvester
yushui2022/MathModel-Skill
Finds authoritative public data sources for modeling tasks, prefers official APIs and bulk downloads, and outputs a reproducible fetch and cleaning plan with citations.
Research Data Feasibility and Leakage Checks
Light0305/Light-skills
Finds usable public datasets, judges whether the data can support a research idea, and checks train and test splits for leakage before results are trusted.
Revise
Aperivue/medsci-skills
A skill your agent uses when a manuscript comes back with reviewer or editor comments.
Submission Guide
brycewang-stanford/Auto-Empirical-Research-Skills
This skill covers academic journal submission, referee responses, and revision management.
Medical Cv Resume Builder
aipoch/medical-research-skills
Use medical cv resume builder for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.
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
Questions about Wber Referee Strategy
What does Wber Referee Strategy do?
A skill your agent uses when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks…. Wber Referee Strategy is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when anticipating referee and editor objections before submitting to The World Bank Economic Review (WBER) — pre-empting the predictable development-economics pushbacks (external validity, identification, data quality, policy relevance) and writing the cover letter.
When should I use Wber Referee Strategy?
Wber Referee Strategy fits situations like: policy relevance) and writing the cover letter; tasks that involve Resume and CV writing; tasks that involve Peer review.
How do I install Wber Referee Strategy in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-referee-strategy -a claude-code`. Or copy the skill folder (World-Bank-Economic-Review-Skills/skills/wber-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wber-referee-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Wber Referee Strategy in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wber-referee-strategy -a codex`. Or copy the skill folder (World-Bank-Economic-Review-Skills/skills/wber-referee-strategy in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wber-referee-strategy in your project. Codex loads it when a task matches its description.
Can I use Wber 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 wber-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/wber-referee-strategy, .gemini/skills/wber-referee-strategy, .github/skills/wber-referee-strategy and .opencode/skills/wber-referee-strategy in your project.
What does Wber Referee Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Wber Referee Strategy is instructions for the agent only.
Does Wber 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 Wber 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 Wber Referee Strategy use?
Wber 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 Wber Referee Strategy use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Wber Referee Strategy?
Skills that share tags, products or a category with Wber Referee Strategy: Clean Data (Aperivue/medsci-skills, 333 stars), Authoritative Data Harvester (yushui2022/MathModel-Skill, 454 stars), Research Data Feasibility and Leakage Checks (Light0305/Light-skills, 640 stars) and Revise (Aperivue/medsci-skills, 333 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wber 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.