Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/business-tools/general-legal-assistant/skills/terms-generator

terms-generator

Verified

Draft service-specific terms from confirmed features, business decisions and scoped applicability review, with clear assumptions and a separate review record. Use when preparing or revising website or app terms. Trigger with "terms-generator" or "create terms of service".

FileKindSize
SKILL.mdskill md6.8 KB
references/service-terms-review.mdmarkdown4.9 KB

references/service-terms-review.md

View on GitHub
# Service terms evidence and review

## Establish the actual service

Record entity/service scope, source versions/URLs and inspection dates. Separate
owner-provided facts, actual observations, unverified signals, proposed decisions
and unknowns. Read-only fetches or code searches do not prove every deployed
feature, account setting, data flow or customer type.

Do not publish credentials, private customer data or raw logs in the review record.
Do not collect new personal information, make purchases or change a live service
to investigate the draft. Use the requested scope and supplied evidence.

## Sixteen candidate sections

| Topic                | Confirm or decide before drafting                                                           |
| -------------------- | ------------------------------------------------------------------------------------------- |
| Agreement/version    | Intended acceptance mechanism, audience, version and actual effective-date decision.        |
| Service description  | Features/limits actually offered; distinguish future proposals.                             |
| Accounts             | Registration, security and actual eligibility/age practices when relevant.                  |
| Acceptable use       | Requested conduct rules and supported enforcement/moderation process.                       |
| User content         | Actual upload/sharing model, ownership and license scope needed for the service.            |
| Provider IP          | Actual rights, third-party dependencies and requested restrictions; no invented ownership.  |
| Payments             | Currency/fees, billing triggers, taxes and actual refund/dispute procedures where relevant. |
| Trials/subscriptions | Actual renewal, cancellation, notices and operational behavior if offered.                  |
| Privacy relationship | Real notice route and role of disclosure, separate from consent/choice implementation.      |
| Third-party services | Actual relationships and dependencies; an SDK import is not the whole arrangement.          |
| Warranties           | Requested allocation and applicable-context review; not an automatic "as-is" insertion.     |
| Liability            | Proposed cap/base/exceptions and legal questions; no generic universal amount.              |
| Indemnification      | Requested duties, covered claims and interactions with other provisions.                    |
| Termination          | Actual grounds/process/effects, surviving duties and user-data handling.                    |
| Law/disputes         | Actual selected jurisdiction/procedure and applicable consumer/legal constraints.           |
| General/contact      | Definitions, amendments, precedence, severability and verified notice contacts.             |

Use relevant sections. Sixteen headings, a privacy paragraph or a waiver clause do
not prove completeness, compliance or enforceability. Explain omitted topics and
material unknowns in review rather than filling them with confident boilerplate.

## Applicability and consistency

Business type, location, audience and actual activity matter. Do not infer GDPR
applicability from Euro pricing or CCPA applicability merely from a US entity.
Different roles may carry different obligations. Check current primary law and
identified jurisdiction before making a legal assertion; leave unsupported claims
unresolved rather than copying a fixed framework list.

A document does not create a working cancellation button, rights-request process,
consent state, payment security program or accessibility outcome. Match descriptions
to verified operations and identify any gap. Do not promise a capability because a
vendor provides it as an optional feature.

Review notice links, definitions, UGC licenses, payment/termination interactions,
plain-language summaries and actual version/date choices. Keep proposed business
terms separate from established practices, and preserve decisions already supplied
or delegated by the user.

## Copy, review and sources

Keep reader-facing copy separate from technical evidence and unresolved questions.
A draft with material unknowns must remain a draft; do not invent contacts or dates
to make it look final. Do not publish or accept terms without the appropriate scope.

If a template is used, verify its actual passage/version/license and label any
adaptation. A generator website, vendor claim or plausible clause is not proof of
legal suitability for the transaction.

Primary starting points reviewed 2026-10-25:

- [CPPA FAQ](https://cppa.ca.gov/faq): official agency information distinguishes
  applicability and roles; it is not an individualized legal opinion.
- [ICO lawful-basis guidance](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/a-guide-to-lawful-basis/):
  UK-specific purpose/context guidance, not a universal EU/US rule.
- [FTC business guidance](https://www.ftc.gov/business-guidance): choose the actual
  applicable topic/source before asserting a consumer-law rule.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall