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.
Install with Tessl CLI
npx tessl i github:github/awesome-copilot --skill snowflake-semanticview80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually use, explicitly states both what the skill does and when to use it, and carves out a distinct niche that won't conflict with other database or SQL skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, alter, and validate Snowflake semantic views', 'validate semantic-view DDL against Snowflake via CLI', and 'guide Snowflake CLI installation and connection setup'. | 3 / 3 |
Completeness | Clearly answers both what ('Create, alter, and validate Snowflake semantic views using Snowflake CLI') and when ('Use when asked to build or troubleshoot semantic views...') with explicit trigger scenarios including DDL validation and CLI setup guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Snowflake', 'semantic views', 'semantic layer', 'CREATE/ALTER SEMANTIC VIEW', 'DDL', 'Snowflake CLI', 'snow', 'connection setup'. Good coverage of both technical terms and common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Snowflake semantic views specifically, with distinct triggers like 'SEMANTIC VIEW', 'snow' CLI, and 'semantic layer definitions'. Unlikely to conflict with general SQL or other database skills. | 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 skill provides a solid workflow structure with good validation practices and clear sequencing for semantic view creation. However, it leans too heavily on external documentation links rather than providing inline executable examples, and has some redundancy between sections. The actionability would improve significantly with complete DDL examples rather than just syntax references.
Suggestions
Include a complete, executable CREATE SEMANTIC VIEW DDL example with all required elements (dimensions, facts, metrics, synonyms, comments) rather than just linking to documentation
Remove the redundant 'Synonyms And Comments' and 'Validation Pattern' sections by consolidating their content into the main workflow steps
Add a concrete example of the `snow sql` command with actual DDL rather than just placeholders to make the validation step copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (synonyms/comments section repeats workflow step 4, validation pattern restates what's in the workflow). Some explanatory text could be trimmed. | 2 / 3 |
Actionability | Provides concrete CLI commands and SQL examples, but relies heavily on external documentation links rather than inline executable code. The DDL syntax itself is not shown - only references to docs. The validation template uses placeholders rather than a complete example. | 2 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (11 numbered steps), explicit validation checkpoint (step 7-8), iteration loop for failures, and cleanup step. The validate-then-apply pattern with temporary names is well-defined. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but external references are all to Snowflake docs rather than companion skill files. Some content is duplicated between sections (synonyms/comments appears twice). Could benefit from separating setup into a referenced file. | 2 / 3 |
Total | 9 / 12 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
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
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.