finding-data-lake-assets

Resolve data lake asset references to catalog entries across Glue, S3, and Redshift.

2.3k|234|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill finding-data-lake-assets-aws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finding-data-lake-assets
Source: https://github.com/aws/agent-toolkit-for-aws/tree/main/plugins/aws-data-analytics/skills/finding-data-lake-assets
Command: npx skills add https://github.com/aws/agent-toolkit-for-aws --skill finding-data-lake-assets-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolves data lake asset references to concrete catalog entries across Glue Data Catalog, S3, S3 Tables, and Redshift. It acts as a resolver for other skills and direct user requests, optimized for low token usage and fast, reliable results.

Core Features & Use Cases

  • Resolve assets across multiple catalogs to surface exact table or dataset references.
  • Layered search strategy (Glue first, fallback to S3/Redshift) with validation and ambiguity prompts.
  • Use case: quickly locate and validate the catalog entry for a given table or S3 path to support data lineage and governance.

Quick Start

Ask it to locate a dataset by table name or S3 path and it will return the best matching catalog entry.

Frequently Asked Questions about finding-data-lake-assets

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

FAQPage Schema
How do I find a specific table or dataset across my data lake catalogs?

To resolve data lake assets across catalogs, it searches Glue Data Catalog first, falling back to S3, S3 Tables, and Redshift. It applies region confirmation and ambiguity prompts to pinpoint exact catalog entries for your tables or datasets.

What is the best way to locate an S3 path or table name in the Glue Data Catalog?

The best way to resolve an S3 path or table name in the Glue Data Catalog is using a layered search strategy that checks Glue first, then validates the entry against fallback sources like S3 and Redshift to ensure the catalog location is deterministic.

Can I resolve data lake asset references across both S3 Tables and Redshift simultaneously?

Yes, you can resolve data lake asset references across S3 Tables and Redshift simultaneously. The resolver searches multiple catalogs in sequence, applying explicit source reporting to drive deterministic results for each referenced dataset or path.

How does ambiguity resolution work when multiple catalog entries match my dataset name?

Ambiguity resolution for matching catalog entries works by applying region confirmation and explicit source reporting. When multiple data lake assets match a name, the resolver prompts for clarification to ensure the returned Glue, S3, or Redshift entry is correct.

Do I need to specify an AWS region to discover data lake assets in Glue or Redshift?

Yes, region confirmation is required to discover data lake assets in Glue or Redshift. The resolver applies a layered search strategy that validates the specific region to drive deterministic results and pinpoint the exact catalog entry.