title: Examples description: Four complete hand-overs from the user-agreements skill, each from a single request by a fictional company: a fitness app, a B2B SaaS, a connected camera and a photo community.
Examples¶
Each example starts from one message a fictional company sent and shows everything the skill handed back: the drafts, the annotations with the legal basis of each clause, the open points for counsel, and the implementation register for the product team. The companies and products are invented; any likeness to a real business is unintended.
| Example | Markets | What was asked for |
|---|---|---|
| Fitness app subscription | Germany, Austria, California, New York | subscription terms, withdrawal information, checkout and cancellation requirements |
| B2B SaaS for manufacturers | Germany, France, Italy, Ohio, Texas, California | master subscription terms, data processing agreement, sub-processor changes |
| Connected camera EULA | Germany, the Netherlands, United States | EULA for app and firmware, cloud plan terms, privacy notice, packaging and setup requirements |
| Photo community with user content | EU (Germany, France, Spain), United States | terms of service, moderation policy, notice and complaint flows, product requirements |
How to read them:
- Start with the example's overview page: the request, the questions the skill asked back, and the list of files.
- Read
annotations.mdnext. Its applicability table shows which laws the skill applied, which it ruled out and which it left open, and why. - Then the drafts, then
open-points.mdandimplementation-requirements.md.
Where a draft was corrected after review, the overview page lists the correction and its legal basis. Everything else is shown as the skill produced it, including its assumptions and the questions it left for counsel.
The drafts are illustrations for review by a qualified lawyer, not legal advice and not ready-to-use terms. Law as of 20 October 2026.