privacy-policy
by phurynThe privacy-policy skill helps draft a first-pass privacy policy for a product or service, with clear data-collection details, jurisdiction scope, and legal review flags. Use it when launching a site, app, or SaaS, updating documentation, or preparing a privacy-policy for Legal review.
This skill scores 76/100, which means it is a solid but not top-tier listing for directory users: it appears genuinely usable for drafting privacy policies, with enough structure and guidance to justify installation, but users should still expect some manual judgment and legal review. The repository evidence shows a real workflow rather than a placeholder, so it offers more install value than a generic prompt, though it is narrower and less operationally complete than a highly polished skill.
- Clear trigger and use case: the frontmatter says to use it when creating or updating a privacy policy or compliance documentation.
- Strong workflow depth: the skill body is substantial, with multiple headings and workflow/constraint signals, indicating more than a stub.
- Good trust signal: it includes an explicit legal disclaimer and asks for qualified attorney review, which is appropriate for this domain.
- No install command, supporting scripts, or reference files were found, so users only get the markdown skill body rather than a fuller operational package.
- The excerpt shows a long input schema but limited evidence of concrete examples or executable assets, so adoption may still require interpretation for edge cases.
Overview of privacy-policy skill
The privacy-policy skill helps you draft a usable first-pass privacy policy for a product or service, with the right legal placeholders, data-collection detail, and review flags. It is best for founders, product teams, legal ops, and agents that need a policy draft before counsel edits it.
What this skill is for
Use this skill when you need a policy that explains what data you collect, why you collect it, where it is processed, and which clauses need attorney review. It is more useful than a generic prompt because it pushes the draft toward publishable structure instead of a vague compliance summary.
Best-fit users and jobs
This privacy-policy skill is a strong fit if you are:
- launching a new site, app, or SaaS product
- updating an old policy after changing analytics, billing, ads, or support tooling
- preparing a compliance draft for Legal or an external reviewer
- creating a baseline document for multiple jurisdictions
What makes it different
The repo is focused on practical policy drafting, not broad legal research. Its real value is in turning product facts into a policy outline that reflects data types, jurisdictional scope, and review boundaries. The main limitation is also its strength: it should support drafting, not replace legal judgment.
How to Use privacy-policy skill
Install privacy-policy skill
Install the skill with:
npx skills add phuryn/pm-skills --skill privacy-policy
If you are using this in an agent workflow, install first, then provide the product facts in a structured prompt. The privacy-policy install step matters because the skill expects named inputs rather than a free-form legal request.
Give the skill the right inputs
The best outputs come from clear product context. At minimum, provide:
- product or service name
- company legal name and address
- privacy contact email
- what personal data is collected
- how data is used
- whether children, payments, ads, or location data are involved
- target jurisdictions or countries
A weak prompt says: “Write our privacy policy.”
A stronger one says: “Draft a privacy-policy for a B2B SaaS that collects account details, usage analytics, support tickets, and billing data; we sell only in the US and EU; flag any GDPR-sensitive clauses for Legal.”
Suggested workflow for better output
Start with a narrow brief, let the skill draft the core policy, then revise for product specifics. Review the first draft for:
- missing data categories
- mismatched jurisdiction language
- unclear retention or sharing terms
- claims that need legal confirmation
For a privacy-policy usage workflow, feed the skill your actual data map rather than marketing copy. The draft gets much stronger when you state what systems collect data, not just what the app does.
Read these files first
If you are evaluating the repo before install, start with:
SKILL.mdfor the main drafting rules- the frontmatter description for quick fit confirmation
This repository is lightweight, so there are no extra rule files or helper directories to inspect. That makes the privacy-policy guide easy to adopt, but it also means the quality of your inputs matters more.
privacy-policy skill FAQ
Is privacy-policy skill legal advice?
No. The skill is meant to draft and organize policy language for review, not to provide legal advice. Treat the output as a working draft for Legal, especially if you process sensitive data or serve multiple regions.
When should I use privacy-policy instead of a generic prompt?
Use the privacy-policy skill when you want a repeatable drafting workflow with clearer coverage of data types, jurisdiction, and review points. A generic prompt may produce text, but it usually misses operational details that matter during review.
Is privacy-policy beginner-friendly?
Yes, if you can describe your product clearly. You do not need privacy expertise to use it well, but you do need basic facts about collection, sharing, and contact channels. The skill is not a substitute for knowing your own data flows.
Does this work for the privacy-policy for Legal review?
Yes. In fact, that is one of its best use cases. The draft is most helpful when Legal receives a structured starting point with obvious review markers instead of a blank-page request.
How to Improve privacy-policy skill
Provide complete product facts
The biggest quality jump comes from better inputs. Include specific data categories, third-party processors, region coverage, and any special cases like cookies, biometrics, minors, or payments. The privacy-policy skill can only draft accurately when your brief reflects reality.
Ask for review flags, not final certainty
Do not ask the model to “make it compliant” and stop there. Ask it to draft the policy and clearly mark clauses needing legal review. That keeps the output useful while avoiding false confidence.
Iterate on the parts that change risk
After the first draft, focus edits on the sections most likely to create exposure:
- lawful basis or consent language
- cross-border transfer language
- retention periods
- sharing with vendors or affiliates
- user rights and contact instructions
Use the output as a structured base
The privacy-policy skill works best when you treat the first draft as a legal-content scaffold. Feed back your reviewer’s comments, tighten any ambiguous claims, and rerun with updated product facts when your data practices change.