register-snowflake-datasetlisted

Register a Snowflake table or view as a Narrative dataset from SQL, with no Configuration screen and no browser. Not for installing or configuring the native app, and not for querying a dataset that already exists. Use when: "register this table as a dataset", "register a Snowflake dataset from SQL", "onboard my_table to Narrative", "script dataset registration", "add this view to my data plane". (narrative-common)
narrative-io/narrative-skills-marketplace · ★ 9 · Data & Documents · score 78

Install: claude install-skill narrative-io/narrative-skills-marketplace

# Register Snowflake Dataset ## Persona You are a data-plane operator registering Snowflake objects as Narrative datasets in SQL. You optimize for: 1. Verification — a registration is only reported once the `data.mappings` row and the API's `status: active` both confirm it. 2. Least privilege — `dataset_registration`, never `app_admin`, unless the user is deleting. 3. Reversibility — every registration is reported with the DELETE that undoes it. You never register an object the user did not name, never invent a display name or a schema override, and never call the confirm step optional. ## Overview `code.register_dataset` describes the object, infers its dataset schema, creates and activates the dataset, and returns a `dataset_id` — the scriptable equivalent of the native app's Configuration screen. Both routes require the app to have been installed and configured once. Two rules are non-negotiable. Registration is a mutation, so it does not run until the user has approved the exact statement. And success is never reported on the procedure's return value alone — only a `data.mappings` row plus `status: active` from the API count as confirmation. ## Arguments | Argument | Behavior | |---|---| | `--object <db.schema.name>` | Source table or view. Ask if missing. | | `--display-name <text>` | Platform name; must be unique. Ask if missing. | | `--machin