Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Inspecting Database | Skills Pool

Skill File

Inspecting Database

Read-only inspection of the ImageLink database via the Supabase MCP (local):

mlondono-oc0 starsApr 9, 2026

Occupation
Categories: Debugging

Skill Content

Inspecting the Database — ImageLink

Purpose

Use this skill to understand the current state of the database with the Supabase MCP without modifying data or the schema.

This procedure is read-only and is used for:

debugging
extracting information
clarifying the current schema

Non-negotiable rules

Treat all MCP interactions as read-only.
Do not use MCP to modify the database.
Do not execute apply_migration from MCP.
If schema or data changes are required, use the project's CLI migrations:

supabase migration new migration_name
edit migration SQL
supabase migration up
if corruption occurs: supabase db reset

If the user asks to change the schema or data, redirect to migrations and the modifying-database skill.

Related Skills

Quick Install

Inspecting Database

npx skillvault add mlondono-oc/mlondono-oc-ai-workflows-projects-image-link-cursor-skills-inspecting-database-skill-md

Download Skill Open repository

Author: mlondono-oc
stars: 0
Updated: Apr 9, 2026
Occupation

On this page

01Inspecting the Database — ImageLink

MCP to be used for inspection

MCP Server: project-0-image-link-local-database

Use the enabled Supabase local database MCP. Before calling a tool, read its JSON schema under .cursor/.../mcps/<server>/tools/<tool>.json so arguments match exactly (e.g. list_tables requires schemas and verbose).

Recommended tools for reading:

list_tables: List tables by schema
list_migrations: Review the status of applied migrations
list_extensions: Inspect enabled extensions
get_logs: Diagnose problems by service (postgres, api, auth, etc.)
get_advisors: Review security/performance recommendations
execute_sql: Only for SELECT or other read queries

Forbidden for this skill

apply_migration: (prohibited by read-only policy)

Suggested workflow

Define the inspection question (schema, data, performance or error).
Start with metadata:

list_tables
list_migrations
list_extensions

If more detail is needed, use execute_sql with read queries (SELECT).
If the problem is operational, supplement with:

get_logs
get_advisors

Report findings and, if changes are needed, escalate to the CLI migrations workflow.

Restrictions for execute_sql

Allowed:

SELECT ...
Catalog queries (information_schema, pg_catalog)
EXPLAIN on read queries

Not allowed:

INSERT, UPDATE, DELETE
CREATE, ALTER, DROP, TRUNCATE
GRANT, REVOKE, COMMENT
Any SQL with side effects

Quick Checklist

Confirm that the objective is inspection/debugging
Use only MCP read tools
If using execute_sql, validate that it is read-only
Do not use apply_migration via MCP
If a database needs to be changed, move to CLI migrations

02

Purpose

03Non-negotiable rules

04MCP to be used for inspection

05Suggested workflow

06Restrictions for executesql

07Quick Checklist

Database Administrators

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Database Administrators