Agent skill

Snowflake Failover Readiness Drill

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or…

MITAuto-check passedDatabases

Install Snowflake Failover Readiness Drill

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill snowflake-failover-readiness-drill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace snowflake-failover-readiness-drill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/snowflake-failover-readiness-drill .claude/skills/snowflake-failover-readiness-drill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
snowflake-failover-readiness-drill
GitHub stars
2.8k
Token cost
~2.1k tokens
SKILL.md length
771 words
Files
11 (incl. scripts, references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or…

  • Works in 4 steps: Have the recovery owner approve an exact… → Collect replication-current in both… → Build the exact schema-2 wrapper in → …
  • An owner needs a Business Critical disaster-recovery preflight
  • SKILL.md covers Purpose, Prerequisites, Workflow and Collection pattern, plus 6 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Snowflake Failover Readiness Drill is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or session changes. Use when an owner needs a Business Critical disaster-recovery preflight, replication failure diagnosis, dangling-reference check, or operator-executed drill proof. Trigger with "Snowflake failover drill", "replication RPO", "failback proof", or "secondary refresh".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `eval-spec.yaml`, `references/evidence-contract.md` and `references/source-notes.md`). Compatibility notes: Model-agnostic workflow; requires Python 3.10+; optional Snowflake CLI for live read-only evidence collection

It sits in Databases, covering Backup and disaster recovery and Data warehousing. It works with Snowflake. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • An owner needs a Business Critical disaster-recovery preflight
  • Replication failure diagnosis
  • Dangling-reference check
  • Operator-executed drill proof

Example prompts

  • “Snowflake failover drill”
  • “replication RPO”
  • “failback proof”
  • “/snowflake-failover-readiness-drill”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Model-agnostic workflow; requires Python 3.10+; optional Snowflake CLI for live read-only evidence collection
  • Pre-approved tools (allowed-tools): Read, Bash(python3:*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Have the recovery owner approve an exact policy containing every in-scope
  2. Collect replication-current in both source and target accounts. Collect
  3. Build the exact schema-2 wrapper in
  4. Run the analyzer; it writes only to stdout

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash(python3:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 7 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Model-agnostic workflow; requires Python 3.10+; optional Snowflake CLI for live read-only evidence collection

    From compatibility in the SKILL.md frontmatter.

Context cost

Snowflake Failover Readiness Drill loads about 2.1k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 771 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 771 words, ~2,074 tokens.

Download SKILL.mdSave it as .claude/skills/snowflake-failover-readiness-drill/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
snowflake-failover-readiness-drill
description
Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or session changes. Use when an owner needs a Business Critical disaster-recovery preflight, replication failure diagnosis, dangling-reference check, or operator-executed drill proof. Trigger with "Snowflake failover drill", "replication RPO", "failback proof", or "secondary refresh".
allowed-tools
Read, Bash(python3:*)
compatibility
Model-agnostic workflow; requires Python 3.10+; optional Snowflake CLI for live read-only evidence collection
argument-hint
[schema-2-evidence.json]
version
3.16.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, snowflake, disaster-recovery, failover, replication, rpo, rto

Snowflake Failover Readiness Drill

Purpose

Produces a deterministic readiness or attestation result from exact, independently trusted evidence. It observes and verifies but never performs or authorizes a Snowflake control-plane change.

Prerequisites

  • Python 3.10+ and this complete skill directory, including its reviewed SQL.
  • An owner-approved scope and separately retained digests for policy, collection, and operator/validation evidence.
  • Existing least-privilege Snowflake CLI profiles in source and target accounts when live collection is required. Profiles used for Information Schema history, progress, or dangling functions must select an approved current database; the skill does not configure authentication or session state.
  • Business Critical Edition or higher for failover groups.

Workflow

  1. Have the recovery owner approve an exact policy containing every in-scope group, dependency, validation, RPO, and RTO. Record its digest at a trusted boundary before evidence is transported.

  2. Collect replication-current in both source and target accounts. Collect replication and replication-progress in each target account over the same current, explicit half-open UTC window. A full failback drill also requires both surfaces in the original source account to prove the reverse refresh leg. Collect replication-dangling in both accounts for every in-scope local group.

  3. Build the exact schema-2 wrapper in references/evidence-contract.md. Record independent digests for the collector bundle, policy, and operator/validation receipts. A digest recomputed from the delivered file is not independent.

  4. Run the analyzer; it writes only to stdout:

    bash
    python3 "${CLAUDE_SKILL_DIR}/scripts/analyze_failover_readiness.py" \
      --input ./snowflake-failover-evidence.json \
      --evaluated-at "$EVALUATED_AT_UTC" \
      --trusted-input-sha256 sha256:... \
      --trusted-policy-sha256 sha256:... \
      --trusted-operator-sha256 sha256:... \
      > ./snowflake-failover-report.json

An INCONCLUSIVE or NOT_READY exit is 1; malformed input exits 2.

Collection pattern

Use an existing least-privilege Snowflake CLI profile. Never pass credentials to the collector and never switch to ACCOUNTADMIN because evidence is missing.

bash
python3 "${CLAUDE_SKILL_DIR}/scripts/collect_snowflake_evidence.py" \
  --surface replication-current --connection source-observer \
  --output ./source-current.json

python3 "${CLAUDE_SKILL_DIR}/scripts/collect_snowflake_evidence.py" \
  --surface replication --connection target-observer \
  --window-start "$WINDOW_START_UTC" --window-end "$WINDOW_END_UTC" \
  --output ./target-history.json

python3 "${CLAUDE_SKILL_DIR}/scripts/collect_snowflake_evidence.py" \
  --surface replication-progress --connection target-observer \
  --window-start "$WINDOW_START_UTC" --window-end "$WINDOW_END_UTC" \
  --output ./target-progress.json

python3 "${CLAUDE_SKILL_DIR}/scripts/collect_snowflake_evidence.py" \
  --surface replication-dangling --connection source-observer \
  --replication-group DR_CORE --output ./source-dangling.json

The group selector is validated locally and hashed inside Snowflake. Raw account, group, role, owner, object, and dependency identifiers are not emitted. Every receipt is live-only schema 2, no older than 15 minutes at evaluation, capped at 5,000 rows, and invalid if the cap is reached. History/progress window ends must be at or before and within 60 seconds of collection start, no more than 15 minutes behind evaluation, and identical for the paired receipts in an account.

Modes and proof

  • PREFLIGHT: one current snapshot per source and target account, no operator events, and passing PRE_FAILOVER validations. A clean result is only READY_FOR_OPERATOR_DRILL_AS_OF.
  • FAILOVER_ATTESTATION: before/after current snapshots, one successful scoped failover receipt per group, and passing pre/post validations. A clean result is FAILOVER_ATTESTED_AS_OF.
  • FULL_DRILL_ATTESTATION: before/middle/after current snapshots, ordered successful failover then failback receipts, and passing validations at all three stages. A clean result is FULL_DRILL_ATTESTED_AS_OF.

RPO age is evaluated_at - PRIMARY_SNAPSHOT_TIMESTAMP from the latest refresh job for preflight, or transition_started_at - PRIMARY_SNAPSHOT_TIMESTAMP for each directional drill leg, only when that job has exactly one COMPLETED terminal phase and exactly one snapshot timestamp. Refresh end time, schedule time, and login success are never substitutes. RTO comes only from trusted operator event start/completion times.

Show full SKILL.md (312 more words)Show less

Non-negotiable safety boundary

  • Never run refresh, promotion, failover, failback, redirect, suspend/resume, cancel/abort, role switching, or session mutation.
  • Never treat a self-checksum as provenance. Require all three separately supplied trusted digests.
  • Never shrink a denominator after collection. Exact group, dependency, and validation counts are part of policy.
  • Never treat missing, stale, permission-filtered, malformed, duplicated, or capped evidence as healthy.
  • Never echo attacker-controlled raw identifiers or provider messages. Findings expose finite codes and hashed scopes only.
  • Keep every actual transition in a separately approved human change window.

References

Use the Read tool to inspect both references before evaluating production evidence; they are part of the contract, not optional background.

Output

The analyzer emits one JSON report to stdout with the overall status, integrity and coverage states, finite findings, RPO results, the three computed trust digests, admitted receipt hashes, conservative non-claims, and a deterministic report digest. It never copies collector, operator, or validation rows into the report.

Error handling

Stop and recollect on schema, digest, freshness, source, query-template, row, count, cap, selector, or authorization-context errors. Stop on a failed/canceled latest refresh, incomplete progress, RPO/RTO breach, suspended/unconfigured secondary schedule, blocking dangling reference, missing dependency ordering proof, stale validation, failed validation, unrestored final-secondary schedule, or unproved transition. A warning-only nonblocking dangling reference yields AT_RISK; it is never silently accepted.

Examples

  • A snapshot exactly 3,600 seconds old against a 3,600-second RPO passes; one second older yields RPO_BREACH and NOT_READY.
  • A recent successful refresh does not override a newer failed job or incomplete progress; the latest refresh remains unproved.
  • A caller-authored SUCCEEDED event with a recomputed self-hash cannot produce an attested result when the independent operator digest does not match.
  • A complete preflight produces READY_FOR_OPERATOR_DRILL_AS_OF, never FULL_DRILL_ATTESTED_AS_OF; that requires ordered operator failover and failback receipts plus before/middle/after state observations and passing validations.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (scripts, references) in skills/.curated/snowflake-failover-readiness-drill of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • eval-spec.yaml
  • references/evidence-contract.md
  • references/source-notes.md
  • scripts/analyze_failover_readiness.py
  • scripts/collect_snowflake_evidence.py
  • scripts/sql/replication-current.sql
  • scripts/sql/replication-dangling.sql
  • scripts/sql/replication-progress.sql
  • scripts/sql/replication.sql
  • scripts/test_analyze_failover_readiness.py

Open the folder on GitHubat commit cfae287

Compare with similar skills

Snowflake Failover Readiness Drill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Snowflake Failover Readiness Drill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Snowflake Failover Readiness Drill this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: PassMIT
Breach Patternsbriiirussell/cybersecurity-skills413—~3.5kAutomated safety check: NotesMIT
Caspian DiscordTryCaspian/caspian-sdk973—~323Automated safety check: PassApache-2.0
Simplywallstgauss314/skills248—~2.9kAutomated safety check: PassMIT
Write Script Snowflakewindmill-labs/windmill18k—~2.2kAutomated safety check: PassCustom licence
Pure Lsp Execute Parallelfinos/legend-engine113—~927Automated safety check: PassApache-2.0

Similar skills

  • Breach Patterns

    briiirussell/cybersecurity-skills

    Learn from public breach disclosures — extract the audit question each one implies and check your own stack.

    413 GitHub stars~3.5k tokensUpdated 4 mo ago
    DatabasesAuto-check: notes
  • Caspian Discord

    TryCaspian/caspian-sdk

    Post a Discord message via Caspian to a channel snowflake id.

    973 GitHub stars~323 tokensUpdated 1 mo ago
    DatabasesAuto-check passed
  • Simplywallst

    gauss314/skills

    Data financiera de 120K+ stocks globales: snowflake scores, valuation, financial health, dividend analysis, insider transactions.

    248 GitHub stars~2.9k tokensUpdated 3 mo ago
    DatabasesAuto-check passed
  • Write Script Snowflake

    windmill-labs/windmill

    MUST use when writing Snowflake queries. An agent skill from windmill-labs/windmill.

    18k GitHub stars~2.2k tokensUpdated today
    DatabasesAuto-check passed
  • Pure Lsp Execute Parallel

    finos/legend-engine

    Runs 2 to 30 Pure functions or tests concurrently on the warm LSP daemon via pure-lsp execute-parallel, or every test in a package or .pure file with --package/--source.

    113 GitHub stars~927 tokensUpdated yesterday
    DatabasesAuto-check passed
  • Plot Structure

    danjdewhurst/story-skills

    This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "sagging middle", "act structure"…

    286 GitHub starsUsed in 1 repo~4k tokens
    DatabasesAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Questions about Snowflake Failover Readiness Drill

What does Snowflake Failover Readiness Drill do?

Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or…. Snowflake Failover Readiness Drill is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze Snowflake failover-group RPO/RTO readiness from independently trusted, privacy-preserving live receipts without executing refresh, failover, failback, redirect, cancellation, resume, or session changes.

When should I use Snowflake Failover Readiness Drill?

Snowflake Failover Readiness Drill fits situations like: an owner needs a Business Critical disaster-recovery preflight; replication failure diagnosis; dangling-reference check; operator-executed drill proof.

How do I install Snowflake Failover Readiness Drill in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill snowflake-failover-readiness-drill -a claude-code`. Or copy the skill folder (skills/.curated/snowflake-failover-readiness-drill in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/snowflake-failover-readiness-drill in your project. Claude Code loads it when a task matches its description.

How do I install Snowflake Failover Readiness Drill in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill snowflake-failover-readiness-drill -a codex`. Or copy the skill folder (skills/.curated/snowflake-failover-readiness-drill in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/snowflake-failover-readiness-drill in your project. Codex loads it when a task matches its description.

Can I use Snowflake Failover Readiness Drill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill snowflake-failover-readiness-drill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/snowflake-failover-readiness-drill, .gemini/skills/snowflake-failover-readiness-drill, .github/skills/snowflake-failover-readiness-drill and .opencode/skills/snowflake-failover-readiness-drill in your project.

What does Snowflake Failover Readiness Drill need to run?

Going by SKILL.md and its folder, Snowflake Failover Readiness Drill needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash(python3:*). Compatibility (from SKILL.md): Model-agnostic workflow; requires Python 3.10+; optional Snowflake CLI for live read-only evidence collection.

Does Snowflake Failover Readiness Drill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Snowflake Failover Readiness Drill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Snowflake Failover Readiness Drill use?

Snowflake Failover Readiness Drill is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Snowflake Failover Readiness Drill use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.7k tokens, read only when the agent opens those files.

What are the alternatives to Snowflake Failover Readiness Drill?

Skills that share tags, products or a category with Snowflake Failover Readiness Drill: Breach Patterns (briiirussell/cybersecurity-skills, 413 stars), Caspian Discord (TryCaspian/caspian-sdk, 973 stars), Simplywallst (gauss314/skills, 248 stars) and Write Script Snowflake (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Snowflake Failover Readiness Drill?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.