Name: snowflake
Rating: 56.8 (1 reviews)
Author: membranedev

snowflake

Snowflake integration. Manage data, records, and automate workflows. Use when the user wants to interact with Snowflake data.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/snowflake/SKILL.md

Quality

Content

63%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 a well-sectioned, actionable guide with a strong, validated connection workflow. Its main weaknesses are an unnecessary conceptual intro and inlined reference material that would benefit from separate files now that no bundle exists.

Suggestions

Remove the introductory paragraph explaining what Snowflake is; Claude already knows this and it costs context tokens.

Move the proxy flags table and the clientAction state spec into a separate reference file (e.g. references/connections.md) and link to it from SKILL.md to improve progressive disclosure.

Tighten the action-search and action-run sections into a single sequenced workflow (search → inspect schema → run → read output) with an explicit checkpoint before running destructive queries.

Dimension	Reasoning	Score
Conciseness	The opening concept explainer ("Snowflake is a cloud-based data warehousing platform... Think of it as a database built for the cloud") and the hierarchical Warehouse/Database/Schema overview explain things Claude already knows, but the rest is mostly efficient command-focused content, fitting the score-3 anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (install, login, connection ensure, action run, request) with a flags table, but placeholders like CONNECTION_ID and actionId must be filled by the user, matching the score-4 anchor.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, though later sections (searching/running actions, proxy) read more as reference than sequenced workflow, fitting the score-4 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and no external references are used, while reference-style content (the flags table, clientAction object spec, agent-types list) is inlined rather than split out, matching the score-3 anchor for some structure with content that should be separate kept inline.	3 / 5
	Total	14 / 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.

The description is a solid, third-person statement with both a 'what' and a 'Use when' clause and a clearly distinct niche. It is held back from the top by somewhat generic action verbs and limited trigger-term variation.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Snowflake actions such as executing SQL queries, browsing warehouses/databases/schemas, and retrieving query results.

Broaden trigger terms to include natural phrases users say, e.g. "run SQL", "query a warehouse", or "get query results".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Snowflake domain plus a couple of actions, but those actions are fairly generic and not a comprehensive concrete list, matching the score-3 anchor.	3 / 5
Completeness	It states what ("Snowflake integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Snowflake data"), but the trigger could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The keyword "Snowflake" and the phrase "interact with Snowflake data" are relevant, but common variations/synonyms (e.g., query, SQL, warehouse) are missing, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Snowflake is a distinct product niche with a clear, specific trigger ("interact with Snowflake data"), giving minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/snowflake/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.