sql-reader

Query production PostgreSQL databases with read-only credentials.

Updated Aug 23, 2026

Search Tags:#postgresql #query #read-only #db

Ready to run

npx skills add https://github.com/cncorp/arsenal --skill sql-reader

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sql-reader
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/sql-reader
Command: npx skills add https://github.com/cncorp/arsenal --skill sql-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires psql.

What problem does it solve?

This Skill provides read-only access to the production PostgreSQL database to investigate data, debug issues, and analyze application state without risking modification.

Core Features & Use Cases

Safe queries: read-only access respecting data quirks.
Bootstrap commands: quickstart commands to bootstrap typical explorations.
Schema exploration: quick intros to understand model shapes.

Quick Start

Run connect.sh to start an interactive read-only session against the production database.

Frequently Asked Questions about sql-reader

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

FAQPage Schema

How do I query production PostgreSQL data safely without risking changes?▼

Read-only access to PostgreSQL ensures queries cannot modify production data. This Skill provides read-only credentials and bootstrap commands to investigate data issues, debug application state, and analyze user data while protecting against accidental writes.

What's the quickest way to start exploring production database tables and schema?▼

Run connect.sh to launch an interactive read-only session. The Skill includes bootstrap queries and commands to quickly inspect table structures, understand data models, and explore core tables without writing custom SQL from scratch.

Can I use read-only PostgreSQL access to verify data and debug production issues?▼

Yes. This Skill is designed for investigating data problems, verifying schema contents, counting records, understanding data relationships, and analyzing user conversations—all from production without modification risk.

Do I need special credentials to access the production database securely?▼

Read-only credentials load from arsenal/.env, isolating sensitive access from application code. The Skill mandates reviewing data quirks documentation before querying to ensure safe, informed exploration of production PostgreSQL.

Can I switch between production and development databases while inspecting data?▼

The Skill provides tooling to switch between production and development PostgreSQL instances, letting you compare data models, verify behavior differences, and validate schema or table contents across environments.

What limitations should I know before querying production data with read-only access?▼

Read-only access prevents modifications but requires understanding data quirks documented in the Skill. Queries use psql and operate within the credential scope defined in arsenal/.env, constraining exploration to permitted tables and schemas.