exploring-data-catalog

Inventories and audits AWS Glue Data Catalog assets across S3 Tables, Redshift-federated, and remote Iceberg catalogs.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill exploring-data-catalog-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploring-data-catalog
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/exploring-data-catalog
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill exploring-data-catalog-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams lose track of what data exists across their AWS account—databases, tables, formats, and catalogs spread across Glue, S3 Tables, and federated sources. This Skill produces a structured, read-only inventory and audit of the entire data landscape without running any queries. ## Core Features & Use Cases - Catalog Landscape Discovery: Enumerates all catalogs via aws glue get-catalogs and classifies them as default Glue, S3 Tables, Redshift-federated, or remote Iceberg. - Database and Table Enumeration: Lists databases and tables per catalog, including S3 Tables API enumeration, and flags tables not registered in Glue (not queryable via Athena). - Audit and Quality Analysis: Reports data formats in human-readable terms, partitioning, stale tables, missing descriptions, and optimization recommendations using a discovery checklist. - Use Case: A data engineer joining a new account runs a full landscape discovery to get catalog counts by type, total databases and tables, unregistered S3 Tables, and a list of CSV tables that should be converted to Parquet. ## Quick Start Ask the assistant to inventory the AWS Glue Data Catalog in your region, optionally narrowing the scope with a catalog name, database name, table name, or S3 path.

Frequently Asked Questions about exploring-data-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all databases and tables in AWS Glue Data Catalog?

Use aws glue get-catalogs with --include-root to find all catalogs, then run get-databases and get-tables per catalog. Pass --next-token for paginated results until no more tokens are returned.

How to audit S3 Tables registered in AWS Glue?

Enumerate table buckets with aws s3tables list-table-buckets, then list namespaces and tables per bucket. Compare results against Glue catalogs where FederatedCatalog.ConnectionName equals aws:s3tables, and flag any S3 Tables not registered in Glue since they are not queryable via Athena.

Can this skill run Athena queries during catalog discovery?

No, the discovery workflow is strictly read-only metadata enumeration and must not execute start-query-execution. Query execution belongs to a separate querying-data-lake skill.

Why is the default Glue catalog missing from get-catalogs results?

The default account catalog is omitted unless you pass --include-root to aws glue get-catalogs. Re-run the command with that flag to capture the root catalog alongside sub-catalogs.

What catalog types does AWS Glue discovery support?

Four types are classified: default Glue catalogs, S3 Tables catalogs (FederatedCatalog with ConnectionName aws:s3tables), Redshift-federated catalogs (TargetRedshiftCatalog present), and remote Iceberg catalogs such as Snowflake or Databricks connections.