How do I install the Investigating Postgres skill?

Run npx skillmds@latest add jovandyaz/investigating-postgres in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Investigating Postgres safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Investigating Postgres?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Investigating Postgres free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Investigating Postgres?

jovandyaz (@jovandyaz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Investigating Postgres by jovandyaz

Name: Investigating Postgres
Author: jovandyaz

Investigating Postgres

Runs read-only investigations against Knowtis PostgreSQL databases — usage questions, data debugging, schema exploration — under a strict SELECT-only contract with PII redaction. Use when asked to query, count, inspect, or debug data ("cuántas notas", "qué usuarios", "revisa en la base de datos", "query the DB"). Never use for schema changes or data mutations — schema evolution goes through managing-drizzle-migrations, and flag/data changes go through the API.

jovandyaz 4ae1a58 4 files · 8.8 KB Updated Sep 17, 2026

File contents

Investigating Postgres (read-only)

Answer data questions against Knowtis databases without ever mutating them. The full contract is in references/read-only-contract.md; the table map is in references/schema-map.md.

Contract (non-negotiable)

Database-enforced read-only. MCP connections must use a dedicated read-only role. Run psql investigations inside BEGIN TRANSACTION READ ONLY with ON_ERROR_STOP; if a production connection cannot prove that boundary, do not query it.
SELECT/WITH only. A CTE must end in a read-only SELECT. No INSERT, UPDATE, DELETE, TRUNCATE, DDL, mutating CTE, or session-changing SET. Redirect mutations to APIs, migrations, or the application.
Schema first. Read apps/api/src/database/schema/ (or the MCP schema tools) before writing SQL — column names come from the source of truth, not from memory.
Connection comes from the user's environment. Use pg-knowtis-local / pg-knowtis-prod or psql "$DATABASE_URL". Never construct, request, or echo credentials/connection strings.
LIMIT every row-listing query (default 50). Aggregate where possible.
Redact PII by default in output: user emails, note titles/content, session tokens, provider keys. Show them only on explicit request and never against prod without confirmation.
Say which database answered (local vs prod). Treat prod as sensitive: prefer local unless the question is explicitly about production.

Workflow

Restate the question as the data needed.
Load the schema for the tables involved (references/schema-map.md lists what lives where).
Write the query with CTEs for readability; explain the join logic in one line.
Execute via MCP or psql; present results as a compact table plus a one-paragraph interpretation.
Empty results are an answer — report them as such; never fabricate rows.

---name: investigating-postgresdescription: Runs read-only investigations against Knowtis PostgreSQL databases — usage questions, data debugging, schema exploration — under a strict SELECT-only contract with PII redaction. Use when asked to query, count, inspect, or debug data ("cuántas notas", "qué usuarios", "revisa en la base de datos", "query the DB"). Never use for schema changes or data mutations — schema evolution goes through managing-drizzle-migrations, and flag/data changes go through the API.license: MIT---# Investigating Postgres (read-only)Answer data questions against Knowtis databases without ever mutating them. The full contract is in [references/read-only-contract.md](references/read-only-contract.md); the table map is in [references/schema-map.md](references/schema-map.md).## Contract (non-negotiable)1. **Database-enforced read-only.** MCP connections must use a dedicated read-only role. Run psql investigations inside `BEGIN TRANSACTION READ ONLY` with `ON_ERROR_STOP`; if a production connection cannot prove that boundary, do not query it.2. **SELECT/WITH only.** A CTE must end in a read-only SELECT. No INSERT, UPDATE, DELETE, TRUNCATE, DDL, mutating CTE, or session-changing `SET`. Redirect mutations to APIs, migrations, or the application.3. **Schema first.** Read `apps/api/src/database/schema/` (or the MCP schema tools) before writing SQL — column names come from the source of truth, not from memory.4. **Connection comes from the user's environment.** Use `pg-knowtis-local` / `pg-knowtis-prod` or `psql "$DATABASE_URL"`. Never construct, request, or echo credentials/connection strings.5. **LIMIT every row-listing query** (default 50). Aggregate where possible.6. **Redact PII by default** in output: user emails, note titles/content, session tokens, provider keys. Show them only on explicit request and never against prod without confirmation.7. **Say which database answered** (local vs prod). Treat prod as sensitive: prefer local unless the question is explicitly about production.## Workflow1. Restate the question as the data needed.2. Load the schema for the tables involved ([references/schema-map.md](references/schema-map.md) lists what lives where).3. Write the query with CTEs for readability; explain the join logic in one line.4. Execute via MCP or psql; present results as a compact table plus a one-paragraph interpretation.5. Empty results are an answer — report them as such; never fabricate rows.

Frequently asked questions