CtrlK
BlogDocsLog inGet started
Tessl Logo

snowflake-development

Use when writing Snowflake SQL, building data pipelines with Dynamic Tables or Streams/Tasks, using Cortex AI functions, creating Cortex Agents, writing Snowpark Python, configuring dbt for Snowflake, or troubleshooting Snowflake errors.

71

Quality

88%

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 snowflake-development in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The body is well-organized and highly actionable with strong executable examples and clear sectioning, supported by well-signaled one-level-deep references. Its weaknesses are missing validation checkpoints in batch/security workflows and referenced bundle files that are absent from the bundle.

Suggestions

Add explicit validation/verification steps to the Practical Workflows — e.g. after RBAC grants run 'SHOW GRANTS TO ROLE analyst_role;' to confirm, and after MERGE upserts verify row counts — to lift workflow clarity above the destructive/batch cap of 3.

Consolidate the overlapping Proactive Triggers, Anti-Patterns, and Common Errors sections (which all restate the SELECT *, colon-prefix, deprecated-Cortex, and credential issues) into a single table or cross-linked section to reduce redundancy and save tokens.

Either ship the referenced files under references/ and scripts/ (snowflake_sql_and_pipelines.md, cortex_ai_and_agents.md, troubleshooting.md, snowflake_query_helper.py) or remove the references and inline the essential content, since the current bundle points to paths that do not exist.

DimensionReasoningScore

Conciseness

The body is largely lean, using tables and code blocks to deliver Snowflake-specific rules (colon prefix, deprecated Cortex names, TARGET_LAG rules) rather than restating basics, but three sections — Proactive Triggers, Anti-Patterns, and Common Errors — rehash the same issues from slightly different angles and could be consolidated.

4 / 5

Actionability

Provides copy-paste-ready, executable artifacts throughout — CLI commands in Quick Start, complete MERGE/Dynamic Table/Stream-Task SQL, a Snowpark Session builder, dbt config blocks, and Cortex function calls covering the common cases.

5 / 5

Workflow Clarity

The three Practical Workflows give clear numbered sequences, but operations that are batch- or security-sensitive (RBAC grants, MERGE upserts, pipeline creation) lack explicit validation/verification checkpoints, capping workflow clarity at 3 per the destructive/batch rule.

3 / 5

Progressive Disclosure

Structure is good: a focused overview with clearly signaled one-level-deep references (inline '> See references/...' callouts plus a Reference Documentation table) to three reference docs and one script, but the referenced bundle paths (references/, scripts/) do not exist in the skill bundle, a notable navigation gap.

4 / 5

Total

16

/

20

Passed

Description

100%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.

The description is a strong, third-person trigger clause that explicitly states what the skill does and when to use it, enumerating concrete Snowflake-specific capabilities. It is concise yet comprehensive with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing Snowflake SQL', 'building data pipelines with Dynamic Tables or Streams/Tasks', 'using Cortex AI functions', 'creating Cortex Agents', 'writing Snowpark Python', 'configuring dbt', 'troubleshooting Snowflake errors' — with comprehensive coverage of the skill's surface.

5 / 5

Completeness

Explicitly answers both what (the enumerated development actions) and when (the leading 'Use when writing Snowflake SQL...') with concrete trigger phrases, matching the anchor example.

5 / 5

Trigger Term Quality

Covers the natural terms users say — 'Snowflake SQL', 'data pipelines', 'Dynamic Tables', 'Streams/Tasks', 'Cortex AI', 'Cortex Agents', 'Snowpark Python', 'dbt for Snowflake', 'Snowflake errors' — including product-specific synonyms a user would name.

5 / 5

Distinctiveness Conflict Risk

A clear Snowflake-specific niche with distinct product triggers (Dynamic Tables, Cortex, Snowpark) that would not fire for other database skills, minimizing conflict risk.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-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.