Running CI Preflight
PostHog/posthog
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
A skill your agent uses when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length…
MITAuto-check passed
Install Hlr Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-submission --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-submission .claude/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .claude/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-submission --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-submission .agents/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .agents/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-submission --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-submission .cursor/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .cursor/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-submission --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-submission .gemini/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .gemini/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .github/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submission -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-submission --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-submission .opencode/skills/hlr-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-submission into .opencode/skills/hlr-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 745 words
- Files
- 2
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length…
- Running the final pre-submission preflight for the Harvard Law Review (HLR) via HLRs own electronic submission system — manuscript readiness
- SKILL.md covers When to trigger, Process facts (live-check only…, Preflight checklist and Anti-patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Bluebook 22nd-edition footnotes
What it does
Hlr Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length limits, Bluebook 22nd-edition footnotes, expedite setup, and season timing. Final upload checks; it does not plan the placement strategy (hlr-placement-strategy) or draft content.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `templates/checklist.md`).
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
- Running the final pre-submission preflight for the Harvard Law Review (HLR) via HLRs own electronic submission system — manuscript readiness
- Bluebook 22nd-edition footnotes
Example prompts
- “/hlr-submission”
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 Submission loads about 1.8k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 745 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). 745 words, ~1,785 tokens.
Download SKILL.mdSave it as
.claude/skills/hlr-submission/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- hlr-submission
- description
- Use when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length limits, Bluebook 22nd-edition footnotes, expedite setup, and season timing. Final upload checks; it does not plan the placement strategy (hlr-placement-strategy) or draft content.
Submission Preflight (hlr-submission)
The last check before uploading through HLR's own electronic submission system
(harvardlawreview.org). HLR does not intake through Scholastica — Scholastica/ExpressO are the
general-market platforms you use to multi-submit and expedite at peer journals
(see hlr-placement-strategy); HLR itself takes the manuscript on its own portal. Unlike a
peer-reviewed science journal, HLR receives a near-final, fully footnoted article — there is no
"revise the methods later." The most common avoidable failures are an over-length manuscript, an
incomplete footnote apparatus, skipped anonymization, and mistimed submission.
When to trigger
- "Submitting this week" — last pass before upload
- Unsure what HLR's submission system expects in the package
- Confirming the manuscript is genuinely near-final, anonymized, and pull-ready
Process facts (live-check only the items marked 待核实)
- Owner / publisher: the Harvard Law Review Association — an independent, student-run organization (editorially independent of Harvard Law School).
- Portal: HLR's own electronic submission system (Microsoft Word documents encouraged; mailing the Articles Office is a fallback). Not Scholastica. (检索于 2026-06；以官网为准 for any additional channel.)
- Review model: student-edited, reviewed anonymously; each piece is read by ≥ 3 editors and many proceed through an Articles Committee vote, a preemption check, a faculty peer-review stage, and a full-body vote. ("Student-edited" — but a faculty peer-review stage does exist; do not tell authors there is zero peer review.)
- Length (count includes text, footnotes, and appendices): Articles preferred ≤ 25,000 words; over 30,000 weighs against selection; unconditional acceptance over 37,500 is rare. Essays (Print/Forum) 12,000–17,500; Forum Responses 8,000; Commentaries 6,000; Book Review proposals a few pages.
- Anonymization (required): keep name, affiliation, bio, and acknowledgments on a separate cover page; put the title on the first text page; anonymize self-citations.
- Citations: The Bluebook, 22nd edition (HLR co-compiles it) — footnoted, pincited, signal-correct.
- Expedite: request via the unique link in your confirmation email; HLR honors requests where it can but does not omit review stages; a ≥ 7-day offer-decision window is committed.
- What HLR publishes: Articles, Essays, Book Reviews by outside authors; Notes and case/ legislation comments by student editors (student writing is unsigned); the annual Supreme Court issue (November) with the Foreword, and a Developments in the Law issue (April).
- Leadership / no fee (re-verified 2026-09-14): HLR is led by an annually-elected student President (the law-review analogue of an editor-in-chief) — Volume 140 (2026–2027) is led by Alex Zhao ('27), elected February 2026, succeeding G. Terrell Seabrooks ('26) who led Volume 139 (2025–2026); the masthead rotates ANNUALLY each volume, so re-check the current masthead before naming anyone. Article selection is by student editors, and HLR charges no submission fee / no APC — Scholastica/ExpressO fees, if any, belong to the peer-journal market, not HLR's own portal.
- Season: submit in the Feb-Mar main window or the smaller Aug window; earlier is stronger. Current intake volume/season status: 待核实 on the live page.
Show full SKILL.md (293 more words)Show less
Preflight checklist
Manuscript readiness
- Genuinely near-final — argument complete, not a draft to finish in editing
- Length within limits: Article ≤ 25k (over 30k weighs against; over 37.5k rarely accepted), counting footnotes and appendices — cut before submitting if over
- Introduction front-loads the claim and contribution (see
hlr-writing-style) - Doctrine → theory → prescription arc intact (see
hlr-argument-structure)
Anonymization & footnotes (the make-or-break)
- Anonymized: separate cover page; title on first text page; self-citations neutralized
- Every proposition pincited to the strongest authority (see
hlr-sources-and-bluebook) - Bluebook 22nd-edition formatting, signals, and short forms consistent
- Every source kept and pull-ready for the source-pull (see
hlr-footnotes-and-cite-check) - Originality confirmed and re-checked near submission (see
hlr-preemption-check)
Package & metadata (HLR submission system)
- Word manuscript (with footnotes) prepared; abstract written
- Anonymized cover page separate from the manuscript body
- CV / author info ready as the portal requires
- Submission set tiered and timed (see
hlr-placement-strategy) - Expedite mechanics understood (only with an offer in hand)
Timing & compliance
- Submitting early in a season, not mid-window into a crowded topic
- If you prefer HLR, submit it ≥ 2 weeks before sending to other journals
- Original, unpublished work; no overlapping commitment
- Current intake volume/season status confirmed on the live page (待核实) — note HLR charges no submission fee / no APC; re-check the current masthead (student President rotates annually)
Anti-patterns
- Submitting "through Scholastica" — that is the peer-journal market platform; HLR uses its own system
- An over-length manuscript (over 30k weighs against; over 37.5k rarely accepted) — and forgetting footnotes count toward the limit
- Skipping anonymization (cover page / self-citations) on an anonymously-reviewed submission
- Uploading a draft you "plan to finish in editing" — HLR expects near-final
- An incomplete or inconsistent footnote apparatus (it will not survive the source-pull)
- Single-submitting and forgoing expedite leverage (see
hlr-placement-strategy)
Output format
【Portal】HLR's own electronic submission system (NOT Scholastica)
【Length】word count incl. footnotes vs ≤25k / 30k / 37.5k thresholds — within? [Y/N]
【Anonymized】cover page + self-citations neutralized? [Y/N]
【Footnotes】pincited, Bluebook 22nd, pull-ready? [Y/N]
【Originality】preemption re-checked near submission? [Y/N]
【Timing】early in Feb-Mar / Aug season; ≥2 wks before other journals if HLR-first? [Y/N]
【Next】await offers → hlr-placement-strategy (expedite) → hlr-student-editor-review (on acceptance)Supplementary resources
templates/checklist.md— printable pre-submission checklist../../resources/official-source-map.md— official HLR submissions facts with 待核实 markers
© 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
SKILL.md and 1 other file in Harvard-Law-Review-Skills/skills/hlr-submission of brycewang-stanford/Awesome-Journal-Skills.
- SKILL.md
- templates/checklist.md
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hlr Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Running CI PreflightPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Finalize Agent Promptgithub/awesome-copilot | 40k | 1 repos | ~224 | Automated safety check: Pass | MIT | |
| Azure Deployment Preflightgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Implementation Final Reviewopenai/openai-agents-python | 30k | — | ~2k | Automated safety check: Pass | MIT | |
| Preflightopenwpm/OpenWPM | 1.4k | — | ~670 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Finalize Agent Prompt
github/awesome-copilot
Finalize prompt file using the role of an AI agent to polish the prompt for the end user.
- Official
Azure Deployment Preflight
github/awesome-copilot
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.
- Official
Implementation Final Review
openai/openai-agents-python
Review completed implementation changes before final verification.
Preflight
openwpm/OpenWPM
Use BEFORE implementing code in a crosslink-tracked project — loads .crosslink/rules/global.md, the language rules for detected manifests, the project rules, and the active tracking-<mode.md.
Preflight
openfootmanager/openfootmanager
Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Hlr Submission
What does Hlr Submission do?
A skill your agent uses when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length…. Hlr Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-submission preflight for the Harvard Law Review (HLR) via HLR's own electronic submission system — manuscript readiness, anonymization, length limits, Bluebook 22nd-edition footnotes, expedite setup, and season timing.
When should I use Hlr Submission?
Hlr Submission fits situations like: running the final pre-submission preflight for the Harvard Law Review (HLR) via HLRs own electronic submission system — manuscript readiness; bluebook 22nd-edition footnotes.
How do I install Hlr Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-submission -a claude-code`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hlr-submission in your project. Claude Code loads it when a task matches its description.
How do I install Hlr Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-submission -a codex`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hlr-submission in your project. Codex loads it when a task matches its description.
Can I use Hlr Submission 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-submission -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-submission, .gemini/skills/hlr-submission, .github/skills/hlr-submission and .opencode/skills/hlr-submission in your project.
What does Hlr Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Hlr Submission is instructions for the agent only.
Does Hlr Submission 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 Submission 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 Submission use?
Hlr Submission 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 Submission 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 Hlr Submission?
Skills that share tags, products or a category with Hlr Submission: Running CI Preflight (PostHog/posthog, 40k stars), Finalize Agent Prompt (github/awesome-copilot, 40k stars), Azure Deployment Preflight (github/awesome-copilot, 40k stars) and Implementation Final Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hlr Submission?
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.