legal-review
Skill16 starsChanged 18 days agoMITView on GitHub
The legal agent's method - read the founder's playbook and the region packs, grade each checklist item GREEN, YELLOW, RED or UNSETTLED with a cited and dated source, draft documents flagged for counsel, escalate. Use at setup, before launches, and on features touching personal data, payments, children, AI output or marketing claims.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- anyreachai/claude-skillstheir own version, first seen Nov 8, 2026
- mobeetle/legalsuitetheir own version, first seen Nov 1, 2026
- Frog1205/OPC-Skillstheir own version, first seen Jun 18, 2026
- hmzainjamil/claude-ai-skillstheir own version, first seen May 10, 2026
- hmzainjamil/claude-ai-systemtheir own version, first seen May 10, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- hmzainjamil/claude-ai-skills★ 3same name
- hmzainjamil/claude-ai-system★ 2same name
- anyreachai/claude-skills★ 1same name
- mobeetle/legalsuite★ 1same name
- Frog1205/OPC-Skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository120 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-agentic-workflow.mdcCursor rule
- .cursor/rules/agent-android-dev.mdcCursor rule
- .cursor/rules/agent-architect.mdcCursor rule
- .cursor/rules/agent-backend-dev.mdcCursor rule
- .cursor/rules/agent-dashboard.mdcCursor rule
- .cursor/rules/agent-debugger.mdcCursor rule
- .cursor/rules/agent-desktop-dev.mdcCursor rule
- .cursor/rules/agent-devops.mdcCursor rule
- .cursor/rules/agent-explainer-writer.mdcCursor rule
- .cursor/rules/agent-feasibility.mdcCursor rule
- .cursor/rules/agent-growth.mdcCursor rule
- .cursor/rules/agent-ios-dev.mdcCursor rule
- .cursor/rules/agent-legal.mdcCursor rule
- .cursor/rules/agent-optimizer.mdcCursor rule
- .cursor/rules/agent-orchestrator.mdcCursor rule
- .cursor/rules/agent-platform-architect.mdcCursor rule
- .cursor/rules/agent-platform-designer.mdcCursor rule
- .cursor/rules/agent-product-designer.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-researcher.mdcCursor rule
- .cursor/rules/agent-reviewer.mdcCursor rule
- .cursor/rules/agent-rollback.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/agent-setup.mdcCursor rule
- .cursor/rules/agent-social-media.mdcCursor rule
- .cursor/rules/agent-web-dev.mdcCursor rule
- .cursor/rules/skill-bug-fix.mdcCursor rule
- .cursor/rules/skill-commit.mdcCursor rule
- .cursor/rules/skill-context-budget.mdcCursor rule
- .cursor/rules/skill-cost-audit.mdcCursor rule
- .cursor/rules/skill-decision-log.mdcCursor rule
- .cursor/rules/skill-experiment.mdcCursor rule
- .cursor/rules/skill-founder-voice.mdcCursor rule
- .cursor/rules/skill-frontend-design.mdcCursor rule
- .cursor/rules/skill-gates.mdcCursor rule
- .cursor/rules/skill-grilling.mdcCursor rule
- .cursor/rules/skill-handoff.mdcCursor rule
- .cursor/rules/skill-human-design.mdcCursor rule
- .cursor/rules/skill-human-steps.mdcCursor rule
- .cursor/rules/skill-karpathy-guidelines.mdcCursor rule
- .cursor/rules/skill-known-reds.mdcCursor rule
- .cursor/rules/skill-legal-review.mdcCursor rule
- .cursor/rules/skill-new-feature.mdcCursor rule
- .cursor/rules/skill-observability.mdcCursor rule
- .cursor/rules/skill-ordered-steps.mdcCursor rule
- .cursor/rules/skill-performance.mdcCursor rule
- .cursor/rules/skill-readiness-gate.mdcCursor rule
- .cursor/rules/skill-release.mdcCursor rule
- .cursor/rules/skill-requirement-first.mdcCursor rule
- .cursor/rules/skill-safe-data-write.mdcCursor rule
- .cursor/rules/skill-setup.mdcCursor rule
- .cursor/rules/skill-single-source.mdcCursor rule
- .cursor/rules/skill-spec-audit.mdcCursor rule
- .cursor/rules/skill-tailoring.mdcCursor rule
- .cursor/rules/skill-twin-check.mdcCursor rule
- .cursor/rules/skill-verified-claims.mdcCursor rule
- .cursor/rules/skill-verify-green.mdcCursor rule
- bug-fixSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Not legal advice: Every output says so first, and lists what a lawyer should review.
- Distinctive: line 30
Every grade cites a primary source where one exists (the law, the regulator's guidance) and the date it was checked.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated by tools/sync_adapters.py from skills/legal-review/SKILL.md. Edit the source, not this file. -->Legal review
Not legal advice. Every output says so first, and lists what a lawyer should review.
Read
project.toml: regions, domain, audience, customer size, sensitive, andorigin: a rebuild of an existing app adds the playbook's "Rebuilding an existing app" row to every launch review.docs/legal/playbook.md: the founder's positions (what we accept, what we escalate).docs/legal/regions/<CODE>.mdfor each region. A region with no pack is itself a RED.- The feature's spec, design and UX files.
Grade
For every applicable item in each pack's checklist:
| Item | Grade | Evidence in the product | Source | Checked |
- GREEN met; YELLOW met with a gap or an assumption, stated; RED not met, blocks launch; UNSETTLED the law's status is unclear or sources disagree, with both sources.
- Every grade cites a primary source where one exists (the law, the regulator's guidance) and the date it was checked. Law changes; an undated claim is worthless in six months.
- Packs older than 90 days are re-checked before a launch, and
python tools/link_check.py docs/legal/regions/*.mdshows no DEAD links. - Each claim in a pack carries a short quote from the source it cites, so a reviewer can check it without trusting the agent that wrote it.
Draft
Policies and notices go to docs/legal/drafts/ with DRAFT, NOT LEGAL ADVICE, REVIEW WITH
COUNSEL as the first line: privacy policy, terms, cookie notice, AI disclosure, refund policy,
DPA for business customers. Write for the product as it is, from the spec and design, never
copied from another company.
Escalate
Any RED, any UNSETTLED on the launch path, sensitive data categories, automated decisions about people, cross-border transfers, enterprise contracts, regulator contact: to the founder, with a recommendation to involve counsel and the exact questions to ask them.
Report in docs/work/<id>/legal.md (feature) or docs/legal/launch-<date>.md (launch).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

