Supabase Rls Policy Generator
CheckedGenerates Row Level Security (RLS) policies for Supabase databases based on provided table schemas and access requirements.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add hopeoverture/worldbuilding-app-skills --skill supabase-rls-policy-generator -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
hopeoverture
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned hopeoverture/worldbuilding-app-skills at 1263b3fb00.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1263b3fb00
- Scanned
- 10 files, 2,188 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill generates Row Level Security (RLS) policies for Supabase databases. It allows you to define fine-grained access control rules based on user roles and data attributes, ensuring that users can only access the data they are authorized to see. The generated policies are formatted as SQL code ready to be applied directly within your Supabase project.
When to use it
- Implementing Role-Based Access Control: You need to restrict access to specific rows in a table based on user roles or attributes (e.g., only allow users from the "admin" role to delete records).
- Data Privacy Compliance: You're building an application that requires strict data privacy controls and want to automate the generation of RLS policies.
- Dynamic Access Control: You need to create access rules based on complex conditions, such as user attributes or relationships between tables.
Key capabilities
- Generates SQL code for Supabase RLS policies.
- Supports defining rules based on user roles and data attributes.
- Automates the creation of fine-grained access control logic.
Example prompts
- "Generate an RLS policy for the 'posts' table that allows users with the role 'editor' to update only their own posts."
- "Create a policy for the 'orders' table where customers can only view orders associated with their user ID."
- “Write a Supabase RLS policy allowing admins to delete any row in the ‘products’ table.”
Tips & gotchas
- Ensure you have a basic understanding of Row Level Security and its implications within your Supabase database. Incorrectly configured policies can lead to unintended data access issues.