chronicle-register-dataset

Registers existing gs:// or s3:// datasets with searchable physics metadata in Chronicle.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/methodic-research/skills --skill chronicle-register-dataset-methodic-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chronicle-register-dataset
Source: https://github.com/methodic-research/skills/tree/main/plugins/chronicle/skills/chronicle-register-dataset
Command: npx skills add https://github.com/methodic-research/skills --skill chronicle-register-dataset-methodic-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large scientific datasets often already live in cloud buckets (gs:// or s3://) and never pass through an upload pipeline, leaving them invisible to catalog search. This Skill registers those datasets by reference in the Chronicle platform and authors the rich, math-bearing metadata layer (PDE, boundary conditions, domain geometry, per-variable shapes and dtypes) that makes them describable, filterable, and searchable. ## Core Features & Use Cases - Register by reference: Create a ready dataset asset from an existing gs:// or s3:// URI in a single MCP call, with no byte upload, presign, or finalize steps. - Author and patch metadata: Write a long LaTeX-bearing description, PDE family and equation, boundary/initial conditions, domain geometry, a per-variable table, and free-form key=value properties; update the mutable metadata layer later without minting a new asset. - List and filter the catalog: Run Postgres-side filtered listing on promoted facets such as n_dims, precision, pde_family, geometry, and size. - Use case: A researcher has a 256^3 Navier-Stokes DNS corpus in a GCS bucket and wants teammates to find it by searching "3D incompressible Navier-Stokes, periodic box, fp64" — this Skill registers the URI and authors exactly that metadata. ## Quick Start Ask the agent to register the dataset already stored at your gs:// bucket URI as a searchable Chronicle dataset with a description of its PDE, boundary conditions, and variables.

Frequently Asked Questions about chronicle-register-dataset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register a dataset that already exists in a GCS or S3 bucket?▼

Call chronicle.register_dataset with the existing gs:// or s3:// URI plus a metadata document containing at least a description. The asset is created ready in one call with no presign, upload, or finalize steps, since the bytes already live in the bucket.

What metadata makes a scientific dataset searchable in a catalog?▼

Author a long Markdown and LaTeX description of the governing PDE, plus curated facets like pde.family, boundary_conditions, domain geometry and resolution, and a per-variable table with shape, dtype, and units. Free-form key=value properties become exact-match search facets without schema changes.

Can I fix wrong dataset metadata after registration?▼

Yes, the metadata layer is a mutable annotation updated via chronicle.update_dataset_metadata with the asset id and a partial or full metadata document. The bytes, URI, and checksum stay immutable; only the descriptive layer, promoted columns, and search projection are refreshed, requiring Write permission on the asset.

When should I use register-by-reference instead of uploading a dataset?▼

Use register-by-reference when the bytes already exist at a gs:// or s3:// URI, including foreign or BYOB buckets Chronicle cannot write to. If the data is a local file or directory, use the chronicle-dataset skill instead, which moves bytes via presigned upload.

Does registering a dataset require installing the Python SDK?▼

No, registration, metadata updates, and catalog listing use the bundled MCP tools directly with credentials resolved from ~/.methodic. The optional methodic-research SDK is only needed for SDK-only paths like large multi-file uploads.

Why does dataset registration fail with an invalid URI error?▼

The URI must point to an existing gs:// or s3:// location because register-by-reference never creates bytes. Upload the data first with the chronicle-dataset skill if it does not exist yet, then register the resulting URI.