CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

84%

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

The canonical home for this skill is querying-data-lake in aws/agent-toolkit-for-aws

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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 an explicit multi-step workflow, validation checkpoints, error-recovery guidance, and clean progressive disclosure into two real reference files. The main weaknesses are repeated constraint statements that pad the token budget and a missing concrete command for retrieving query results/cost in the final step.

Suggestions

Deduplicate constraint statements: 'confirm the output S3 location', 'respect the user's decision to abort', and the workgroup-first rule each appear 2-3 times across the Overview, task sections, and Principles — state each once in the most relevant section.

Add the concrete command for retrieving results and query statistics in step 7 (e.g., 'aws athena get-query-execution / get-query-results --query-execution-id <ID>') so the execute-then-present loop is fully executable.

Trim or merge the Principles section, which largely restates constraints already covered in the Common Tasks sections.

DimensionReasoningScore

Conciseness

The body is mostly dense and efficient (constraint bullets, tables, exact addressing rules) but several constraints are stated multiple times: 'You MUST confirm the output S3 location before executing' appears in both the Overview and task 6, 'You MUST respect the user's decision to abort' appears twice, and the workgroup-first rule is repeated in task 2 and Principles. This repetition goes beyond the 'minor instances' of the score-4 anchor, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Guidance is largely executable: 'aws sts get-caller-identity', a complete 'aws athena start-query-execution --work-group <WORKGROUP_NAME> --query-string ...' example, catalog-specific addressing rules, a statement classification table, and an error/cause/fix table. The minor gap is that step 7 (Present and Recover) gives no command for fetching results or query statistics (e.g., get-query-results/get-query-execution), keeping it just below the fully-executable score-5 anchor.

4 / 5

Workflow Clarity

Seven clearly sequenced tasks with explicit validation checkpoints (verify credentials first, select a workgroup before submitting, state the resolved asset, classify statements and confirm destructive ones) and feedback loops for error recovery via the troubleshooting table and 'On failure, list available workgroups and let the user choose which to retry with'. Argument routing is explicitly ordered ('Resolve in this order; stop at the first match'), matching the score-5 anchor.

5 / 5

Progressive Disclosure

The body is a clear overview that defers detail to two real, one-level-deep references, each well-signaled at its point of use (workgroup-selection.md in task 2, query-patterns.md in argument routing) and again under Additional Resources. Content is appropriately split with easy navigation, matching the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 capability statement, explicit trigger phrases with synonyms, and clear negative boundaries against sibling skills. The only weaknesses are minor — a couple of natural trigger phrasings are absent and the action list is not fully comprehensive.

DimensionReasoningScore

Specificity

The description states concrete actions ('Execute and manage Athena SQL queries across default and federated catalogs (Glue, S3 Tables, Redshift)') with named technologies, though it stops short of comprehensively listing capabilities like cost reporting or error recovery. It lists several specific actions with minor coverage gaps, matching the score-4 anchor rather than the comprehensive score-5 anchor.

4 / 5

Completeness

It clearly answers 'what' ('Execute and manage Athena SQL queries across default and federated catalogs') and 'when' with an explicit trigger clause ('Triggers on phrases like: query data, run SQL, athena query...'), matching the anchor that requires both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Nine natural trigger phrases are provided ('query data, run SQL, athena query, analyze table, SQL query, workgroup status, profile table, query Redshift catalog, query S3 Tables') with good synonym coverage of query actions. A few natural terms users might say are missing (e.g., 'execute SQL', 'run a query', 'query the data lake'), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Athena SQL-query niche is distinct and the description adds explicit negative boundary guidance ('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)'), giving minimal conflict risk and matching the score-5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

mreferre/aws-agent-toolkit-skills

Path

.kiro/skills/querying-data-lake/SKILL.md

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.