Agent skill

Supabase Advanced Troubleshooting

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop…

MITAuto-check passedDevelopment

Install Supabase Advanced Troubleshooting

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-advanced-troubleshooting -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace supabase-advanced-troubleshooting --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/supabase-advanced-troubleshooting .claude/skills/supabase-advanced-troubleshooting && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
supabase-advanced-troubleshooting
GitHub stars
2.8k
Token cost
~2.8k tokens
SKILL.md length
781 words
Files
9 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop…

  • Works in 3 steps: pg_stat_statements and slow query analysis → lock debugging and connection leak… → RLS conflicts, Edge Function cold…
  • Standard troubleshooting fails
  • SKILL.md covers Overview, Prerequisites, Authentication and Instructions, plus 5 more sections
  • Calls supabase; reaches supabase.com; needs SUPABASE_SERVICE_ROLE_KEY

What it does

Supabase Advanced Troubleshooting is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop analysis. Use when standard troubleshooting fails, when investigating performance regressions, when debugging race conditions, or when building evidence for a Supabase support escalation. Trigger with "supabase deep debug", "supabase slow query", "supabase lock contention", "supabase connection leak", "supabase RLS…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/errors.md`, `references/evidence-collection-framework.md` and `references/examples.md`). Compatibility notes: Designed for Claude Code

It sits in Development, covering Query optimization, Debugging and Async programming. It works with Supabase, PostgreSQL and SQL. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Standard troubleshooting fails
  • Investigating performance regressions
  • Debugging race conditions
  • Building evidence for a Supabase support escalation

Example prompts

  • “supabase deep debug”
  • “supabase slow query”
  • “supabase lock contention”
  • “/supabase-advanced-troubleshooting”

Requirements

  • Node.js
  • A credential in SUPABASE_SERVICE_ROLE_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Grep, Bash(npx supabase:*), Bash(supabase:*), Bash(curl:*), Bash(psql:*)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. pg_stat_statements and slow query analysis
  2. lock debugging and connection leak detection
  3. RLS conflicts, Edge Function cold starts, and Realtime drops

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Bash(npx supabase:*)
    • Bash(supabase:*)
    • Bash(curl:*)
    • Bash(psql:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • supabase

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • supabase.com

    Also links to:

    • postgresql.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SUPABASE_SERVICE_ROLE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Supabase Advanced Troubleshooting loads about 2.8k tokens when it runs, and up to ~9.1k if it reads all its reference files. Until then it costs about 146 tokens; SKILL.md has 781 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~146
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 781 words, ~2,783 tokens.

Download SKILL.mdSave it as .claude/skills/supabase-advanced-troubleshooting/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
supabase-advanced-troubleshooting
description
Deep Supabase diagnostics: pg_stat_statements for slow queries, lock debugging with pg_locks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop analysis. Use when standard troubleshooting fails, when investigating performance regressions, when debugging race conditions, or when building evidence for a Supabase support escalation. Trigger with "supabase deep debug", "supabase slow query", "supabase lock contention", "supabase connection leak", "supabase RLS conflict", "supabase cold start".
allowed-tools
Read, Grep, Bash(npx supabase:*), Bash(supabase:*), Bash(curl:*), Bash(psql:*)
compatibility
Designed for Claude Code
version
1.54.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, supabase, debugging, advanced, performance, troubleshooting

Supabase Advanced Troubleshooting

Overview

When basic debugging does not reveal the root cause, you need deep PostgreSQL diagnostics: pg_stat_statements to find the slowest queries by cumulative execution time, pg_locks to detect lock contention and deadlocks, pg_stat_activity to find connection leaks, RLS policy conflict analysis to diagnose silent data filtering, Edge Function cold start profiling, and Realtime channel drop investigation. This skill covers every advanced diagnostic technique with real SQL queries and createClient from @supabase/supabase-js.

When to use: Slow query investigation, lock contention causing timeouts, connection pool exhaustion from leaks, RLS policies that silently filter or conflict, Edge Functions with unpredictable latency, or Realtime subscriptions that disconnect intermittently.

Prerequisites

  • Supabase project with pg_stat_statements extension enabled
  • Direct database access via SQL Editor or psql
  • @supabase/supabase-js v2+ installed in your project
  • Supabase CLI for Edge Function logs
  • Familiarity with PostgreSQL system catalogs

Authentication

Every technique here runs against your own project's Postgres, so authenticate with project-scoped credentials, never a shared key:

  • psql / SQL Editor — connect with the project's direct connection string or pooled Supavisor URI from Dashboard → Settings → Database. Keep the database password in an env var (PGPASSWORD / .pgpass), never inline in a command.
  • SDK (createClient) — pass the service-role key (SUPABASE_SERVICE_ROLE_KEY) for the diagnostic RPCs below, since they read pg_stat_activity and system catalogs that the anon key cannot. Load it from the environment; never commit it.
  • supabase CLI — run supabase login once (stores a personal access token), then supabase link --project-ref <ref> for Edge Function logs.

Instructions

Work the three diagnostic tracks in the order the symptom points to. Each track's full query set and SDK helper lives in a reference file — SKILL.md carries the skeleton so you can start immediately, then drill in for the complete toolkit.

Step 1: pg_stat_statements and slow query analysis

Enable pg_stat_statements, then rank queries by total execution time, call frequency, and cache-hit ratio to find the real cost centers. Follow up with EXPLAIN (ANALYZE, BUFFERS) on the worst offenders and add targeted indexes with CREATE INDEX CONCURRENTLY. The starter query:

sql
CREATE EXTENSION IF NOT EXISTS pg_stat_statements;

SELECT queryid, calls,
  round(total_exec_time::numeric, 2) AS total_ms,
  round(mean_exec_time::numeric, 2)  AS avg_ms,
  left(query, 150) AS query_preview
FROM pg_stat_statements
ORDER BY total_exec_time DESC
LIMIT 10;

The full toolkit — frequency and cache-hit-ratio rankings, the EXPLAIN ANALYZE reading guide, and a timedQuery SDK wrapper that flags any call over 500 ms — is in slow query analysis.

Step 2: lock debugging and connection leak detection

Find blocked/blocking query pairs via pg_locks joined to pg_stat_activity, then hunt connection leaks — especially idle in transaction backends, which hold locks and exhaust the pool. The starter query surfaces who is blocked and who holds the lock:

sql
SELECT blocked.pid AS blocked_pid, blocking.pid AS blocking_pid,
  bl.mode AS lock_mode, left(blocked.query, 80) AS blocked_query
FROM pg_stat_activity blocked
JOIN pg_locks bl ON bl.pid = blocked.pid AND NOT bl.granted
JOIN pg_locks kl ON kl.relation = bl.relation AND kl.granted AND kl.pid != bl.pid
JOIN pg_stat_activity blocking ON blocking.pid = kl.pid
WHERE blocked.state = 'active';

The full toolkit — deadlock detection, idle/idle-in-transaction leak queries with pg_terminate_backend cleanup, and a get_connection_health RPC with utilization alerts — is in lock and connection diagnostics.

Step 3: RLS conflicts, Edge Function cold starts, and Realtime drops

Diagnose silent RLS data filtering, profile Edge Function cold-vs-warm latency, and trace Realtime channel drops. The full walkthrough — RLS policy conflict analysis (SQL and SDK), cold start profiling, channel-state monitoring, and publication configuration — is in RLS, Edge Functions, and Realtime.

Show full SKILL.md (299 more words)Show less

Output

This skill produces the following diagnostic artifacts:

  • Slow query identification — pg_stat_statements queries ranking by total time, frequency, and cache hit ratio
  • EXPLAIN ANALYZE proficiency — reading execution plans and creating targeted indexes
  • Lock contention diagnosis — blocked/blocking query pairs with lock modes
  • Connection leak detection — idle and idle-in-transaction connections with kill commands
  • Connection pool monitoring — SDK-based health check RPC with utilization alerts
  • RLS conflict analysis — policy listing with permissive/restrictive classification and multi-level comparison
  • Edge Function profiling — cold start vs warm invocation measurement
  • Realtime debugging — channel state monitoring with system event logging

Error Handling

ErrorCauseSolution
pg_stat_statements not availableExtension not enabledRun CREATE EXTENSION pg_stat_statements;
Seq Scan on large tableMissing index on filter columnCreate index with CREATE INDEX CONCURRENTLY
deadlock detectedCircular lock dependencyEnsure consistent lock ordering across transactions
All connections in idle in transactionApplication not closing transactionsAdd connection timeout; review ORM connection pool settings
RLS returns empty for authenticated userJWT claims don't match policyCheck auth.jwt() output; verify app_metadata is set
Edge Function > 2s cold startLarge dependency bundleLazy-import heavy modules; reduce function size
Realtime TIMED_OUTNetwork/firewall blocking WebSocketCheck port 443 (HTTPS/WSS) is open outbound; verify no proxy strips the Upgrade header
CHANNEL_ERROR on subscribeTable not in Realtime publicationRun ALTER PUBLICATION supabase_realtime ADD TABLE ...

Examples

Example 1 — Quick performance audit:

sql
-- Run this query to get a snapshot of database health
SELECT
  'Connections' AS metric,
  count(*)::text AS value
FROM pg_stat_activity WHERE datname = current_database()
UNION ALL
SELECT 'Cache hit ratio',
  round(100.0 * sum(heap_blks_hit) / nullif(sum(heap_blks_hit + heap_blks_read), 0), 2)::text || '%'
FROM pg_statio_user_tables
UNION ALL
SELECT 'Table bloat (dead tuples)',
  sum(n_dead_tup)::text
FROM pg_stat_user_tables
UNION ALL
SELECT 'Longest running query',
  coalesce(max(age(now(), query_start))::text, 'none')
FROM pg_stat_activity WHERE state = 'active' AND query NOT LIKE '%pg_stat%';

Example 2 — Build a diagnostic bundle for support:

typescript
import { createClient } from '@supabase/supabase-js';

const supabase = createClient(url, serviceRoleKey, {
  auth: { autoRefreshToken: false, persistSession: false },
});

async function buildDiagnosticBundle() {
  const bundle: Record<string, any> = {
    timestamp: new Date().toISOString(),
    projectRef: process.env.SUPABASE_PROJECT_REF,
  };

  // Connection stats
  const { data: connHealth } = await supabase.rpc('get_connection_health');
  bundle.connections = connHealth;

  // Table sizes
  const { data: tableSizes } = await supabase.rpc('get_table_sizes');
  bundle.tableSizes = tableSizes;

  // Recent errors from application logs
  const { data: recentErrors } = await supabase
    .from('error_logs')
    .select('message, count, last_seen')
    .order('last_seen', { ascending: false })
    .limit(10);
  bundle.recentErrors = recentErrors;

  console.log(JSON.stringify(bundle, null, 2));
  // Submit with your support ticket at https://supabase.com/dashboard/support
}

Example 3 — Automated slow query alert:

typescript
import { createClient } from '@supabase/supabase-js';

const supabase = createClient(url, serviceRoleKey, {
  auth: { autoRefreshToken: false, persistSession: false },
});

async function checkSlowQueries(thresholdMs = 1000) {
  const { data: slowQueries } = await supabase.rpc('get_slow_queries', {
    threshold_ms: thresholdMs,
  });

  if (slowQueries && slowQueries.length > 0) {
    console.warn(`Found ${slowQueries.length} queries averaging > ${thresholdMs}ms`);
    for (const q of slowQueries) {
      console.warn(`  [${q.avg_ms}ms avg, ${q.calls} calls] ${q.query_preview}`);
    }
  }
}

// Database function:
// CREATE OR REPLACE FUNCTION get_slow_queries(threshold_ms numeric DEFAULT 1000)
// RETURNS TABLE(queryid bigint, avg_ms numeric, calls bigint, query_preview text) AS $$
//   SELECT queryid, round(mean_exec_time::numeric, 2), calls, left(query, 150)
//   FROM pg_stat_statements
//   WHERE mean_exec_time > threshold_ms AND calls > 10
//   ORDER BY mean_exec_time DESC LIMIT 10;
// $$ LANGUAGE sql SECURITY DEFINER;

Resources

Next Steps

  • For load testing and scaling patterns, see supabase-load-scale
  • For incident response procedures, see supabase-incident-runbook
  • For performance tuning and index optimization, see supabase-performance-tuning
  • For common error patterns and quick fixes, see supabase-common-errors

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/.curated/supabase-advanced-troubleshooting of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/evidence-collection-framework.md
  • references/examples.md
  • references/lock-connection-diagnostics.md
  • references/rls-edge-functions-realtime.md
  • references/slow-query-analysis.md
  • references/systematic-isolation.md
  • references/timing-analysis.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Supabase Advanced Troubleshooting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Supabase Advanced Troubleshooting compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Supabase Advanced Troubleshooting this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.8kAutomated safety check: PassMIT
Safe SQL Executionsupabase/supabase111k—~4.2kAutomated safety check: PassApache-2.0
PR Bot Reviewspgplex/pgconsole155—~2.1kAutomated safety check: PassApache-2.0
New Lintsupabase/splinter281—~2.9kAutomated safety check: NotesNone
Relational Query ProcessorFoundationDB/fdb-record-layer676—~1kAutomated safety check: PassApache-2.0
Srtd Devt1mmen/srtd105—~2.3kAutomated safety check: PassMIT

Similar skills

  • Safe SQL Execution

    supabase/supabase

    Official

    A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…

    111k GitHub stars~4.2k tokensUpdated yesterday
    DatabasesAuto-check passed
  • PR Bot Reviews

    pgplex/pgconsole

    Triage, verdict, and reply to automated PR review comments from GitHub Copilot and Greptile, then iterate until the bots have nothing left to say.

    155 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • New Lint

    supabase/splinter

    Official

    Create a new splinter lint — a SQL view that checks for a database anti-pattern.

    281 GitHub stars~2.9k tokensUpdated 12 days ago
    DevelopmentAuto-check: notes
  • Relational Query Processor

    FoundationDB/fdb-record-layer

    Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner.

    676 GitHub stars~1k tokensUpdated yesterday
    DatabasesAuto-check passed
  • Srtd Dev

    t1mmen/srtd

    Expert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd.

    105 GitHub stars~2.3k tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd.

    105 GitHub stars~807 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Supabase Advanced Troubleshooting

What does Supabase Advanced Troubleshooting do?

Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop…. Supabase Advanced Troubleshooting is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deep Supabase diagnostics: pgstatstatements for slow queries, lock debugging with pglocks, connection leak detection, RLS policy conflicts, Edge Function cold starts, and Realtime connection drop analysis.

When should I use Supabase Advanced Troubleshooting?

Supabase Advanced Troubleshooting fits situations like: standard troubleshooting fails; investigating performance regressions; debugging race conditions; building evidence for a Supabase support escalation.

How do I install Supabase Advanced Troubleshooting in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-advanced-troubleshooting -a claude-code`. Or copy the skill folder (skills/.curated/supabase-advanced-troubleshooting in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/supabase-advanced-troubleshooting in your project. Claude Code loads it when a task matches its description.

How do I install Supabase Advanced Troubleshooting in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-advanced-troubleshooting -a codex`. Or copy the skill folder (skills/.curated/supabase-advanced-troubleshooting in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/supabase-advanced-troubleshooting in your project. Codex loads it when a task matches its description.

Can I use Supabase Advanced Troubleshooting in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill supabase-advanced-troubleshooting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/supabase-advanced-troubleshooting, .gemini/skills/supabase-advanced-troubleshooting, .github/skills/supabase-advanced-troubleshooting and .opencode/skills/supabase-advanced-troubleshooting in your project.

What does Supabase Advanced Troubleshooting need to run?

Going by SKILL.md and its folder, Supabase Advanced Troubleshooting needs the command-line tools its instructions call (supabase) and credentials named SUPABASE_SERVICE_ROLE_KEY. Our summary lists: Node.js; A credential in SUPABASE_SERVICE_ROLE_KEY. Its frontmatter pre-approves these tools: Read, Grep, Bash(npx supabase:*), Bash(supabase:*), Bash(curl:*), Bash(psql:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Supabase Advanced Troubleshooting access the network?

SKILL.md names 2 domains. In commands or code: supabase.com; the agent is likely to contact it when it follows the instructions. As links in the text: postgresql.org. This is read from the text; nothing was executed.

Is Supabase Advanced Troubleshooting safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Supabase Advanced Troubleshooting use?

Supabase Advanced Troubleshooting is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Supabase Advanced Troubleshooting use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Supabase Advanced Troubleshooting?

Skills that share tags, products or a category with Supabase Advanced Troubleshooting: Safe SQL Execution (supabase/supabase, 111k stars), PR Bot Reviews (pgplex/pgconsole, 155 stars), New Lint (supabase/splinter, 281 stars) and Relational Query Processor (FoundationDB/fdb-record-layer, 676 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Supabase Advanced Troubleshooting?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.