chronicle-dataset

Upload, register, and load datasets as searchable assets linked to Chronicle experiments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires methodic-research.

What problem does it solve? Getting research datasets into an experiment-tracking platform with proper provenance, searchability, and access control is tedious and error-prone. This Skill handles uploading dataset bytes (or registering existing gs:// or s3:// data by reference), authoring searchable metadata, and linking datasets as experiment or variation inputs in Chronicle. ## Core Features & Use Cases - Dataset Upload & Sharding: Upload a single file or a directory of shards as components via presigned PUTs, with automatic sha256 and size provenance recording. - Searchable Metadata Layer: Author a metadata document (description with LaTeX, PDE family, boundary conditions, variables, properties) that is full-text and semantically indexed for discovery. - Register by Reference: Register datasets already living in GCS or S3 without moving bytes, created ready in one call. - ACL-Aware Linking: Link datasets at experiment or variation level with control over ACL propagation for sensitive data. - Use Case: You have a 13 GB turbulence simulation in a GCS bucket. Register it by reference with rich PDE metadata, link it as a variation input, and teammates can later find it via faceted search on pde_family and precision. ## Quick Start Ask the agent to upload the dataset at ./data/fields.npz to the current Chronicle experiment with a description and metadata so it is searchable.

Frequently Asked Questions about chronicle-dataset

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

FAQPage Schema
How do I upload a dataset to a Chronicle experiment?▼

Call chronicle.datasets.upload with the file or directory path, the experiment ID, and optionally a variation index to link it as an input in one call. The SDK records sha256 and size provenance per component automatically.

How do I register a dataset already in GCS or S3 without uploading?▼

Use chronicle.datasets.register_by_reference with the gs:// or s3:// URI, a name, metadata, and declared size in bytes. The dataset is created in ready state in a single call and can be linked like any uploaded dataset.

How do I make a dataset searchable in Chronicle?▼

Author a metadata document with a LaTeX-bearing description, PDE family, boundary conditions, domain, variables, and free-form properties. Chronicle full-text and semantically indexes this metadata and exposes facets like precisions and pde_family for filtered search.

Can I upload a multi-GB dataset as a single file?▼

Each component is a single presigned PUT with no multipart support. On GCS the resumable session handles large objects, but the S3 fallback caps a single PUT, so shard large datasets into a directory of files and upload the directory.

Why does linking a dataset fail with a 409 committed error?▼

Experiment and variation inputs freeze at commit time, so linking after commit is refused. Link the dataset before committing, or create a new open variation and link the dataset to it.

What permissions are needed to share a dataset via experiment link?▼

An experiment-level link with ACL propagation requires Administer on the dataset since it stamps the experiment's reader ACLs onto it. For read-only-shared or sensitive datasets, link with propagate_acl set to false.