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.
Agent skill
Hlr Revision And Editing
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page…
Install Hlr Revision And Editing
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-revision-and-editing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-revision-and-editing --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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .claude/skills/hlr-revision-and-editing && 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 "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .claude/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editingType 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 hlr-revision-and-editing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-revision-and-editing --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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .agents/skills/hlr-revision-and-editing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .agents/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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 hlr-revision-and-editing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-revision-and-editing --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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .cursor/skills/hlr-revision-and-editing && 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 "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .cursor/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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 Harvard-Law-Review-Skills/skills/hlr-revision-and-editing--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 hlr-revision-and-editing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-revision-and-editing --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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .gemini/skills/hlr-revision-and-editing && 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 "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .gemini/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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 hlr-revision-and-editingInstalls 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 hlr-revision-and-editing -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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .github/skills/hlr-revision-and-editing && 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 "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .github/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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 hlr-revision-and-editing -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 hlr-revision-and-editing --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/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing .opencode/skills/hlr-revision-and-editing && 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 "hlr-revision-and-editing" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-revision-and-editing into .opencode/skills/hlr-revision-and-editing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-revision-and-editing", 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
hlr-revision-and-editing- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 500 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page…
- Works in 6 steps: Resolve substance before style. Settle… → Track every change across rounds. Edits… → Respond comprehensively, not… → …
- Working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds
- SKILL.md covers When to trigger, The edit cycle (round by round), Working the cycle well and Deadlines and momentum, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hlr Revision And Editing is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page proofs to publication. Drives the edit cycle to completion; it does not manage the offer/expedite phase (hlr-placement-strategy) or the first editor handshake (hlr-student-editor-review).
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds
- Responding to editor markups
- Page proofs to publication
Example prompts
- “/hlr-revision-and-editing”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Resolve substance before style. Settle the argument-level edits early; do not relitigate them once
- Track every change across rounds. Edits move footnotes and text; a fix in round one can break an
- Respond comprehensively, not selectively. Address every query in a round; partial responses cause
- Keep a clean change log. Note what you accepted, what you pushed back on, and why — it prevents
- Protect the voice and the claim; concede the rest. Defend substance and signature phrasing with
- Proof carefully, change minimally. At proofs, fix errors — do not reopen the argument.
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
Hlr Revision And Editing loads about 1.1k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 500 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). 500 words, ~1,121 tokens.
Download SKILL.mdSave it as
.claude/skills/hlr-revision-and-editing/SKILL.md (or your agent's skills folder).- name
- hlr-revision-and-editing
- description
- Use when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page proofs to publication. Drives the edit cycle to completion; it does not manage the offer/expedite phase (hlr-placement-strategy) or the first editor handshake (hlr-student-editor-review).
Revision and Editing (hlr-revision-and-editing)
After acceptance, an HLR piece goes through an intensive, multi-round editing cycle run by student editors — heavier and more iterative than at most journals. There is no single "R&R letter" as in peer review; instead there are successive passes (substantive, technical/line, Bluebook, proofs), each with deadlines. This skill keeps the cycle moving, protects the argument across rounds, and lands the piece in print without late surprises.
When to trigger
- The substantive edit is underway and rounds are stacking up
- You receive markups, queries, or new source-pull requests between rounds
- You disagree with a proposed change and must respond across a round
- Page proofs arrive and need a careful final pass
The edit cycle (round by round)
| Round | Focus | Author's job |
|---|---|---|
| Substantive round(s) | Strengthen the argument; close gaps editors flagged | Revise on the merits; defend with reasons where warranted |
| Technical / line round | Prose, clarity, house style | Approve or push back on specific edits, not en masse |
| Bluebook / cite round | Every footnote conformed and verified | Supply pincites/sources fast; fix unsupportable claims |
| Page proofs | Final typeset, last corrections | Catch errors; make only essential changes |
Working the cycle well
- Resolve substance before style. Settle the argument-level edits early; do not relitigate them once the piece moves to line and Bluebook rounds.
- Track every change across rounds. Edits move footnotes and text; a fix in round one can break an
Id. or a cross-reference in round three. Re-verify short forms after each round (see
hlr-sources-and-bluebook). - Respond comprehensively, not selectively. Address every query in a round; partial responses cause another round and slip the schedule.
- Keep a clean change log. Note what you accepted, what you pushed back on, and why — it prevents re-arguing settled points and helps the next editor.
- Protect the voice and the claim; concede the rest. Defend substance and signature phrasing with reasons; concede style and formatting to keep goodwill and momentum.
- Proof carefully, change minimally. At proofs, fix errors — do not reopen the argument.
Show full SKILL.md (167 more words)Show less
Deadlines and momentum
The cycle runs on the journal's production calendar. Responsiveness is the variable you control: fast, complete returns keep the piece on schedule and signal good faith; slow returns stall it and strain the team. Build in time for the source-pull rounds, which are the most labor-intensive for the author.
Checklist
- Substantive edits resolved before line/Bluebook rounds
- Every query in each round answered (no partial returns)
- Short forms / cross-references re-verified after each round of moves
- Source-pull requests answered with exact pincites, fast
- Change log kept (accepted / pushed back / why)
- Argument and voice protected; style conceded
- Page proofs reviewed for errors only
Anti-patterns
- Reopening settled substantive edits during the line or Bluebook round
- Partial responses that trigger extra rounds and slip the calendar
- Leaving dangling Id./supra after footnotes were reordered in a round
- Fighting every line edit and exhausting editor goodwill
- Introducing new argument at page proofs
Output format
【Round】substantive / technical / Bluebook / proofs
【Open queries】count + the hard ones
【Short forms re-verified】after this round's moves? [Y/N]
【Change log】updated (accepted / pushed back / why)? [Y/N]
【Deadline】next return date
【Next】next round → publication (loop hlr-student-editor-review for relationship issues)Supplementary resources
../../resources/official-source-map.md— HLR editorial process and publication schedule../../resources/external_tools.md— change-tracking and citation-management tools for the cycle
© 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 Harvard-Law-Review-Skills/skills/hlr-revision-and-editing of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hlr Revision And Editing 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 |
|---|---|---|---|---|---|---|
| Hlr Revision And Editing this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Research PipelineImbad0202/academic-research-skills | 51k | — | ~15k | Automated safety check: Pass | Custom licence | |
| Math Modeling Competition WorkflowXiaoMaColtAI/math-modeling-skill | 1.9k | — | ~1.2k | Automated safety check: Pass | None | |
| Social Science Paper Writingfakerqwq/social-science-paper-writing-skill | 382 | — | ~7k | Automated safety check: Pass | None | |
| Modeling Code and Result Contractsyushui2022/MathModel-Skill | 454 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
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.
Math Modeling Competition Workflow
XiaoMaColtAI/math-modeling-skill
Three-role workflow for math modeling contests: problem analysis, code and results, then a paper, with independent subagent checks at each stage gate.
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.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
PRISMA Systematic Review Writer
keemanxp/slr-prisma
Guides you through writing a systematic literature review to the PRISMA 2020 checklist, producing a journal-format Word manuscript, a flow diagram and APA 7th references.
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 Hlr Revision And Editing
What does Hlr Revision And Editing do?
A skill your agent uses when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page…. Hlr Revision And Editing is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds, responding to editor markups, and page proofs to publication.
When should I use Hlr Revision And Editing?
Hlr Revision And Editing fits situations like: working through the Harvard Law Review (HLR) post-acceptance editing cycle — successive substantive and technical edit rounds; responding to editor markups; page proofs to publication.
How do I install Hlr Revision And Editing in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-revision-and-editing -a claude-code`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-revision-and-editing in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hlr-revision-and-editing in your project. Claude Code loads it when a task matches its description.
How do I install Hlr Revision And Editing in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-revision-and-editing -a codex`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-revision-and-editing in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hlr-revision-and-editing in your project. Codex loads it when a task matches its description.
Can I use Hlr Revision And Editing 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 hlr-revision-and-editing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hlr-revision-and-editing, .gemini/skills/hlr-revision-and-editing, .github/skills/hlr-revision-and-editing and .opencode/skills/hlr-revision-and-editing in your project.
What does Hlr Revision And Editing need to run?
SKILL.md names no scripts, command-line tools or credentials: Hlr Revision And Editing is instructions for the agent only.
Does Hlr Revision And Editing 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 Hlr Revision And Editing 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 Hlr Revision And Editing use?
Hlr Revision And Editing 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 Hlr Revision And Editing use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Hlr Revision And Editing?
Skills that share tags, products or a category with Hlr Revision And Editing: Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars), Academic Research Pipeline (Imbad0202/academic-research-skills, 51k stars), Math Modeling Competition Workflow (XiaoMaColtAI/math-modeling-skill, 1.9k 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 Hlr Revision And Editing?
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.