Skip to content
Back to skills

Snowflake Data Analyst

ASecurity

Business rules and domain knowledge for answering natural-language data questions accurately against Snowflake.

  • 77 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 11, 2026
databasessql

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 11, 2026

npx -y skills add Gyrus-Dev/frosty --skill snowflake-data-analyst --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Snowflake Data Analyst?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Snowflake Data Analyst
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gyrus-dev-snowflake-data-analyst/badge)](https://www.skillsdirectory.com/skills/gyrus-dev-snowflake-data-analyst)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: snowflake-data-analyst
description: Business rules and domain knowledge for answering natural-language data questions accurately against Snowflake.
---

Before generating SQL for any data question:

1. Read `references/business-rules.md` to load domain context — metric definitions,
   canonical column names, standard filters, common join paths, and date conventions.

2. Apply any relevant rules when writing the SQL:
   - Use the exact column and calculation defined for each metric (e.g. "revenue" may
     map to `SUM(ORDER_VALUE) WHERE STATUS = 'COMPLETED'`, not a raw column sum).
   - Apply standard filters listed in the rules (e.g. exclude test records, restrict
     to active statuses) unless the user explicitly asks to include them.
   - Use the documented join keys when combining tables — do not guess join columns
     from column name similarity alone.
   - Filter on the canonical date column per table (e.g. always filter ORDERS on
     ORDER_DATE, not CREATED_AT) unless the user specifies otherwise.

3. If the user's question references a term defined in the business rules, always
   use the rule definition — do not derive it from column names alone.

4. If the business-rules.md file is empty or has only template placeholders, skip
   this step and fall back to schema context from discover_schema.

5. If no rule applies to part of the question, use schema context and reasonable
   Snowflake defaults.

Files in this skill

  • SKILL.md1.4 KB
  • references/business-rules.md2.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.