access-check
Skill0 starsChanged 38 days agoMITView on GitHub
Tests who can see what in an app: visitors, signed-in users and paying members. Use for 'who can see this', 'is my paywall safe', 'check permissions' or 'can people get in free'.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sabirmgd/terminal-first-goal-looptheir own version, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sabirmgd/terminal-first-goal-loop★ 2same 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.
- data-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
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 11
Read the app and list every page (and important actions, like "download", "watch", "edit").
- Distinctive: line 14
Ask (with tap-to-answer options) or infer from their brief, then show the intended rules:
- Distinctive: line 19
Use ✓, ✗ or "preview only".
- Distinctive: line 22
Run the app (or use the preview link) and open each page while logged out.
- Distinctive: line 23
Check the obvious ways around a paywall: opening a paid page's URL directly, direct links to files or videos, thumbnails or links that leak …
- Distinctive: line 24
If you can, test as a signed-in free user too.
≈ “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
Access check
You're checking that the right people see the right things. The person doesn't code, so report in a table they can read at a glance.
1. List every page and action
Read the app and list every page (and important actions, like "download", "watch", "edit"). Include sign-in and account pages.
2. Say who should see what
Ask (with tap-to-answer options) or infer from their brief, then show the intended rules:
| Page / action | Visitor (logged out) | Signed in, free | Paying member | Admin |
Use ✓, ✗ or "preview only".
3. Test it for real
- Run the app (or use the preview link) and open each page while logged out. Record what actually happens: shows the content, redirects to sign-in, or shows an error.
- Check the obvious ways around a paywall: opening a paid page's URL directly, direct links to files or videos, thumbnails or links that leak a paid item's ID, and API routes that return paid content without checking who's asking.
- If you can, test as a signed-in free user too.
- If you can't open pages yourself (for example in a normal chat rather than the Code tab), give them a short numbered list of exactly what to click and ask them to report back or send screenshots. Never mark a step passed without seeing the result.
4. Report
Show the table again with what actually happened next to what should happen, and highlight every mismatch in plain English: "A visitor can open /videos/12 directly and watch it without paying." For each problem, explain the fix in one line, and offer to make it on a branch. Don't change anything without a yes.
5. Sign-in sanity
Briefly confirm sign-in itself is handled by a login service (such as Clerk), not home-made password code, and that pages check sign-in on the server, not just by hiding buttons.
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.