CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

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/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

72%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 strong, dense reference-style skill that concentrates on genuinely non-obvious Snowflake pitfalls and gives mostly executable examples. Its weaknesses are the absence of validation/verification steps for risky pipeline and DDL operations, and a monolithic single-file structure that could offload detailed reference material to bundle files.

Suggestions

Add explicit validation checkpoints to pipeline workflows (e.g. query INFORMATION_SCHEMA.TASK_HISTORY or SHOW TASKS after ALTER TASK ... RESUME to confirm the task is running, and check SYSTEM$STREAM_HAS_DATA before relying on a stream).

Replace the 'SELECT ...' placeholder in the task example with a concrete executable INSERT ... SELECT so the snippet is copy-paste ready.

Move the Cortex AI function table and the Common Error Patterns table into references/ files (e.g. references/cortex-functions.md, references/error-patterns.md) and link them from SKILL.md to reduce the main-file footprint.

DimensionReasoningScore

Conciseness

The body is lean and rule-dense with no concept padding: every section delivers Snowflake-specific gotchas (colon prefix rule, '$spec$' delimiter, TO_FILE argument split, deprecated function list) and assumes Claude's competence. Every token earns its place.

5 / 5

Actionability

Mostly executable SQL/Python snippets with concrete BAD/GOOD contrasts (e.g. the colon-prefix procedure pair and the MERGE example), but minor gaps remain: the task example uses a literal 'SELECT ...' placeholder and the stored procedure snippet omits the '$$' body delimiters.

4 / 5

Workflow Clarity

The 'Choosing Your Approach' table and the 'Common Error Patterns' table provide a decision sequence and error-to-fix mapping, but there are no explicit validation checkpoints (e.g. verifying task state after ALTER TASK ... RESUME). Since the skill covers destructive/batch operations (CREATE OR REPLACE, pipeline refresh), the missing validation steps cap this at 3.

3 / 5

Progressive Disclosure

Sections are clearly organized with headers and tables, but this is a single ~225-line file with no bundle references at all; content such as the Cortex function reference table and the error-pattern table could live in separate reference files. It is more organized than the anchor-2 'wall of text', but not the well-split anchor-4/5 structure.

3 / 5

Total

15

/

20

Passed

Description

66%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 product-name trigger terms, but it is missing any 'Use when ...' trigger guidance and leads with the fluffy word 'Comprehensive'. Adding an explicit when-to-use clause would resolve its main weakness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Snowflake, asks for Snowflake SQL, pipelines (Dynamic Tables, Streams, Tasks, Snowpipe), Cortex AI, Snowpark, or dbt on Snowflake.'

Drop the 'Comprehensive ... assistant covering' framing in favor of direct action verbs (e.g. 'Write and review Snowflake SQL, design data pipelines with Dynamic Tables/Streams/Tasks/Snowpipe, ...').

Include a few more natural user synonyms such as 'warehouse sizing', 'GRANTs', and 'stages' to round out trigger coverage.

DimensionReasoningScore

Specificity

It names the domain plus many specific sub-capabilities ('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') with only minor gaps. It falls short of a 5 because capabilities are listed as covered topics rather than concrete actions, and the 'Comprehensive ... assistant covering' framing is slightly padded.

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when ...' clause or equivalent explicit trigger guidance anywhere in the description; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage with product-specific natural terms users would actually say ('Snowflake', 'SQL', 'Cortex', 'Snowpark', 'dbt', 'Snowpipe', 'performance tuning'), plus named features like Dynamic Tables and Streams. A few natural terms are missing (e.g. 'warehouse', 'GRANT', 'stages', 'roles'), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The Snowflake-specific product names (Cortex, Snowpark, Snowpipe, Dynamic Tables) create a clear niche with minimal conflict risk. Minor overlap remains: generic phrases like 'dbt integration', 'performance tuning', and 'security hardening' could pull in non-Snowflake dbt or general SQL-tuning requests.

4 / 5

Total

15

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/snowflake-development/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.