row-level-security
It applies database policies to restrict user access to specific rows to ensure data isolation in multi-tenant applications.
Install
mkdir -p .claude/skills/row-level-security && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4277" && unzip -o skill.zip -d .claude/skills/row-level-security && rm skill.zipInstalls to .claude/skills/row-level-security
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement PostgreSQL Row Level Security (RLS) for multi-tenant SaaS applications. Use when building apps where users should only see their own data, or when implementing organization-based data isolation.Key capabilities
- →Enable RLS on database tables
- →Create user-based access policies
- →Implement organization-based data isolation
- →Define role-based access control
How it works
It applies PostgreSQL policies to tables that restrict row access based on user or organization IDs, ensuring data isolation at the database level.
Inputs & outputs
When to use row-level-security
- →Implement multi-tenant data isolation
- →Configure PostgreSQL RLS policies
- →Restrict user access to their own records
About row-level-security
Configures database-level policies to restrict row access based on user context. It is designed for multi-tenant applications requiring strict data isolation.
Implement PostgreSQL Row Level Security (RLS) for multi-tenant SaaS applications. Use when building apps where users should only see their own data, or when implementing organization-based data isolation.
When not to use it
- →Publicly accessible data
- →Simple applications without user authentication
Prerequisites
Limitations
- →Requires indexing RLS columns for performance
- →Complex subqueries can impact query speed
How it compares
It enforces security at the database layer, making it impossible to bypass via application-level bugs, unlike manual filtering in code.
Compared to similar skills
row-level-security side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| row-level-security (this skill) | 1 | 6mo | Review | Advanced |
| supabase-rls-policy-generator | 11 | 9mo | No flags | Advanced |
| sqlmap-database-penetration-testing | 4 | 6mo | Review | Advanced |
| data-safety-auditor | 3 | 7mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dadbodgeoff
View all by dadbodgeoff →You might also like
supabase-rls-policy-generator
hopeoverture
This skill should be used when the user requests to generate, create, or add Row-Level Security (RLS) policies for Supabase databases in multi-tenant or role-based applications. It generates comprehensive RLS policies using auth.uid(), auth.jwt() claims, and role-based access patterns. Trigger terms include RLS, row level security, supabase security, generate policies, auth policies, multi-tenant security, role-based access, database security policies, supabase permissions, tenant isolation.
sqlmap-database-penetration-testing
davila7
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
data-safety-auditor
ananddtyagi
Comprehensive data safety auditor for Vue 3 + Pinia + IndexedDB + PouchDB applications. Detects data loss risks, sync issues, race conditions, and browser-specific vulnerabilities with actionable remediation guidance.
supabase-data-handling
jeremylongshore
Implement Supabase PII handling, data retention, and GDPR/CCPA compliance patterns. Use when handling sensitive data, implementing data redaction, configuring retention policies, or ensuring compliance with privacy regulations for Supabase integrations. Trigger with phrases like "supabase data", "supabase PII", "supabase GDPR", "supabase data retention", "supabase privacy", "supabase CCPA".
branch-isolation
Peadarpol
Expert review of multi-tenant and branch isolation safety, ensuring no query data leaks or cross-tenant access.
supabase-postgres-best-practices
davila7
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.