Agent skill · Code Review & Quality

hlr-preemption-check

Use when verifying that a Harvard Law Review (HLR) argument has not already been made — the law-review "preemption check" run across SSRN, Westlaw/Lexis, HeinOnline, and Google Scholar BEFORE drafting. Confirms originality and refines the claim; it does not draft the thesis (hlr-thesis-and-contribution) or the literature engagement in the body.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-preemption-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Harvard-Law-Review-Skills/skills/hlr-preemption-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Preemption Check (hlr-preemption-check) In legal scholarship, **"preemption"** means: has someone already published your argument? Running this search **before** you write is the single highest-return habit in the field — discovering that your claim appeared in a 2024 article *after* you have drafted 25,000 words is the classic wasted summer. A clean preemption check both protects originality and sharpens your contribution against the nearest prior work. ## When to trigger - You have a candidate thesis and have not yet written the body - You are about to claim "no one has argued X" or "first to address Y" - A draft is done and you want to confirm nothing close appeared while you wrote - An editor or colleague says "isn't this just [Author]'s point?" ## Where to search (run all four; do not stop at one) | Source | What it catches | Note | |--------|-----------------|------| | **SSRN / bepress** | Working papers and forthcoming articles not yet in print | Catches the most recent, still-in-press work — the highest preemption risk | | **Westlaw / Lexis** journals databases | Published law-review articles, full text | Use field-restricted and date-restricted queries | | **HeinOnline**

What's inside
Steps it walks through
  1. When to trigger
  2. Where to search (run all four; do not stop at one)
  3. How to search well
  4. Reading the result (three outcomes)
  5. Checklist
  6. Anti-patterns
  7. Preemption is not the same as the literature review
  8. Worked micro-pattern (illustrative)
  9. Output format
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the hlr-preemption-check skill do?

Use when verifying that a Harvard Law Review (HLR) argument has not already been made — the law-review "preemption check" run across SSRN, Westlaw/Lexis, HeinOnline, and Google Scholar BEFORE drafting. Confirms originality and refines the claim; it does not draft the thesis (hlr-thesis-and-contribution) or the literature engagement in the body.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hlr-preemption-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going