data-check
Skill0 starsChanged 37 days agoMITView on GitHub
Read-only check that an app's database and personal data are safe. Use for 'is my data safe', 'check my database', 'GDPR', 'security check' or 'could users see each other's data'.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Zwin-ux/kittheir own version, first seen Oct 11, 2026
- kayspiegel/survey-insight-skillstheir own version, first seen Aug 16, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kayspiegel/survey-insight-skills★ 2same name
- Zwin-ux/kit★ 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 repository13 other files it gives its agents.
- access-checkSkill
- deploy-doctorSkill
- domain-helperSkill
- first-tenSkill
- idea-to-mvpSkill
- keys-checklistSkill
- make-it-yoursSkill
- payment-testSkill
- project-starterSkill
- review-loopSkill
- safe-changeSkill
- sketch-itSkill
- stack-checkSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 25
Search the code and the git history for anything that looks like a database URL or password.
≈ “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
Data check
You're checking someone's data is safe. They don't code, so explain everything plainly. This check is read-only: never change, delete or move data. Recommend fixes; make them only on a branch and only with a yes.
1. Map the data
Using the Neon connector (or whichever database is connected), list every table. For each, give:
| Table | What it holds | Personal data? | Rows (roughly) |
"Personal data" means anything that identifies a person: names, emails, phone numbers, addresses, payment details, IP addresses.
2. Who can read it?
- Find how the app talks to the database. In a typical setup only the server should, using a connection string kept in an environment variable. Confirm this is true.
- Flag anywhere the browser could reach the database directly, any public API route that returns other people's data, or any data API that's switched on without access rules.
- For each table, say plainly who can read it: "only the server", "the logged-in owner", or "anyone with the link" (which is bad for personal data).
3. Where's the connection string?
- Confirm it's only in environment variables (Vercel settings and
.env.local), and that.env*is in.gitignore. - Search the code and the git history for anything that looks like a database URL or password. If found: flag it clearly and recommend rotating the credential in the database dashboard. Never repeat the value.
4. Report
Give a short report:
- ✓ What's safe
- ⚠️ What to fix, most important first, each with a one-line plain-English reason
- A plain answer to: "Could a stranger see someone else's data?" yes or no, and why
Offer to make the fixes on a branch. Tell them that asking "check for security problems, then fix them" is a real job Claude can do; "make it secure" is too vague.
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.