Token导航 LogoToken导航

Agent Skill · 研究检索

terms-of-service(服务条款)

terms-of-service 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

terms-of-service 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 42,619。

总安装 1,056周安装 44GitHub Stars 114下载 352核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:terms-of-service(服务条款)
来源仓库:https://github.com/shawnpang/startup-founder-skills
仓库路径:skills/terms-of-service
安装命令:
npx skills add https://github.com/shawnpang/startup-founder-skills --skill terms-of-service
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/shawnpang/startup-founder-skills --skill terms-of-service

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

terms-of-service 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。它支持结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

来源仓库内路径:skills/terms-of-service

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/shawnpang/startup-founder-skills --skill terms…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

terms-of-service 怎么安装?

在终端执行 npx skills add https://github.com/shawnpang/startup-founder-skills --skill terms-of-servic…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

terms-of-service 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

terms-of-service 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

terms-of-service 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

terms-of-service 用的人多吗?

公开数据是累计安装 1,056 次,近一周安装 44 次,下载 352 次,GitHub 114 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

terms-of-service 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
terms-of-service

服务条款 · 本页

1,056114需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Terms of Service

When to Use

Activate when a founder needs to create terms of service for a product launch, update existing terms to reflect new features or business model changes, or assess whether current terms adequately protect the company. Also activate when the user asks about acceptable use policies, liability limitations, or user agreement structures.

Context Required

  • From startup-context: product type, platform, business model, pricing structure, target customer (B2B vs B2C), geographic markets, company legal entity and jurisdiction.
  • From the user: what the product does, how users interact with it, whether users create or upload content, whether the product integrates with third-party services, payment/subscription structure, any past disputes or known risk areas, and whether the audience includes enterprise customers who will negotiate terms.

Workflow

  1. Scope assessment — Determine the product type (SaaS, marketplace, API, mobile app) and audience (consumers, SMBs, enterprise). This dictates the tone, enforceability approach, and which clauses are essential.
  2. Risk identification — Map the key liability scenarios for this specific product: data loss, service outages, user-generated content issues, integration failures, billing disputes.
  3. Draft terms — Write each section using the template below. Use plain language with legally precise phrasing. Avoid unnecessary jargon while maintaining enforceability.
  4. Enforceability review — Flag clauses that may be unenforceable in certain jurisdictions (e.g., blanket liability exclusions are limited in the EU, mandatory arbitration is restricted in some states and countries).
  5. Presentation guidance — Recommend how to present the terms (clickwrap vs browsewrap), versioning strategy, and how to notify users of changes.

Output Format

A terms of service document with the following sections.

Section Template

  1. Agreement to Terms — How acceptance works (clickwrap recommended), age requirements, authority to bind an organization.
  2. Description of Service — What the product does, what it does not guarantee, service levels if applicable.
  3. Account Registration & Security — Account creation requirements, user responsibilities for credentials, account sharing policy.
  4. Acceptable Use Policy — Prohibited activities (abuse, scraping, reverse engineering, illegal use, competitive benchmarking). Be specific to the product.
  5. User Content & Data — Who owns user-uploaded content, license grants the company needs to operate the service, what happens to data on termination.
  6. Data Ownership & Portability — Clarify that customer data belongs to the customer. Describe export capabilities and formats.
  7. Intellectual Property — Company retains ownership of the platform, trademarks, proprietary algorithms. User gets a limited license to use the service.
  8. Payment & Billing — Subscription terms, billing cycles, price change notice periods, refund policy, what happens on failed payments.
  9. Free Trials & Freemium — Terms specific to free tiers, conversion expectations, feature limitations, data retention after trial expiry.
  10. Service Availability & SLAs — Uptime commitments (or lack thereof), scheduled maintenance windows, force majeure.
  11. Limitation of Liability — Cap on damages (typically limited to fees paid in prior 12 months), exclusion of consequential/indirect damages.
  12. Indemnification — User indemnifies company for misuse, content violations, third-party claims arising from user's use.
  13. Termination — How either party can terminate, what happens to data post-termination (retention period, deletion timeline), survival clauses.
  14. Dispute Resolution — Governing law, jurisdiction, arbitration clause if applicable, class action waiver if applicable.
  15. Modifications to Terms — How changes are communicated, notice period (30 days recommended), continued use as acceptance.
  16. Miscellaneous — Severability, entire agreement, assignment, waiver, notices.

Frameworks & Best Practices

Plain Language Approach

  • Write so a non-lawyer customer can understand their obligations and rights.
  • Use "you" and "we" consistently. Define them once at the top.
  • Use short paragraphs and bullet points for lists of prohibited activities.
  • Bold or highlight the most impactful clauses (liability caps, auto-renewal, arbitration).
  • Provide a "key terms summary" sidebar or header for each section with a one-line plain English explanation.

SaaS-Specific Considerations

  • Data ownership is non-negotiable. Customer data must unambiguously belong to the customer. The company gets only the license needed to provide the service.
  • Aggregated/anonymized data. If you use customer data in aggregate for analytics, benchmarking, or model training, disclose this explicitly and ensure it is truly de-identified.
  • API terms. If you offer an API, specify rate limits, authentication requirements, and restrictions on redistribution of API output.
  • Integration liability. Clarify that the company is not responsible for third-party integrations or data passed to third-party services at the user's direction.
  • Sub-processors. List or link to sub-processors (hosting, payment, analytics). Enterprise customers expect this.

Enforceability Guardrails

  • Clickwrap over browsewrap. Require an affirmative action (checkbox, click) to accept terms. Browsewrap ("by using this site you agree") is weakly enforceable.
  • Conspicuous disclosure. Arbitration clauses, auto-renewal terms, and liability limitations must be prominently displayed to be enforceable in many jurisdictions.
  • Consumer protection limits. EU and UK consumer law restricts unfair terms. Blanket liability exclusions for negligence are generally unenforceable for consumers.
  • Auto-renewal laws. California (ARL), FTC guidelines, and EU consumer directives require clear disclosure of auto-renewal and easy cancellation.
  • Unilateral modification. Courts increasingly scrutinize "we can change these terms at any time" clauses. Provide reasonable notice (30 days) and allow termination if users disagree.

B2B vs B2C Differences

  • B2B: Expect negotiation on liability caps, SLAs, indemnification, and data processing terms. Have an enterprise-tier addendum ready.
  • B2C: Consumer protection laws are more protective. Arbitration may be restricted. Cooling-off periods may apply.
  • Hybrid (self-serve B2B): Start with standard terms but have a process for enterprise customers to request modifications via a Master Service Agreement.

Related Skills

  • privacy-policy — Must be drafted together. Terms should reference the privacy policy for data handling practices. Definitions (like "personal data") should be consistent.
  • contract-review — When enterprise customers redline your terms, use contract-review to assess their proposed changes.

Examples

Example 1: B2B SaaS product

User: "We're launching a B2B analytics platform with a freemium tier and paid plans starting at $49/month. We need terms of service."

Good output excerpt:

6. Data Ownership & Portability Your Data is yours. We claim no ownership over any data, content, or information you submit to the Service ("Customer Data"). You grant us a limited, non-exclusive license to use Customer Data solely to provide and improve the Service. You may export your Customer Data at any time via the dashboard export feature in CSV or JSON format. Upon termination of your account, we will retain your Customer Data for 30 days to allow retrieval, after which it will be permanently deleted from our active systems and removed from backups within 90 days. We may generate aggregated, anonymized statistics about platform usage ("Aggregated Data") that cannot identify you or any individual user. We own Aggregated Data and may use it for benchmarking, research, and product improvement.

Example 2: Marketplace with user-generated content

User: "Our platform lets freelancers sell digital templates. We need terms covering both buyers and sellers."

Good output excerpt:

5. User Content For Sellers: You retain ownership of all templates and digital assets you upload ("Seller Content"). By listing Seller Content on the platform, you grant us a non-exclusive, worldwide license to display, distribute, and promote your Seller Content in connection with operating the marketplace. This license ends 30 days after you remove the content, except for copies already purchased by Buyers. For Buyers: Your purchase grants you a license to use the template as specified in the Seller's license terms. You do not acquire ownership of the underlying intellectual property. Resale, redistribution, or sub-licensing of purchased templates is prohibited unless the Seller's license explicitly permits it. Our Responsibilities: We do not pre-screen Seller Content. We are a platform, not a publisher. However, we reserve the right to remove content that violates these Terms or applicable law.

Disclaimer: This skill generates draft terms of service for educational and planning purposes only. It does not constitute legal advice. Terms of service must be tailored to your specific product, business model, and applicable jurisdictions. Enforceability varies by jurisdiction and depends on how terms are presented to users. Always have a qualified attorney review your final terms of service before publication.

平台分布

Codex

35.99%
按下载量换算127

Claude

28.69%
按下载量换算101

Cursor

19.35%
按下载量换算68

Gemini CLI

8.93%
按下载量换算31

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills