agentsclimarketplace

Terms of service

Skill bromso/metapowers/plugins/legal/skills/terms-of-service

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill terms-of-service

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft or update Terms of Service for digital products

SKILL.md

3.6 KB, 779 tokens by cl100k_base, as published. Nobody here has run it

Terms of Service

Draft or update Terms of Service for "$ARGUMENTS". Generate a comprehensive, jurisdiction-aware ToS document tailored to the product type and user base.

Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.

Prerequisites

Check that .metapowers/legal/$ARGUMENTS/00-assess.md exists. If it does not exist, stop and tell the user:

"Run an Assess skill first (e.g. /legal:risk-assessment $ARGUMENTS) to generate the prerequisite assessment artifact."

If the user passes --skip-checks, bypass this check and log the skip to .metapowers/legal/$ARGUMENTS/skip-log.md with a timestamp and the reason "Prerequisite check skipped for terms-of-service".

Process

  1. Read inputs:

    • Read .metapowers/legal/$ARGUMENTS/00-assess.md for risk and jurisdiction context
    • Read plugins/legal/shared/contract-template.md for standard contract provisions

  2. Identify product context:

    • Product type (web app, mobile app, marketplace, API, SaaS platform, etc.)
    • Target audience (consumers, businesses, or both)
    • Primary jurisdiction and any additional jurisdictions
    • Key features that require specific terms (payments, user content, subscriptions, etc.)

  3. Draft the following sections:

    • Acceptance Mechanism — how users accept the terms (clickwrap, browsewrap, sign-in wrap) with enforceability considerations
    • User Eligibility — age requirements (COPPA/GDPR-K considerations), geographic restrictions, entity requirements
    • Account Terms — registration requirements, account security obligations, account sharing restrictions
    • User Rights and Restrictions — license grant to use the service, scope and limitations
    • Prohibited Uses — specific prohibited activities (illegal use, abuse, reverse engineering, scraping, etc.)
    • Intellectual Property Ownership — company IP rights, trademarks, copyright notices
    • User-Generated Content — if applicable: license grant from users, content moderation rights, DMCA/takedown procedures, content responsibility
    • Disclaimers of Warranties — "as is" / "as available" disclaimers, no warranty of uninterrupted service
    • Limitation of Liability — liability cap, exclusion of consequential damages, jurisdictional carve-outs where required
    • Indemnification — user indemnification obligations, process requirements
    • Termination — termination rights (by user, by company, automatic), effect of termination, data retention post-termination
    • Governing Law and Dispute Resolution — choice of law, forum selection or arbitration clause, class action waiver (where enforceable)
    • Modification Procedure — how changes are communicated, notice period, deemed acceptance mechanism

  4. Tailor to jurisdiction requirements:

    • EU: consumer withdrawal rights, unfair terms directive compliance, GDPR cross-references
    • California: CCPA cross-references, additional consumer protections
    • Other jurisdictions identified in the assessment

  5. Write the artifact to .metapowers/legal/$ARGUMENTS/01-draft.md with frontmatter:

    ---
description: Terms of Service draft for $ARGUMENTS
---

Output

The Terms of Service draft written to .metapowers/legal/$ARGUMENTS/01-draft.md. Present a summary to the user highlighting:

  • Product type and primary jurisdiction identified
  • Key sections included and any sections omitted with rationale
  • Jurisdiction-specific provisions added
  • Areas flagged for attorney review

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.