production-database-query

Query Ballee's production and staging Supabase PostgreSQL databases with secure credentials.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill production-database-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-database-query
Source: https://github.com/JaveedIshaq/ai-workflow-orchestrator/tree/main/skills/ballee/production-database-query
Command: npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill production-database-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a secure and controlled way to query Ballee's production and staging databases, enabling safe debugging, data verification, and hotfix application without risking data integrity.

Core Features & Use Cases

  • Secure Access: Uses .env.local or 1Password for credentials, with automatic caching.
  • Environment Specificity: Clearly distinguishes between production and staging database connections.
  • Use Case: A user reports a bug that seems to be related to data on the production server. You can use this Skill to safely query the production database to verify the data and understand the issue without direct, risky access.

Quick Start

Safely connect to the production database and execute the query 'SELECT * FROM events LIMIT 5;'.

Frequently Asked Questions about production-database-query

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

FAQPage Schema
How do I safely query a production Supabase database for debugging?

Safely query a production Supabase database by utilizing secure credential management via environment variables or 1Password fallback, enabling controlled access for debugging and data verification without risking data integrity.

What is the best way to manage database credentials when running SQL queries on staging?

The best way to manage database credentials for SQL queries is by using `.env.local` files or 1Password fallback with automatic caching, securely providing connection details for both production and staging Supabase environments.

Can I access legacy Meteor MongoDB data for migration alongside Supabase PostgreSQL?

Yes, you can access Meteor MongoDB legacy data for migration and debugging purposes alongside Supabase PostgreSQL, allowing you to query and verify data across both database systems during the transition.

Does this database querying approach work for both staging and production environments?

Yes, this database querying approach clearly distinguishes between production and staging Supabase PostgreSQL environments, providing specific connection details and quick reference commands for direct SQL execution in each.

How do I execute direct SQL commands to verify production data issues?

You can execute direct SQL commands to verify production data issues by utilizing provided quick reference commands and secure connection details, allowing you to safely run queries like selecting limited rows to understand reported bugs.