Explore
Use this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: inventory, column profiles, PII detection, grain and data-quality problems, verified joins, ER diagrams, ad-hoc SQL probes, segmentation, and the semantic layer a repo declares (dbt, Ossie, SLayer, or Cube). Trigger it on an unmet precondition, not on phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work (building a model, fixing one, debugging wrong numbe
Install
npx skills add exmergo/dex --skill exploregit clone --depth 1 https://github.com/exmergo/dex.git /tmp/dex
mkdir -p ~/.claude/skills
cp -r /tmp/dex/skills/explore ~/.claude/skills/explorePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Explore Make sense of a warehouse or a local DuckDB database the way an analytics engineer does: rank what matters, drill selectively, and persist a draft map in `.dex/`. This skill is read-only: it writes nothing but the `.dex/` cache. ## Procedure Dex works in one loop: explore, transform, maintain. Every step runs one engine command, reads the single JSON envelope it prints, and decides the next step from that envelope. Step 1 only reads. Steps 2 to 4 write project files, commit and build on dev, so take them only when the task asks for a change; a task that asks what is in the data stops after step 1 and reports what it found. 1. **Explore before you write.** Before writing or fixing SQL against a table whose columns, types, grain, or join keys you have not verified in this session, run `explore map` (or `explore profile <tables>` for a few named ones) and read its grain, keys, PII flags, and data-quality findings. Answer ad-hoc questions with `explore query`, never with a raw database client. 2. **Plan the change.** Author the file content and hand it to `transform plan` (or `semantic define|update|plan` for the semantic layer). Nothing is written yet. Read the diffs, the `warnings`, and, on a model that already exists, `data.row_attribution`; re-plan until they describe the change you meant. 3. **Apply it.** `transform apply <plan-id>` writes the plan as a reviewable git
Details
- Skill name
explore- Repository
- exmergo/dex
- Path
skills/explore/SKILL.md- License
- Apache-2.0
- Repo updated
- 31 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Explore skill do?
Use this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: inventory, column profiles, PII detection, grain and data-quality problems, verified joins, ER diagrams, ad-hoc SQL probes, segmentation, and the semantic layer a repo declares (dbt, Ossie, SLayer, or Cube). Trigger it on an unmet precondition, not on phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work (building a model, fixing one, debugging wrong numbe
How do I install the Explore skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add exmergo/dex --skill explore. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Explore popular?
It lives in exmergo/dex, which has 107 GitHub stars and 46 forks, and is included in 1 curated skill list.
Related skills
Slr Prisma
116keemanxp/slr-prisma
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a revi
Neon Postgres Egress Optimizer
108neondatabase/agent-skills
Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.
Netlify Database
49netlify/context-and-tools
Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building a contact form or CRUD API, writing SQL migrations, wiring up Drizzle, running netlify database commands, testing with a local Postgres, or switching from Neon/Supabase/RDS to Netlify Database.
Neon Postgres
108neondatabase/agent-skills
Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching, autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Live queries, reactive UIs, and realtime data go to `neon-realtime`. Also use for "@neondatabase/serverless", "@neon/neon-js", "neon inspect db", "semantic search", "vector search", "full-
Database Sentinel
51Farenhytee/database-sentinel
Multi-backend database security auditor. Audits Supabase, Firebase (Firestore/RTDB/Storage/Functions/Remote Config), MongoDB (self-hosted + Atlas), self-hosted PostgreSQL, and self-hosted MySQL for RLS/rules misconfigurations, exposed credentials, auth bypasses, MongoBleed (CVE-2025-14847), pgBouncer CVE-2025-12819, mysql_native_password drift, ghost auth, and storage exposures. Use this skill whenever the user mentions database security, RLS or rule audits, security review, penetration testing a vibe-coded app, checking if their DB is exposed, hardening a backend, fixing security rules, or au
Redis Core
171redis/agent-skills
Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing/cleaning up Redis key naming.
Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.