Skip to content
TrustedSkillsbeta
Back to all skills

Postgres Rls

Checked
troykelly·vlatest·database

Enforce granular PostgreSQL Row Level Security policies based on user context using this powerful AI assistant.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add troykelly/claude-skills --skill postgres-rls -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

troykelly

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 troykelly/claude-skills at 38a2ecc528.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
38a2ecc528
Manifest
skills/postgres-rls/SKILL.md
Scanned
1 file, 365 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables Row Level Security (RLS) in PostgreSQL. RLS allows you to define policies that control which rows a user can access, based on their role or other criteria. It provides fine-grained data access control directly within the database itself, enhancing security and simplifying application logic.

When to use it

  • Multi-tenant applications: Restrict each tenant's access to only their own data records.
  • Role-based access control: Limit a user’s view of data based on their job function or permissions.
  • Sensitive data filtering: Ensure users can only see non-sensitive information, even if they have broader database privileges.
  • Data masking: Implement rules to mask certain columns for specific roles.

Key capabilities

  • Defines policies using SQL expressions.
  • Enforces row-level access control at the database level.
  • Supports dynamic policy evaluation based on user context.
  • Integrates with PostgreSQL's existing security framework.

Example prompts

  • "Create a RLS policy so that users in the 'sales' role can only see records where the region is 'North'."
  • "Show me the current RLS policies defined for the 'orders' table."
  • "Disable RLS on the 'products' table temporarily."

Tips & gotchas

  • Requires PostgreSQL 9.5 or higher.
  • Carefully consider policy complexity to avoid performance bottlenecks; optimize queries used in your RLS policies.