CtrlK
BlogDocsLog inGet started
Tessl Logo

snowflake-development

Comprehensive Snowflake development assistant covering SQL best practices, data pipeline design (Dynamic Tables, Streams, Tasks, Snowpipe), Cortex AI functions, Cortex Agents, Snowpark Python, dbt integration, performance tuning, and security hardening.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/snowflake-development/SKILL.md

The canonical home for this skill is snowflake-development in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

83%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 dense, highly actionable reference with lean prose and executable examples across SQL, pipelines, Cortex AI, Snowpark, and dbt. The main gap is the absence of explicit validation checkpoints for its batch/destructive operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints to destructive/batch flows, e.g. 'After MERGE, verify row counts: SELECT count(*) before/after' or a validate-then-resume step for tasks.

Factor the Cortex AI function table and deprecated-function list into a references/cortex.md file and link from SKILL.md to reduce inline reference bulk.

Include a short 'Build a pipeline' numbered workflow (choose approach → create DT/stream → validate → resume task → monitor) with a verify step to lift workflow clarity above 3.

DimensionReasoningScore

Conciseness

The body is lean — bullets, tables, and executable code with no padding and no explanation of concepts Claude already knows; every line earns its place (e.g. 'DataFrames are lazy — executed on collect()/show().').

5 / 5

Actionability

Provides copy-paste-ready, executable examples across domains — MERGE upserts, Dynamic Table DDL, Stream/Task DDL with RESUME, the Cortex Agent $spec$ block, Snowpark Session setup, and dbt config macros — covering the common cases.

5 / 5

Workflow Clarity

Sequences are present (e.g. create stream → create task → ALTER TASK RESUME) and a Common Error Patterns table offers recovery, but batch/destructive operations (MERGE, pipelines, CREATE OR REPLACE) lack explicit validate-before-commit checkpoints, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-sectioned reference with clear headers and tables for navigation. Structure is good, though the Cortex function reference and code-pattern catalog could be split into separate reference files for a cleaner overview.

4 / 5

Total

17

/

20

Passed

Description

75%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 specific, well-scoped description with strong capability coverage and a clear Snowflake niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for help with Snowflake SQL, building data pipelines, Cortex AI, or Snowpark Python.'

Add a few natural synonyms or tokens users say ('Snowflake SQL', '.sql', 'Snowpipe ingestion', 'Cortex Search/Analyst') to broaden trigger-term coverage.

Lead with the trigger phrase before the capability list so the 'when' is as prominent as the 'what'.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities across the domain — 'SQL best practices, data pipeline design (Dynamic Tables, Streams, Tasks, Snowpipe), Cortex AI functions, Cortex Agents, Snowpark Python, dbt integration, performance tuning, and security hardening' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-term coverage ('Snowflake', 'SQL', 'data pipeline', 'Cortex AI', 'Snowpark Python', 'dbt') that users would actually say, but lacks synonyms and file extensions, so it stops short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

'Comprehensive Snowflake development assistant' carves a clear Snowflake-specific niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

20

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.