thaildhe172591/pythia
Use when you need to understand anything in an Oracle schema - finding objects, reading PL/SQL source, signatures, table columns, DDL, searching code, or asking who uses what.
npx skills add thaildhe172591/pythia --skill pythia-explore
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Azure Storage Services including Blob Storage, File Shares, Queue Storage, Table Storage, and D…
567.1K installsQuery and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetr…
566.2K installsPostgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsGuides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…
269.8K installsPrisma Client API reference covering model queries, filters, operators, and client methods. Use…
269.3K installsPrisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …
267K installsOther skills from thaildhe172591/pythia · top by installs.
npx skills add thaildhe172591/pythia
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
3,578 B
SUMMARY.md
495 B
Announce at start: "Using pythia-explore — asking the database directly."
Phase: Learn
Repositories of exported .sql files go stale the day after export. A real mid-size system, audited in 2026, compared its repo dump against the live database:
| Object type | In the dump | In the database | Verdict |
|---|---|---|---|
| Procedures | 3,827 | 3,827 | matched |
| Tables | 952 | 952 | matched |
| Types | 0 | 115 | all missing |
| Packages | 0 | 9 | all missing |
| Indexes | 116 | 1,016 | ~89% missing |
Code that "reads fine" against the dump can reference types and packages the dump never heard of.
When the developer hands you a .sql file — "explain this procedure", "here is the export, what does it do" — the file is a claim, not the truth. Read it, then run pythia src <NAME> and answer from the database. If the two differ, say so first: which is newer is exactly what the developer needs to know, and it is invisible from the file alone. Never answer about a database object from a file alone while the database is reachable.
Read files as the answer only when the database is unreachable — and say that is what you are doing.
| Need | Command |
|---|---|
| Is the connection alive, what schema | pythia check |
| Find objects by name | pythia ls "PKG_%" |
| Read source, with the compiler's line numbers | pythia src NAME (--body, --spec) |
| A procedure/function signature | pythia args NAME |
| Columns and real data types | pythia cols TABLE_NAME |
| Full DDL | pythia ddl TABLE NAME |
| Search all PL/SQL text | pythia grep "text" |
| What an object depends on | pythia deps NAME |
| What depends on an object | pythia impact NAME |
| Exact identifier usages (beats grep) | pythia plscope NAME |
| Programs named like this one | pythia similar NAME |
| Everything currently broken | pythia invalid, pythia errors |
| A free-form question | pythia sql "select ..." (SELECT/WITH only) |
-- truncated ... orset "truncated": true in --json. If you do not see the marker, you saw everything; if you do, say so or fetch more (--limit, --offset, --max-lines) — never present a truncated list as complete.
plscope before grep for "where is X used": PL/Scope is recorded bythe compiler and exact; grep matches comments and look-alike names. If PL/Scope has no data, the command says so and grep is the fallback.
src line numbers are the compiler's own — an error at line 47means line 47 in src output. No offset arithmetic.
for the object you are actually working on.
Deeper reference — which dictionary views back these commands, PL/Scope enablement, licensing boundaries: reference/data-dictionary.md.