Generate privacy policy and terms of service page drafts based on real business and data processing facts.
Triggers
Activate when
-
The user asks to use this Skill for its documented outcome.
-
"Generate privacy policy and terms of service page drafts based on real business and data processing facts."
-
“Draft website privacy and terms pages.”
Do not activate when
- Only querying this Skill's description, or requesting tasks unrelated to the above results; do not perform actual business operations.
- When the user only wants a preview or review, do not enter the modify, submit, or publish branches.
Execution boundary
A natural language request is sufficient to trigger; no legacy slash path, parameter interpolation, or specified assistant is needed. Clearly parse the project, target files, options, and output location in the current request; use the file, search, CLI, and browser capabilities actually provided by the current host. Project dependency versions and external APIs are verified at execution time; do not assume the examples are the current configuration. Package scripts are resolved from the Skill root, business files are resolved from the target project root. Read the current state first, protect existing uncommitted content and the staging area of other tasks. Analysis and preview requests remain read-only; modifications, commits, pushes, deployments, and releases are each executed according to the explicit scope of the current request. Do not bypass protections, automatically send messages, forcibly terminate user processes, or seize the foreground. On failure, retain the diagnosable original error.
Workflow
-
Read the website business, data collection, purposes, storage, third-party processors, payments, refunds, contacting entity, and applicable regions. When substantive facts are missing, ask focused questions; do not fabricate company addresses, retention periods, or compliance commitments.
-
Check the currently applicable official legal and platform materials, and organize the privacy policy and terms of service using actual facts; clearly state that the text is a draft pending review by responsible personnel, and do not claim legal compliance certification.
-
Reuse the website layout, language, dates, and linking conventions to create the user-specified pages and routes; keep existing legal text faithful to its source, with changes clearly reviewable.
-
Modify the Footer only when the requested scope includes navigation integration; do not automatically publish pages or agree to any agreement.
-
Check rendering, links, contact information, dates, and factual consistency, list gaps requiring confirmation by the responsible party, and keep the draft status.
Composition
Before execution, read capability composition, and hand off to adjacent capabilities according to the explicit artifact.
Runtime context (shared)
Before running, read this package's skill.yaml and Profile contract. Priority is the current request,
project context, this Skill's records, shared preferences, brand/user Profile, and safe defaults.
Read only declared fields; hosts without a dedicated runtime may use scripts/profile_store.py to read the shared Profile.
For missing configuration, ask only one question that affects the result. Values the user explicitly requests to save long-term are atomically written via that script,
and report the actual path; do not save inferences, credentials, or materials from other tasks.
For authorial text, execute authorship and source contract, and do not fabricate the author's experience, facts, or sources.