law-review-editor
From the author
Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.
Install
npx skills add lawve-ai/awesome-legal-skills --skill law-review-editor -a claude-code
Installs to .claude/skills/law-review-editor/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (APACHE-2.0) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- paper-reviewbrycewang-stanford/Auto-Empirical-Research-SkillsUse when a paper is complete or near-complete and a holistic pre-submission audit is needed. Cross-cuts text, code, tables, figures, results, citations, and reproducibility in a single pass and produces a persistent audit report. Works standalone on papers written outside the plugin.Science★ 4.7K
- paper-polishbrycewang-stanford/Auto-Empirical-Research-SkillsProofread and verify academic papers in LaTeX. Runs 19 sequential checks covering titles, consistency, citations, formatting, theoretical tension in motivation, concise results reporting, cross-section repetition, em-dash usage, and auxiliary-text-to-footnote conversion. Trigger when user says "check paper" / "proofread" / "paper-checker" / "校对" / "核查论文".Science★ 4.7K
- make-content-two-pass-editgooseworks-ai/goose-skillsEdits an existing draft in order: a substance pass (arguable thesis, swap test, fakes removed, CTA fit), a claims and fact check that cuts or softens unproven lines, a readability and voice-match pass, then an AI-tell sweep, with an edit note listing open gaps. Use alone when you already have a finished draft and the brand's voice samples and approved claims; otherwise run make-content.Writing★ 1.3K
- proofreadpedrohcgs/claude-code-my-workflowRead-only proofreading pass over lecture `.tex` or `.qmd` files. Checks grammar, typos, overflow, terminology consistency, and academic writing quality; produces a report without editing. Use when user says "proofread", "check for typos", "look for grammar issues", "copy-edit this", "any writing errors?", or before a lecture release.Writing★ 1.7K
- reader-first-technical-editlawve-ai/awesome-legal-skillsEdit mathematically, empirically, or technically dense papers for readers outside the author’s specialty, including empirical legal scholarship, law-and-economics models, and legal-technology research. Clarifies terminology, antecedents, study design, and claim–statistic relationships while checking equations, numbers, quotations, and citations against the source. Use to clarify exposition or de-jargonize a technical draft; not to rewrite briefs or doctrinal arguments. Produces an edited draft and audit memo. Full integrity checks and original-format rendering require suitable extraction, code execution, and document tools; otherwise provides proposed edits with verification limits disclosed.Writing★ 888
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.Engineering★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in