CtrlK
BlogDocsLog inGet started
Tessl Logo

querying-data-lake

Execute and manage Athena SQL queries across default and federated catalogs (Glue, S3 Tables, Redshift). Triggers on phrases like: query data, run SQL, athena query, analyze table, SQL query, workgroup status, profile table, query Redshift catalog, query S3 Tables. Do NOT use for finding specific data assets (use finding-data-lake-assets), full catalog audits (use exploring-data-catalog), importing data (use ingesting-into-data-lake).

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with a clear sequenced workflow, executable commands, and clean progressive disclosure into two real reference files. The only weakness is mild redundancy of constraints across sections that could be deduplicated.

Suggestions

Consolidate the recurring 'confirm the output S3 location before executing' constraint into a single authoritative statement rather than repeating it in parameter acquisition, section 6, and Principles.

Remove the 'Always select workgroup before executing' bullet from Principles since section 2 already mandates it as a MUST constraint.

Consider folding the small standalone principles list into the relevant workflow steps to avoid restating rules already expressed as Constraints.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence with no concept padding, but several constraints recur across sections (e.g. 'confirm the output S3 location before executing' in parameter acquisition, section 6, and Principles; workgroup selection restated in Principles), adding tokens that could be tightened.

2 / 3

Actionability

Provides executable commands ('aws sts get-caller-identity', a full 'aws athena start-query-execution' tool call), precise table-addressing syntax ('"awsdatacatalog".database.table', 'Catalog=s3tablescatalog/<BUCKET_NAME>'), and concrete classification/troubleshooting tables.

3 / 3

Workflow Clarity

A clearly sequenced seven-step flow (verify -> workgroup -> asset -> schema -> build -> classify/execute -> present/recover) with explicit confirmation checkpoints for destructive statements and error-recovery feedback loops in the troubleshooting table.

3 / 3

Progressive Disclosure

The body is an overview that delegates detail to two real, one-level-deep reference files (workgroup-selection.md, query-patterns.md, both verified present), clearly signaled inline and re-listed under Additional Resources, with the core flow kept inline.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, explicit trigger phrases, and clear negative guidance separating it from sibling skills. It answers what, when, and when-not concisely.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('Execute and manage Athena SQL queries') and specific catalogs ('Glue, S3 Tables, Redshift'), matching the anchor for listing multiple specific concrete actions rather than just naming a domain.

3 / 3

Completeness

Explicitly answers both what (execute/manage Athena SQL queries across catalogs) and when ('Triggers on phrases like: ...'), with negative-trigger guidance, matching the anchor that clearly answers both what AND when.

3 / 3

Trigger Term Quality

Provides broad natural-language triggers users would say ('run SQL', 'athena query', 'query data', 'analyze table'), matching good coverage of natural terms rather than partial coverage.

3 / 3

Distinctiveness Conflict Risk

Explicit 'Do NOT use for ... (use finding-data-lake-assets / exploring-data-catalog / ingesting-into-data-lake)' disambiguation gives it a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aws/agent-toolkit-for-aws
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.