execute-sql-customer

Run read-only PostgreSQL queries via REST with explicit columns and LIMIT 50.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill execute-sql-customer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-sql-customer
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/geo-sus/skills/execute-sql-customer
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill execute-sql-customer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to run read-only SQL queries against a customer's PostgreSQL database via a REST endpoint, facilitating quick data investigations, debugging, and validation in production-like environments.

Core Features & Use Cases

  • Safe, read-only SQL execution against customer databases through REST to inspect data and verify fixes.
  • Automated formatting of results into a readable JSON-table representation, with clear handling for empty results and errors.
  • Use Case: A developer needs to verify orders for a specific customer by running constrained SQL against geovendas1 to confirm data integrity.

Quick Start

Run a read-only SQL query against the customer's PostgreSQL database using the REST endpoint and review the formatted results.

Frequently Asked Questions about execute-sql-customer

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

FAQPage Schema
How do I run read-only SQL queries against customer PostgreSQL databases?▼

Run read-only SQL queries against customer PostgreSQL databases via a REST endpoint to investigate data issues. The skill enforces PostgreSQL syntax, disallows SELECT *, and formats results into a readable JSON-table representation for quick data validation.

What is the safest way to debug production data in customer PostgreSQL databases?▼

Debug production data safely by running constrained, read-only SQL queries through a REST endpoint. This mechanism requires explicit column selection and applies a default LIMIT 50 to prevent heavy queries from impacting customer environments during data validation.

Can I use SELECT * when querying customer data through the REST SQL endpoint?▼

Querying customer data through the REST SQL endpoint does not allow SELECT *. You must use explicit column selection and adhere to PostgreSQL syntax to execute constrained queries, with a default LIMIT 50 applied to prevent heavy database loads.

How do I verify data integrity for specific customer orders in PostgreSQL?▼

Verify data integrity for specific customer orders by running read-only SQL queries against the PostgreSQL database via REST. Constrained queries with explicit columns and LIMIT 50 return formatted JSON-table results to quickly confirm data fixes and investigate issues.

Does the REST SQL querying skill handle empty results or database errors?▼

The REST SQL querying skill handles empty results and errors during read-only query execution. It automatically formats the output into a readable JSON-table representation, ensuring clear visibility of data validation outcomes or PostgreSQL syntax issues.