Generate Supabase Row Level Security policies from table_name, columns, and access_rules.
npx skills add https://github.com/Zibilispops/dark2 --skill rls-generator
Please help me install this Agent Skill. Skill: rls-generator Source: https://github.com/Zibilispops/dark2/tree/main/.agent/skills/rls-generator Command: npx skills add https://github.com/Zibilispops/dark2 --skill rls-generator
This Skill automates the creation of Row Level Security policies for new Supabase tables, reducing manual errors and ensuring policy coverage.
Provide the table_name, columns, and access_rules to generate the initial RLS policy for a new table.
High-intent search queries and answers about installing and using this skill.
To generate Row Level Security policies for new Supabase tables, provide the table_name, columns, and access_rules to produce a json object containing the sql_policy, explanation, and risk_notes for consistent access controls.
You need to provide the table_name, a list of columns, and the access_rules for the Supabase table. The Skill combines these inputs to validate consistency and generate the precise row-level security policy.
Yes, you can integrate RLS policy generation into development, staging, and production PR workflows. This ensures every new table ships with a compliant row-level security policy, reducing manual errors and misconfigurations.
The generated RLS policy includes an explanation and risk_notes alongside the sql_policy. These fields detail how the row-level access controls work and outline potential security implications for the Supabase table.
New Supabase tables often lack consistent row-level access controls due to manual policy creation errors. Automatically generating RLS policies from table_name, columns, and access_rules enforces consistent data access controls across environments.
semicolon-devteamCreate and validate Supabase database schemas, RLS policies, and migrations.
AdamFehseManage Supabase database schema, migrations, and Row Level Security policies.
aigars-stgQuery STP Supabase database with natural language and explore schemas.
HainrixzAudit database access control, PII exposure, encryption, and SQL injection risks.
