菜单
Static checks for sources.json — JSON Schema shape + cross-checks (handler registry, slug uniqueness, fetch.type/auth consistency). Use after any manifest edit, before triggering a build, or whenever an agent wants a sub-second sanity check that the manifest is well-formed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | raincloud-validate-manifest |
| description | Static checks for sources.json — JSON Schema shape + cross-checks (handler registry, slug uniqueness, fetch.type/auth consistency). Use after any manifest edit, before triggering a build, or whenever an agent wants a sub-second sanity check that the manifest is well-formed. |
Run the manifest validator:
python -m scripts.pipeline.validate_manifest $ARGUMENTS
What it checks:
sources.schema.json (Draft 2020-12). Requires the jsonschema package; pinned in pyproject.toml. Skipped with a hint if missing.datasets[].transform.handler resolves in scripts/pipeline/handlers/__init__.py:_REGISTRY.fetch.urls non-empty unless fetch.type == "custom".fetch.auth matches fetch.type for kaggle / huggingface.fetch.requires_interactive_accept only on fetch.type == "kaggle".write.output filename agrees with slug for single-output handlers (warning otherwise — multi-output handlers legitimately diverge).Modifiers:
--json — machine-readable report ({ok, n_datasets, errors, warnings, schema_skipped}).--strict — treat warnings as errors. Useful in CI-style gating.Exit code: 0 on success (warnings allowed), 1 on errors.
When to invoke:
sources.json (especially handler renames, license changes, slug additions)./raincloud-build on a fresh slug — catches typo'd handler names without paying for a fetch./raincloud-status: /raincloud-status reports filesystem state, /raincloud-validate-manifest reports manifest correctness.Context: AGENTS.md "Safe ways to edit sources.json", sources.schema.md, sources.schema.json.