Manim Video Production
browser-use/video-use
Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.
A skill your agent uses when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill.
MITAuto-check passed
Install Hlr Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-workflow --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-workflow .claude/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .claude/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-workflow --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-workflow .agents/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .agents/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-workflow --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-workflow .cursor/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .cursor/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hlr-workflow --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-workflow .gemini/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .gemini/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .github/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/hlr-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Harvard-Law-Review-Skills/skills/hlr-workflow into .opencode/skills/hlr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hlr-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 432 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill.
- Navigating any Harvard Law Review (HLR) article
- SKILL.md covers When to trigger, First question: which piece…, Routing map (stage → skill) and Default order, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Book review and you need the right next sub-skill
What it does
Hlr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill. Routes by lifecycle stage and the distinctive student-edited, multi-submit/expedite law-review process. It dispatches; it does not draft content.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Navigating any Harvard Law Review (HLR) article
- Book review and you need the right next sub-skill
Example prompts
- “/hlr-workflow”
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 Workflow loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 432 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). 432 words, ~1,270 tokens.
Download SKILL.mdSave it as
.claude/skills/hlr-workflow/SKILL.md (or your agent's skills folder).- name
- hlr-workflow
- description
- Use when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill. Routes by lifecycle stage and the distinctive student-edited, multi-submit/expedite law-review process. It dispatches; it does not draft content.
HLR Workflow Router (hlr-workflow)
The orchestrator for a Harvard Law Review submission. HLR is student-edited, not peer-reviewed, and generalist across all of law. The router's first job is to set the right mental model: you write a near-final article, run a preemption check before drafting, submit broadly across peer journals via Scholastica (but to HLR through its own submission system, not Scholastica), leverage offers with expedite requests, and then survive an intensive student-editor edit plus a full cite-check / source-pull. Figure out the stage, then dispatch.
When to trigger
- Starting a new HLR piece and unsure where to begin
- Mid-project and unsure which skill applies next
- Deciding the piece type (Article, Essay, Book Review, or a Supreme Court Foreword/Comment by invitation)
- Holding an offer and deciding whether/how to expedite (route to
hlr-placement-strategy) - An editor sent edits or a source-pull request (route to
hlr-student-editor-review)
First question: which piece type?
| Situation | Type | Route to |
|---|---|---|
| Full original legal argument, novel normative claim | Article (long, heavily footnoted) | normal pipeline below |
| Shorter, focused intervention or provocation | Essay | normal pipeline, tighter scope |
| Engaging a recent book to make an independent claim | Book Review | hlr-thesis-and-contribution + hlr-argument-structure |
| Invited Supreme Court Foreword / Comment / Term piece | Supreme Court issue | hlr-argument-structure + hlr-sources-and-bluebook (invitation-driven) |
Notes are student-written and unsigned by HLR editors — not an outside-author track. If you are not an HLR editor, you are writing an Article, Essay, or Book Review.
Routing map (stage → skill)
Is the topic timely and placeable? → hlr-topic-selection
What is the legal claim / payoff? → hlr-thesis-and-contribution
Has this argument been made already? → hlr-preemption-check
How is the argument built? → hlr-argument-structure
Are authorities cited correctly? → hlr-sources-and-bluebook
Is the footnote apparatus sound? → hlr-footnotes-and-cite-check
Does the prose read like a law review?→ hlr-writing-style
Where and when do I submit/expedite? → hlr-placement-strategy
Ready to upload (HLR's own system)? → hlr-submission
Editor sent edits / source-pull? → hlr-student-editor-review
Working through the edit cycle? → hlr-revision-and-editingDefault order
topic-selection → thesis-and-contribution → preemption-check → argument-structure → sources-and-bluebook → footnotes-and-cite-check → writing-style → placement-strategy → submission → student-editor-review → revision-and-editing
Run the preemption check early — discovering your claim was already made after drafting is the classic wasted-summer failure. Iterate thesis ↔ argument ↔ sources before polishing prose.
Show full SKILL.md (161 more words)Show less
Law-review reality check (force this before routing)
| Check | Pass condition | Route if weak |
|---|---|---|
| Student-edited model | You expect a generalist student audience, not a subfield peer panel | hlr-writing-style |
| Preemption | You have searched SSRN / Westlaw / HeinOnline and your claim is genuinely new | hlr-preemption-check |
| Normative payoff | The piece does more than describe doctrine — it argues for something | hlr-thesis-and-contribution |
| Source-pull readiness | Every proposition is pin-cited and pullable to a real source | hlr-footnotes-and-cite-check |
| Placement plan | You know the seasons and the expedite mechanics before you submit | hlr-placement-strategy |
Anti-patterns
- Treating HLR like a peer-reviewed journal — it is student-edited; pitch and process differ
- Skipping the preemption check and discovering the claim was published last year
- Submitting outside the seasons, or single-submitting when the norm is multi-submit + expedite
- A descriptive doctrinal survey with no normative thesis (generalist editors reject "no payoff")
- Loose, un-pinpointed citations that cannot survive the source-pull
Output format
【Stage】topic / thesis / preemption / argument / sources / footnotes / writing / placement / submit / edit / revise
【Type】Article / Essay / Book Review / Supreme Court (invited)
【Route to】hlr-<skill>
【Why】one line
【Then】the next skill after thatSupplementary resources
../../resources/external_tools.md— legal research databases + Bluebook/citation tooling../../resources/official-source-map.md— official HLR URLs behind every fact in this pack
© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hlr Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Manim Video Productionbrowser-use/video-use | 28k | 6 repos | ~3k | Automated safety check: Pass | MIT | |
| Logseq Review Workflow Evallogseq/logseq | 45k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill | 2.5k | 2 repos | ~3.2k | Automated safety check: Pass | None | |
| DeepTutor CLIHKUDS/DeepTutor | 41k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
Baoyu URL To Markdown
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
DeepTutor CLI
HKUDS/DeepTutor
Teaches the agent to set up and run DeepTutor from the command line: chat and capabilities, knowledge bases, partners, memory, sessions, notebooks and the server or Web app.
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
AI Engineering Placement Quiz
rohitg00/ai-engineering-from-scratch
Runs a 10-question quiz across five areas to place a learner in the AI Engineering from Scratch curriculum, so they skip what they already know.
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 Workflow
What does Hlr Workflow do?
A skill your agent uses when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill. Hlr Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when starting or navigating any Harvard Law Review (HLR) article, essay, or book review and you need the right next sub-skill.
When should I use Hlr Workflow?
Hlr Workflow fits situations like: navigating any Harvard Law Review (HLR) article; book review and you need the right next sub-skill.
How do I install Hlr Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-workflow -a claude-code`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hlr-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Hlr Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-workflow -a codex`. Or copy the skill folder (Harvard-Law-Review-Skills/skills/hlr-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hlr-workflow in your project. Codex loads it when a task matches its description.
Can I use Hlr Workflow 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-workflow -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-workflow, .gemini/skills/hlr-workflow, .github/skills/hlr-workflow and .opencode/skills/hlr-workflow in your project.
What does Hlr Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Hlr Workflow is instructions for the agent only.
Does Hlr Workflow 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 Workflow 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 Workflow use?
Hlr Workflow 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 Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.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 Workflow?
Skills that share tags, products or a category with Hlr Workflow: Manim Video Production (browser-use/video-use, 28k stars), Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars) and DeepTutor CLI (HKUDS/DeepTutor, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hlr Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.