Skip to content
TrustedSkillsbeta
Back to all skills

Multi Tenant Safety Checker

Checked
patricio0312rev·vlatest·cloud·MIT

This skill verifies if your multi-tenant application meets security best practices, ensuring data isolation and protecting all users.

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 patricio0312rev/skills --skill multi-tenant-safety-checker -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Commit
79ea6af485
Manifest
db-management/multi-tenant-safety-checker/SKILL.md
Scanned
1 file, 383 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, Multi Tenant Safety Checker, helps ensure your multi-tenant application maintains data isolation and prevents data leakage between tenants. It focuses on implementing Row Level Security (RLS) within a PostgreSQL database to enforce tenant-specific access controls. The skill also provides guidance for setting up an Application-Level Tenant Context using middleware to manage the app.tenant_id variable, which is crucial for RLS policies.

When to use it

  • When building a multi-tenant application where data isolation between tenants is critical.
  • During security audits to verify adherence to tenant safety best practices.
  • To implement and test Row Level Security (RLS) in PostgreSQL databases.
  • When needing to enforce that all database queries are filtered by tenant ID.
  • To ensure file uploads and background jobs operate within the correct tenant context.

Key capabilities

  • Row Level Security (RLS) Implementation: Sets up RLS on tables using PostgreSQL policies.
  • Application-Level Tenant Context: Provides middleware for managing app.tenant_id to control data access.
  • Tenant Isolation Checklist: Offers a comprehensive checklist covering database, application, and testing aspects of multi-tenancy security.
  • Automated Security Tests Guidance: Suggests tests to verify RLS bypass prevention and SQL injection vulnerabilities.

Example prompts

  • "Show me how to enable Row Level Security on the 'users' table."
  • "What is the purpose of the app.tenant_id variable?"
  • "Generate a policy for the 'orders' table using RLS to filter by tenant ID."

Tips & gotchas

  • Requires a PostgreSQL database and Prisma client setup.
  • The skill relies on setting a local variable (app.tenant_id) which must be managed consistently throughout your application.
  • Thorough testing, including cross-tenant query tests and RLS bypass attempts, is essential to ensure security effectiveness.