finding-data-lake-assets — Skills

What it does

You MUST accept a single argument: table name, keyword, column name, or S3 path

You MUST accept the argument as direct input or a pointer to a file containing the spec

You MUST ask for the target AWS region if not already set

You MUST confirm ambiguous input before searching (e.g., "Did you mean table X or bucket Y?")

You MUST respect the user's decision to abort at any step

You MUST verify AWS MCP server tools (awscallaws) are available; fall back to AWS CLI if not

You MUST confirm credentials with aws sts get-caller-identity

Requirements & configuration

S3, S3 Tables, and Redshift. Optimized for low token usage — return the

do not expect PascalCase inside. The operations you need:

misses, you MAY need to scan across databases. Do NOT issue separate

| get-tables fails with missing database | Requires --database-name | For cross-database search, use search-tables instead |

| Delegating caller expects verbose output | Other skill called this as a resolver | Return minimal output — caller needs a catalog reference, not a formatted summary |

finding data lake assets

Source

Repository: https://github.com/aws/agent-toolkit-for-aws

finding-data-lake-assets FAQ

What does the finding-data-lake-assets skill do?

>- Resolve data lake and lakehouse asset references across Glue Data Catalog, S3, S3 Tables, and Redshift. Triggers on: find the table, where is our data, which table has, locate dataset, find data for, search catalog, what tables match, Redshift table, lakehouse table, data lake table, warehouse table, reverse lookup S3 path. Do NOT use for: full catalog audits (use exploring-data-catalog), running queries (use querying-data-lake), creating tables (use creating-data-lake-table). You MUST accept a single argument: table name, keyword, column name, or S3 path You MUST accept the argument as direct input or a pointer to a file containing the spec

What does finding-data-lake-assets require?

S3, S3 Tables, and Redshift. Optimized for low token usage — return the do not expect PascalCase inside. The operations you need: misses, you MAY need to scan across databases. Do NOT issue separate | get-tables fails with missing database | Requires --database-name | For cross-database search, use search-tables instead | | Delegating caller expects verbose output | Other skill called this as a resolver | Return minimal output — caller needs a catalog reference, not a formatted summary |

How do I install finding-data-lake-assets?

Run: npx -y skills add https://github.com/aws/agent-toolkit-for-aws --skill finding-data-lake-assets --agent claude-code — the source lives at github.com/aws/agent-toolkit-for-aws.

Maintain finding-data-lake-assets?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[finding-data-lake-assets on getagentictools](https://getagentictools.com/skills/aws-agent-toolkit-for-aws-finding-data-lake-assets?ref=badge)

npx agentictools info skills/aws-agent-toolkit-for-aws-finding-data-lake-assets

The second line is the CLI lookup for this page — handy in READMEs and docs.