terms-review
Skill13 starsChanged yesterdayMITView on GitHub
Review ToS, licenses, and DPAs against an intended use.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- fmind/dotword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- fmind/dot★ 13100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository62 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dot_agents/AGENTS.mdAGENTS.md
- skills/repository-docs/references/agents.mdAGENTS.md
- claudeCLAUDE.md
- chezmoiSkill
- dot-developmentSkill
- dot-releaseSkill
- dot-skillsSkill
- acliSkill
- agent-frameworksSkill
- agent-harnessesSkill
- agent-projectSkill
- agent-protocolsSkill
- agySkill
- airflowSkill
- auth-statusSkill
- awsSkill
- bfSkill
- cfSkill
- chrome-devtoolsSkill
- clipboardSkill
- cloud-runSkill
- code-securitySkill
- colabSkill
- databricksSkill
- diagrams-as-codeSkill
- dockerSkill
- documentation-siteSkill
- dot-cliSkill
- draft-docSkill
- draft-mailSkill
- draft-typst-deckSkill
- duckdbSkill
- fmindSkill
- full-reviewSkill
- gcloudSkill
- ghSkill
- git-deliverySkill
- github-actionsSkill
- gwsSkill
- hfSkill
- humanizeSkill
- infra-as-codeSkill
- kaggleSkill
- kubernetesSkill
- miseSkill
- model-providersSkill
- playwrightSkill
- project-scaffoldingSkill
- pupSkill
- python-mlopsSkill
- python-stackSkill
- python-webSkill
- repository-docsSkill
- scheduled-jobsSkill
- skillifySkill
- <name>Skill
- task-promptsSkill
- trimSkill
- upgrade-toolsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 27
Protect private context: keep contract text and business details out of public searches, shared reports, and repo fixtures.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Terms Review
Assess whether an intended use of a product, service, or artifact fits its governing terms and user constraints. Deliver a dated, clause-backed decision—never treat silence as permission or present the review as legal advice. project-license owns choosing a repository license.
Workflow
- Define context & criteria: record product, exact version/artifact, plan, entities, jurisdictions, scale, data flows, and checkable policy/regulatory requirements (ignore badges and marketing).
- Collect & order primary texts: inspect signed agreements and incorporated docs (ToS, EULA/license, DPA, subprocessors, release model/dataset licenses) with URL/ID and effective date; resolve consumer/API/enterprise precedence and mark unavailable texts
Unresolvedinstead of reconstructing from memory. - Audit clauses: cover commercial/API/scraping/benchmark/export rights; code/weights/dataset/output licenses and copyleft compatibility (read raw license text); and confidentiality, AI training/opt-out, retention, residency, and DPA/BAA obligations alongside technical verification.
- Deliver the report: state dated verdict (
Supported,Conditional,Not supported, orUnresolved), context/assumptions, evidence matrix (requirement | document & clause | finding | status | action), ranked blockers, counsel/vendor questions, re-review triggers, and dated sources.
Boundaries
- Analysis only: accepting terms, buying, changing settings, uploading data, or contacting vendors requires separate approval; draft outreach locally.
- Protect private context: keep contract text and business details out of public searches, shared reports, and repo fixtures; search using public product names only.
Companion skills
- code-security: technical controls and dependency licenses/vulns.
- full-review: operational launch proof beyond contractual permission.
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.

