agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/data/snowflake-validation/SKILL.md

snowflake-validation

Skill19 starsChanged 2 months agoMITView on GitHub

HOW — Read-only Snowflake validation patterns: use repo-documented CLI (snowflake/sql) or

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the task or repo requires Snowflake verification.

    line 10
  2. Very specific:

    Read repo docs for: connection method (env vars, profiles.yml, SSO), Snowflake SQL or Snowflake CLI (snow) usage, and …

    line 20
  3. Distinctive:

    No secrets in tickets, PRs, or command lines in logs pasted to chat—use env vars and documented patterns only.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Snowflake validation (HOW)

Use when the task or repo requires Snowflake verification. Client workflows may delegate here alongside dbt-validation.

Boundaries

  • Read-only validation unless the user and repo explicitly authorize DDL/DML.
  • Never claim “Snowflake validation passed” or “query succeeded” without credentials and observed outputs (or explicit statement that checks were skipped).
  • Do not rotate keys, change roles, or alter security objects from this skill unless the repo’s AGENTS.md clearly authorizes it and the user approves.

Discovery

Read repo docs for: connection method (env vars, profiles.yml, SSO), Snowflake SQL or Snowflake CLI (snow) usage, and warehouse/database/schema defaults.

Patterns

SituationAction
Credentials availableRun minimal SELECT statements or documented smoke queries; record that they were executed
Snowflake CLI documentedUse repo’s exact commands; check snow --help for current subcommands
No credentialsState skipped in Jira/PR; list what would be validated when access exists
dbt + SnowflakeCoordinate with dbt-validation; Snowflake may be exercised indirectly via dbt

Evidence

  • For each run: what ran (object or test name), environment (non-secret), result (row count, success/failure).
  • Redact account identifiers if the user requests privacy in chat.

Safety

  • No secrets in tickets, PRs, or command lines in logs pasted to chat—use env vars and documented patterns only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free