snowflake-smoke-test
Skill from oracle-samples/oracle-aidp-samples
Install
npx skills add oracle-samples/oracle-aidp-samples --skill snowflake-smoke-test
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install oracle-ai-data-platform-workbench-spark-connectors@claude-plugins-official
This skill is part of the plugin “oracle-ai-data-platform-workbench-spark-connectors”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the snowflake-smoke-test skill do?
Description from the SKILL.md in the source repository.
Questions about snowflake-smoke-test
What does the snowflake-smoke-test skill do?
Check connectivity and permissions on both ends before any migration work. Verifies Snowflake is reachable and readable (list databases, read INFORMATION_SCHEMA) and, when AIDP coordinates are supplied, that the target catalog is readable and optionally writable. Use before the first assessment, when credentials change, or whenever a stage fails with an authorization error and you need to know which end is at fault.
How do I install snowflake-smoke-test?
In a terminal: npx skills add oracle-samples/oracle-aidp-samples --skill snowflake-smoke-test. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use snowflake-smoke-test?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is snowflake-smoke-test safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from oracle-samples/oracle-aidp-samples
Use this Oracle Analytics domain skill when creating or editing Oracle Analytics Cloud workbooks, visualizations, calculations, filters, layouts, governed analyses, or when routing an analytics request to a more specific nested skill.
Parse and summarize the JOB_REPORT.md produced by a prior migration run. Surfaces cell pass/fail/fix counts per task, lists the failing cells, and recommends a next-step skill (fixup-cell, resume, or all-clear). Use after any aidp-migrate-job run, or when the user asks "how did the migration go", "what failed", "did it pass".
Review a migrated .ipynb for correctness — NOT just "did it run". Catches latent issues the cell-execute loop missed — wrong write-mode, lost rows, dropped columns, hardcoded paths, dead Databricks-isms, builtins shadowing, format downgrades. Outputs a structured Blockers / Important / Style / Good review report. Use after aidp-migrate-job completes, especially on the first few notebooks of a new workload before scaling out.
Guided full-job migration flow. Walks the user from "I want to migrate this Databricks job" through DAG → data check → migrate → status, asking before each phase. Composes aidp-build-dag, aidp-check-data, aidp-migrate-job, and migration-status. Use when the user wants the end-to-end guided experience instead of running individual phases manually.
Guided catalog migration flow. Extracts Databricks Unity Catalog / HMS metadata, previews the 18-rule DDL rewrite, then batched replay on AIDP. Asks before the destructive replay step. Use when the user wants to migrate the catalog layer (schemas + tables) with checkpoints, rather than running aidp-migrate-catalog directly.
Read a single Databricks notebook (.ipynb / .py / .scala source format) and produce a migration-readiness report — what it does, what it depends on, what risks the migrator will hit, which gotchas (from references/gotchas.md) will apply. Run before manually authoring an entry in a migration manifest, OR as a one-off "should we migrate this?" assessment. Read-only — does not modify the notebook and does not invoke the migrator.
Pre-migration data-availability scan. Reads a migration manifest, probes every spark.read.* / saveAsTable target on the AIDP cluster, reports OK / MISSING / EMPTY with remediation tips per category. Use before any aidp-migrate-job run, or whenever the user asks "is the data ready?", "pre-migration check", "what's missing on AIDP".
Consume an OCI Streaming stream from an AIDP notebook via Spark structured streaming (Kafka-compat). Use when the user mentions OCI Streaming, Kafka on OCI, stream pool, structured streaming, or wants to read Kafka messages into Spark. Auth is SASL/PLAIN with an OCI auth token. Pattern matches the official Oracle AIDP sample.
Related skills in Testing & QA
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Build and verify an NVIDIA PVA operator with the public PVA SDK. Use alone or from OpGen. Run optional EMU correctness, a fresh L4T build with the NVVPU or ASIP/Chess backend that Doctor proved, direct-SSH Tegra hardware correctness, and optional hardware performance. Return PASSED, FAILED, or BLOCKED with exact evidence.
Run Megatron-LM (MLM) and Megatron Bridge training with mock or real data. Covers correlation testing, available recipes, and multi-GPU examples.