菜单
Add a Kaggle dataset gated behind a one-time ToS click-through. Use when a Kaggle URL returns 403 from the API and the user needs the manifest+workflow pattern that documents the click-through gate cleanly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Walk through adding a new dataset to sources.json and producing its first build. Use when the user wants to onboard a new upstream source, add a slug to the manifest, or extend the catalog.
Walk through writing a new transform handler under scripts/pipeline/handlers/. Use when the default tighten_types/identity paths can't produce the right shape — row-level JSON parsing, streaming to avoid OOM, multi-output splitting, or VARIANT-from-the-start.
Load a Raincloud dataset via the lightweight Python loader API (`raincloud.load(slug)`). Use when the user wants to read a prepared parquet/vortex artifact, inspect a slug's metadata, or pull a dataset for downstream analysis from cache → mirror → local build.
Push locally-built Raincloud artifacts to a mirror (`scripts.pipeline.publish`). Use when the maintainer wants to upload one or more slugs' parquet/vortex bytes to a configured mirror after a successful build, gated on the snapshot's recorded sha256.
Use when the user asks to compute or refresh per-column statistics for a raincloud dataset — produces `outputs/v1/<slug>/profile.json` for the TUI's detail pane and `list_datasets --inspect`.
Run the full Raincloud pipeline (fetch → extract → parse → transform → write → validate → convert) for one or more dataset slugs. Use when the user asks to build a dataset, rebuild a slug, or process a batch.
基于 SOC 职业分类
| name | raincloud-add-kaggle-tos |
| description | Add a Kaggle dataset gated behind a one-time ToS click-through. Use when a Kaggle URL returns 403 from the API and the user needs the manifest+workflow pattern that documents the click-through gate cleanly. |
Guide the user through adding a Kaggle dataset that requires a one-time click-through ToS acceptance on the Kaggle web UI before the API will serve downloads. Reference: SKILLS.md "Adding a Kaggle dataset gated behind ToS acceptance".
Diagnostic note: an HTTP 403 from a Kaggle fetch can also indicate a wrong slug. Double-check the Kaggle URL before reaching for this pattern.
Steps:
Add the spec as a normal fetch.type: "kaggle" entry but mark it as gated and leave expect.rows: null:
"fetch": {
"type": "kaggle",
"urls": ["https://www.kaggle.com/datasets/<owner>/<dataset>"],
"auth": "kaggle",
"requires_interactive_accept": true,
"notes": "Kaggle gates this dataset behind a one-time click-through ToS acceptance."
},
"expect": { "rows": null, "notes": "Row count populated after the first successful build." }
Use the Python load-edit-dump pattern — never sed.
Confirm Kaggle creds are set up: ~/.kaggle/kaggle.json with chmod 600, and the project synced via uv sync --extra kaggle --inexact.
Try the first build via /raincloud-build <slug> --loose. Pre-flight will print kaggle (ToS-gated): .... Expect a 403 on the first try. The error message will point at the exact Kaggle URL the user must visit.
Tell the user to click Download once in a browser signed into Kaggle. The 403 handler is generic — it triggers whether or not requires_interactive_accept is set, so forgetting the flag still yields a useful error; the flag only improves the up-front announcement.
Re-run /raincloud-build <slug> --loose. It should succeed.
Update expect.rows in the manifest with the actual count and drop expect.notes (now that the row count is known).
Regenerate docs via /raincloud-docs.