Supabase security basics: RLS, key separation, hardening
Secure a Supabase project — anon vs service_role keys, RLS policies, JWT verification, API hardening
- What
- Secure a Supabase project — anon vs service_role keys, RLS policies, JWT verification, API hardening
- Cost
- Free
- Needs
- a Supabase project (free tier available — usable for this); `@supabase/supabase-js` installed; SUPABASE_URL and SUPABASE_ANON_KEY available to the agent — the service_role key stays server-side only, never in chat
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Supabase security primer built around the most common mistake: confusing the anon and service_role keys. Covers the two-key model (anon is public, respects RLS; service_role bypasses everything and must never touch the client), Row Level Security policy patterns, JWT verification, and API surface hardening, framed as a production security checklist for auditing a Supabase project. By @jeremylongshore, listed here with credit to its creator. Honest caveats: requires a Supabase project (free tier available — usable for this) and `@supabase/supabase-js`; security guidance only — it tells the agent what to lock down, but you must run the checklist yourself; tables without RLS are publicly readable with just the anon key — this is the whole point of the skill. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Supabase security basics is a free Muse skill for securing a Supabase project. Built around the most common mistake, confusing the anon and service_role keys, it covers the two-key model, Row Level Security policy patterns, JWT verification and API hardening, framed as a production checklist for auditing a project, with a free tier usable for this.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit cfae287Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Supabase project (free tier available — usable for this); `@supabase/supabase-js` installed; SUPABASE_URL and SUPABASE_ANON_KEY available to the agent — the service_role key stays server-side only, never in chat Install "Supabase security basics: RLS, key separation, hardening" for me. Give my agent the Supabase security primer — the two-key model, RLS policy patterns, JWT verification and API hardening, framed as a production security checklist Repository: https://raw.githubusercontent.com/jeremylongshore/tons-of-skills-marketplace/cfae287053f6d06aa2c58b548f263476d520238a/plugins/saas-packs/supabase-pack/skills/supabase-security-basics/SKILL.md Pinned version: install the code at commit cfae287053f6d06aa2c58b548f263476d520238a exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the jeremylongshore-tons-of-skills-marketplace-supabase-security-basics skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "jeremylongshore-tons-of-skills-marketplace-supabase-security-basics". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. run the security checklist against my project, rotate any exposed service_role key). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- cfae287 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.