ClaudeSuperPower

finding-data-lake-assets

Skill

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

Install

git clone https://github.com/aws/agent-toolkit-for-aws.git ~/.claude/skills/finding-data-lake-assets

What is finding-data-lake-assets?

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).

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~120 tokens of context used while enabled, before you invoke anything

Documentation

README · ~10 min read

Find Data Lake Assets

Overview

Resolves data lake asset references to concrete catalog entries. Acts as a resolver for other skills and direct user requests. Covers Glue, S3, S3 Tables, and Redshift. Optimized for low token usage — return the answer fast and get out of the way.

Constraints for parameter acquisition:

  • 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

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills