privacy-review
Skill0 starsChanged 26 days agoMITView on GitHub
Use when reviewing a codebase, feature, or data flow for privacy issues — unnecessary data collection, missing consent, third-party trackers, or logs that shouldn't exist.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- Smaui94/ClaudeSkillCollectiontheir own version, first seen Nov 8, 2026
- kerimovxx1990-dot/business-ai-kittheir own version, first seen Oct 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- kerimovxx1990-dot/business-ai-kit★ 0same name
- lengrufeng2008/dsh-skill-library★ 0same name
- Smaui94/ClaudeSkillCollection★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- offline-first-workflowSkill
- safe-browser-agentSkill
- secrets-handlingSkill
- security-auditSkill
- session-startSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Run this as a short checklist — keep it fast, not exhaustive prose.
- Distinctive: line 18
Logging: check whether logs capture anything sensitive — emails, IPs tied to identity, auth tokens, full request/response bodies on …
- Distinctive: line 19
Consent: if data collection falls into a category that typically needs consent (analytics, marketing, location, biometric, third-party …
- Distinctive: line 21
Retention: check whether there's any defined deletion/retention policy for collected data, or whether it's kept indefinitely by default.
- Distinctive: line 27
Agent should: Check what fields are collected and whether all are necessary, whether the analytics call sends more than needed, whether a …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Privacy Review
When to Use
- The user asks for a privacy review before shipping a feature
- Reviewing code that collects, stores, logs, or transmits user data
- Auditing third-party SDKs/scripts added to a project
Instructions
Run this as a short checklist — keep it fast, not exhaustive prose.
- Data minimization: for each piece of user data collected, confirm it is actually used for a stated purpose. Flag anything collected "just in case."
- Logging: check whether logs capture anything sensitive — emails, IPs tied to identity, auth tokens, full request/response bodies on user-data endpoints. Logs are a common accidental leak point.
- Consent: if data collection falls into a category that typically needs consent (analytics, marketing, location, biometric, third-party sharing), confirm a consent step exists before collection, not after.
- Third parties: list every third-party SDK/script/pixel present and what data each can access. Flag any with broad access (e.g., a full-page tracking script) relative to its stated purpose.
- Retention: check whether there's any defined deletion/retention policy for collected data, or whether it's kept indefinitely by default.
- Sharing boundary: confirm user data isn't sent to a third-party endpoint as a side effect of an unrelated feature (e.g., an analytics call that accidentally includes a full user object).
- Output findings as a short checklist with ✅ / ⚠️ / ❌ per item — don't write paragraphs per point.
Examples
User: "Can you do a quick privacy pass on our signup flow before we launch?" Agent should: Check what fields are collected and whether all are necessary, whether the analytics call sends more than needed, whether a privacy policy/consent checkbox exists, and return a short ✅/⚠️/❌ checklist — not a long essay.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.