← ClaudeAtlas

pythia-setuplisted

Use when setting pythia up for a project or a machine - writing connections.json, creating a least-privilege agent user, wiring the SQLcl MCP server, or diagnosing a connection that will not open. Also the place to start when check prints a privilege warning.
thaildhe172591/pythia · ★ 4 · AI & Automation · score 77
Install: claude install-skill thaildhe172591/pythia
# Setting Up **Announce at start:** "Using pythia-setup to configure the database access." **Phase:** Do — one-time harness setup; everything after runs through Learn → Ask → Do Set up in this order: connection first (everything else needs it), the least-privilege user second (the only protection that cannot be bypassed), SQLcl MCP last (optional, reads only). ## 1. Connection Create `.pythia/connections.json` at the project root — `pythia install` scaffolds it (pip installs: `pip install pythia-plsql`), or copy `examples/connections.example.json` from a clone. Fill it in. Rules pythia applies: - One entry: used as-is. Several entries: the path segment directly under the project root picks one (`root/DEV/...` → `DEV`), else the entry named by a top-level `"default": "<name>"`. Ambiguity is an error, never a guess. - `--conn NAME` and `PYTHIA_CONNECTION` override everything; the `PYTHIA_USER/PYTHIA_PASSWORD/PYTHIA_DSN` variables bypass the file. - The file holds credentials: install writes it into `.gitignore` (commit that line) — keep it that way, and keep it out of chat and screenshots. `pythia doctor` fails if git tracks it. - Thin mode first; on `DPY-3015` (old 10G password verifier), `DPY-3010` (database before 12.1) or `DPY-3001` it retries in thick mode through an Oracle Client. `"thick": true|false` and `"lib_dir"` pin it (GUIDE §2). Verify with `pythia check`: it prints who you are connected as and object counts. A failure names the connection and