Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit.
Install Jpart Rebuttal
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-rebuttal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-rebuttal --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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .claude/skills/jpart-rebuttal && 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 "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .claude/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttalType 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 jpart-rebuttal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-rebuttal --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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .agents/skills/jpart-rebuttal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .agents/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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 jpart-rebuttal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-rebuttal --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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .cursor/skills/jpart-rebuttal && 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 "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .cursor/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal--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 jpart-rebuttal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jpart-rebuttal --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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .gemini/skills/jpart-rebuttal && 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 "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .gemini/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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 jpart-rebuttalInstalls 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 jpart-rebuttal -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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .github/skills/jpart-rebuttal && 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 "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .github/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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 jpart-rebuttal -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 jpart-rebuttal --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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal .opencode/skills/jpart-rebuttal && 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 "jpart-rebuttal" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal into .opencode/skills/jpart-rebuttal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jpart-rebuttal", 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
jpart-rebuttal- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 698 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit.
- Works in 6 steps: Read the editor's letter as the rubric.… → One point-by-point response, every… → Concede or rebut explicitly, with… → …
- Writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit
- SKILL.md covers When to trigger, Strategy, Triage table for a JPART R&R and Response-letter format, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jpart Rebuttal is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit. JPART reviews are detailed and developmental, so the response must convert each reviewer while keeping the theoretical contribution intact. Structures the response letter; it does not fabricate new results.
Its SKILL.md is about 1.6k 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 Peer review. 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
- Writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit
- Tasks that involve Peer review
Example prompts
- “/jpart-rebuttal”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read the editor's letter as the rubric. The editor signals which points are decisive (often the
- One point-by-point response, every comment addressed. Quote each comment, then respond. Never
- Concede or rebut explicitly, with evidence. For each: did what was asked (say where, with the new
- Reconcile conflicting reviewers openly. When R2 wants the opposite of R3, say so, choose a
- Protect the theory contribution. Add robustness and clarifications; resist changes that turn the
- Update the public package. Re-verify the data and code so every new table/figure re-runs, and
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
Jpart Rebuttal loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 698 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). 698 words, ~1,550 tokens.
Download SKILL.mdSave it as
.claude/skills/jpart-rebuttal/SKILL.md (or your agent's skills folder).- name
- jpart-rebuttal
- description
- Use when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit. JPART reviews are detailed and developmental, so the response must convert each reviewer while keeping the theoretical contribution intact. Structures the response letter; it does not fabricate new results.
R&R Rebuttal (jpart-rebuttal)
A JPART R&R is the normal path to publication, and its reviews are detailed and developmental — they report perceived strengths/weaknesses, the basis for the decision, and advice on how to proceed. Treat the reviews as a roadmap. The response letter must move every reviewer toward yes while keeping the editor confident the public-management theory contribution survives the revision.
When to trigger
- An R&R decision arrived and you are planning the revision + response letter
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer requests analyses that would change the paper's claims
- Writing the cover note to the editor summarizing the revision
Strategy
- Read the editor's letter as the rubric. The editor signals which points are decisive (often the theoretical contribution and the identification/common-method threat). Solve those first.
- One point-by-point response, every comment addressed. Quote each comment, then respond. Never skip one — silence reads as non-compliance.
- Concede or rebut explicitly, with evidence. For each: did what was asked (say where, with the new text/table number), or push back respectfully with a reason (theory, design, or evidence). Developmental reviewers respect a well-argued disagreement over a hollow capitulation.
- Reconcile conflicting reviewers openly. When R2 wants the opposite of R3, say so, choose a principled path, and explain the tradeoff to the editor.
- Protect the theory contribution. Add robustness and clarifications; resist changes that turn the paper into a policy report or strip the mechanism. Defend scope conditions rather than over-claiming.
- Update the public package. Re-verify the data and code so every new table/figure re-runs, and
keep the Data Availability Statement current (see
jpart-transparency-and-data); keep the revised manuscript double-blind.
Triage table for a JPART R&R
| Comment signal | Who owns the call | Default move in the response |
|---|---|---|
| Editor flags it as decisive | editor | solve first, headline it in the cover note |
| "This is atheoretical / no mechanism" | author + editor | strengthen the theory move; make the mechanism observable |
| "This is common-method bias / selection" | author | add a separate-source/sensitivity analysis; report honestly |
| Two reviewers want opposite things | editor | pick a principled path, explain the tradeoff openly |
| Reviewer asks for an analysis that would change the claim | author + editor | run it, then defend or re-scope the contribution honestly |
| Reviewer wants the result generalized beyond design | author | add scope conditions; resist over-claiming |
Response-letter format
For each reviewer comment:
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].Open with a short summary of the main changes to the editor; group by reviewer; end each entry with the location of every change so the editor can verify quickly.
Show full SKILL.md (279 more words)Show less
Worked micro-example (illustrative)
A hypothetical R&R on a representative-bureaucracy survey experiment draws three reviews. The editor's letter names two decisive points (the mechanism for passive→active representation, and a common-method concern). R2 wants the formal framing cut; R3 wants it expanded. The disciplined letter opens with a three-sentence summary to the editor, addresses the mechanism and common-method points first with new text/table locations (adding a separate-source outcome and a sensitivity analysis), then reconciles R2/R3 by keeping a compact theory section in the main text and moving the extended derivation to the supplement — stating the tradeoff explicitly. Of 27 comments, 27 receive a quoted response; 19 are conceded with a change location, 8 are rebutted with a reason. (Counts illustrative.)
Referee-pushback patterns and the JPART repair
- "The revision turned the paper into a policy report." → Restore the theory framing; lead the discussion with implications for public-management theory, not just for practice.
- "New tables don't match the deposited package." → Re-run the public data-and-code so every revised exhibit reproduces; update the Data Availability Statement.
- "You ignored a comment." → Silence reads as non-compliance; quote and answer every one, even to say why you respectfully disagree.
- "Capitulation weakened the mechanism." → A well-argued disagreement is respected more than a hollow concession; defend the scope conditions that carry the contribution.
Calibration anchors (hedged)
- Treat the editor's letter as the rubric; JPART decisions rest on the editors' read of detailed, developmental reviews.
- The decisive axis is usually the theory contribution + the PA-specific threat (common-method, selection) — answer both head-on.
- Exact decision-category language and review mechanics can change — confirm against the journal's current author guidelines before quoting them in the letter.
Output format
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Theory contribution protected】no drift into policy report? [Y/N]
【Anonymity + public package updated】[Y/N]
【Next】resubmit via Editorial ExpressSupplementary resources
../../resources/official-source-map.md— decision process, developmental-review description
© 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-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jpart Rebuttal 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 |
|---|---|---|---|---|---|---|
| Jpart Rebuttal this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
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.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
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 Jpart Rebuttal
What does Jpart Rebuttal do?
A skill your agent uses when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit. Jpart Rebuttal is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit.
When should I use Jpart Rebuttal?
Jpart Rebuttal fits situations like: writing the response to a Journal of Public Administration Research and Theory (JPART) revise-and-resubmit; tasks that involve Peer review.
How do I install Jpart Rebuttal in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-rebuttal -a claude-code`. Or copy the skill folder (Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jpart-rebuttal in your project. Claude Code loads it when a task matches its description.
How do I install Jpart Rebuttal in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-rebuttal -a codex`. Or copy the skill folder (Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-rebuttal in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jpart-rebuttal in your project. Codex loads it when a task matches its description.
Can I use Jpart Rebuttal 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 jpart-rebuttal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jpart-rebuttal, .gemini/skills/jpart-rebuttal, .github/skills/jpart-rebuttal and .opencode/skills/jpart-rebuttal in your project.
What does Jpart Rebuttal need to run?
SKILL.md names no scripts, command-line tools or credentials: Jpart Rebuttal is instructions for the agent only.
Does Jpart Rebuttal 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 Jpart Rebuttal 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 Jpart Rebuttal use?
Jpart Rebuttal 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 Jpart Rebuttal use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 Jpart Rebuttal?
Skills that share tags, products or a category with Jpart Rebuttal: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jpart Rebuttal?
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.