Connect ada to a Postgres database (read-only SQL) via the Postgres MCP server.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill connect-postgres --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Connect Postgres?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-connect-postgres)More formats (shields.io, HTML) on the badges page.
---
name: connect-postgres
description: Connect ada to a Postgres database (read-only SQL) via the Postgres MCP server.
category: connectors
---
# Connect Postgres
Use when the user wants ada to inspect a schema or run read-only analytics queries against Postgres.
1. Add the connector: `ada mcp add postgres`.
2. Edit the connection string in `.ada/mcp.json` (the last arg) to point at your database — prefer a **read-only** role and a non-prod replica.
3. Keep credentials out of the file: use a role whose password is supplied via the environment or a `.pgpass`, not inline.
4. Trust the project and start `ada`; the tools appear as `postgres__*` (schema introspection + query).
5. Start by listing tables / describing the schema before writing any query.
## Rules
- Connect with a read-only user — never hand ada write/DDL credentials to "just query".
- Point at a replica or dev DB, not production, when possible.
- Review any generated SQL before running it on a large table; add `LIMIT` while exploring.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...