db-env-check

Validates database environment variables, PostgreSQL client tools, and connectivity without exposing secrets.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill db-env-check-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-env-check
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/database/db-env-check
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill db-env-check-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before running database operations against Supabase or PostgreSQL, misconfigured environment variables, missing client tools, or broken connections cause confusing failures. This Skill checks the environment upfront while redacting credentials so secrets never leak into logs or output. ## Core Features & Use Cases - Environment Variable Validation: Confirms SUPABASE_DB_URL is set and reports presence without printing the secret value. - SSL and Pooler Checks: Verifies sslmode is configured and detects whether a connection pooler host is in use. - Client Tool and Connectivity Checks: Confirms psql and pg_dump are installed and runs a live SELECT version() query to prove the database is reachable. - Use Case: Before running a migration or backup script in CI, run this check to fail fast with a clear remediation message instead of a cryptic mid-pipeline connection error. ## Quick Start Ask the agent to validate my database environment and confirm the Supabase connection works without printing any secrets.

Frequently Asked Questions about db-env-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my Supabase database connection works before running migrations?▼

Run a pre-flight check that verifies SUPABASE_DB_URL is set, confirms psql is installed, and executes SELECT version() against the database. This catches connection failures before migration scripts run.

How to validate database environment variables without exposing secrets?▼

Test for the presence of variables like SUPABASE_DB_URL using shell checks that only echo confirmation messages, never the value itself. Pattern-match for sslmode or pooler substrings instead of printing the full connection string.

Does Supabase require sslmode in the connection string?▼

Supabase connections should include sslmode=require to encrypt traffic. The check warns when sslmode is missing from SUPABASE_DB_URL and recommends adding it, and also suggests using the pooler host for better connection management.

Why does my database connection fail in CI pipelines?▼

Common causes are missing SUPABASE_DB_URL, absent psql or pg_dump client tools, or network restrictions blocking the database host. A pre-flight check identifies which specific condition failed and provides remediation steps.

What should I do when a PostgreSQL connection check fails?▼

Verify the connection string and credentials, confirm network access to the database host, and retry with exponential backoff up to three attempts. The check exits with a non-zero status and a clear error message for each failure type.