Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup.
86
81%
Does it follow best practices?
Impact
93%
1.75xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines a specific niche (Snowflake semantic views via CLI), lists concrete actions, includes natural trigger terms at both conceptual and command levels, and provides explicit 'Use when' guidance. It follows the third-person voice convention and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create, alter, validate semantic views, validate DDL against Snowflake via CLI, and guide CLI installation and connection setup. | 3 / 3 |
Completeness | Clearly answers both what (create, alter, validate Snowflake semantic views using Snowflake CLI) and when (explicit 'Use when...' clause covering building, troubleshooting, validating DDL, and CLI setup guidance). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Snowflake', 'semantic views', 'semantic layer', 'CREATE SEMANTIC VIEW', 'ALTER SEMANTIC VIEW', 'Snowflake CLI', 'snow', 'DDL', 'connection setup'. Good coverage of both conceptual and command-level terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Snowflake semantic views specifically with Snowflake CLI tooling. Unlikely to conflict with general SQL skills, other Snowflake skills, or generic database skills due to the precise focus on semantic views and the snow CLI. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid skill with an excellent multi-step workflow that includes validation, error recovery, and cleanup. Its main weaknesses are redundancy between sections (synonyms/comments guidance appears twice) and reliance on external links for critical syntax like CREATE SEMANTIC VIEW DDL, which reduces immediate actionability. Tightening the content and including a minimal inline DDL template would significantly improve it.
Suggestions
Include a minimal but complete CREATE SEMANTIC VIEW DDL example inline rather than only linking to external docs, so Claude has copy-paste-ready syntax.
Consolidate the synonyms/comments guidance into a single location—either the workflow step or the dedicated section—to eliminate redundancy.
Remove the 'Notes' section or merge its points into the relevant workflow steps, as all three notes restate information already covered above.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy—synonyms/comments guidance is repeated across the workflow section and the dedicated 'Synonyms And Comments' section. The 'Notes' section also restates points already made. However, it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides a clear workflow with specific steps and includes a CLI template and SQL example, but relies heavily on external documentation links rather than providing inline executable DDL examples. The CREATE SEMANTIC VIEW syntax is never shown—only linked—which reduces copy-paste readiness. | 2 / 3 |
Workflow Clarity | The 11-step workflow is clearly sequenced with explicit validation checkpoints (steps 6-8), a feedback loop for failed validation, cleanup of temporary artifacts (step 11), and a final confirmation query (step 10). This is a strong workflow with proper error recovery. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic—the synonyms/comments section duplicates workflow content, and external links are used for core syntax that could benefit from a brief inline summary or a dedicated reference file. No content is split into separate files despite the skill being moderately long. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
4020587
Table of Contents
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.