← Browse

@gyrus-dev/snowflake-create-file-format

A

Consult Snowflake CREATE FILE FORMAT parameter reference before generating any CREATE FILE FORMAT DDL.

skillclaude

Install

agr install @gyrus-dev/snowflake-create-file-format --target claude

Writes 1 file into .claude/skills/, pinned to git-8975389b.

  • .claude/skills/snowflake-create-file-format/SKILL.md

Document


name: snowflake-create-file-format description: Consult Snowflake CREATE FILE FORMAT parameter reference before generating any CREATE FILE FORMAT DDL.

Before writing a CREATE FILE FORMAT statement:

  1. Read references/parameters.md to review all available parameters and their defaults.
  2. For each parameter, decide whether the user's request implies a non-default value.
  3. Include only the parameters that differ from the default or that the user explicitly requested — do not bloat the DDL with unnecessary clauses.
  4. Never use CREATE OR REPLACE — always use CREATE FILE FORMAT IF NOT EXISTS.
  5. Always specify the TYPE parameter explicitly, even though CSV is the default, to make the format self-documenting.
  6. For CSV formats, pay special attention to FIELD_OPTIONALLY_ENCLOSED_BY, NULL_IF, SKIP_HEADER, and COMPRESSION — these are the most commonly customized options.
  7. AVRO, ORC, and XML formats are for loading only; do not use them for unloading.
  8. Do not combine OR REPLACE and IF NOT EXISTS in the same statement — they are mutually exclusive.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-8975389b4d942026-07-31