This skill drafts legal pages from an inventory of the code: what is collected and from whom, where it is stored and for how long, which providers it reaches, and what a visit stores in the browser. A unit test fails when the code reaches a provider the pages do not name.
The method keeps legal text true to the product. It is not legal advice: the owner supplies the legal identity, contact details, provider agreements and retention periods, and approves the full text before any stranger sees it.
What You Get
- Ten binding rules, from matching every sentence to code through to public pages that read no session
- An inventory method that draws on the schema, CSP origins, tables, browser storage and jobs
- A unit test that pins the policy’s provider list to what the code reaches
- A consent and cookie disclosure procedure for non-essential tags
- A list of seven facts and approvals only the owner can give
Common Use Cases
- Writing a privacy policy and terms for a new SaaS before its first sign-up
- Adding analytics and updating the policy in the same change
- Turning on sign-up consent in the identity provider
- Checking that pages promise no deletion that no job performs
What Makes It Unique
Pages are derived from the code and held to it by a test, not copied from a template. It refuses promises the code cannot keep: no retention period without a job that enforces it, no analytics tool named before its tag exists, and no unbuilt capability sold until it runs.
Under The Hood
The skill is instructions with a short receipts file and no scripts. Following it, the agent reads the product’s code, schema, content security policy and browser storage, may run a browser test that reads cookies and storage after each public page, and writes the legal pages, footer links and a unit test into the repository. It reaches nothing outside the repository. The owner supplies identity, contact and provider facts by hand.