Virtual Icechunk · IOOS Hackathon 2026
The skill does the building; you supply what it cannot know
| Step | You get | It must |
|---|---|---|
| 1 · Plan | plan.md: files, layout, decisions |
Be reviewed by you before any code |
| 2 · Smoke test | A notebook that builds a local store from a few files | Reopen it read-only and read real values |
| 3 · Production | A build script: settings at the top, batches, commits, restart | Survive being interrupted; tag the result |
| 4 · Docs | A README, a loading example, the tested environment | Let a stranger open the store with no help |
It stops for your review between steps.
It cannot guess these. Put them in your first prompt:
It will propose these, and ask you to confirm:
The files usually decide these. You can still ask “why?”, and override.
“Build a virtual Icechunk store of the NDVI files in
s3://noaa-cdr-ndvi-pds/data/(public, us-east-1) for 2000–2024. Publish it to my Source Cooperative repositorymy-org/ndvi; my write keys are in environment variables. Python users and a browser viewer will read it. Start with the plan.”
Then, one session per step:
“The plan is approved. Write the smoke-test notebook.” (builds a local test store)
“The smoke test passed. Write the production build script.” (writes to your bucket)
“Write the README and a loading example.”
The agent writes to your bucket with your credentials. Tell it where they are:
| Destination | Typical credentials |
|---|---|
| Amazon S3 | An AWS profile, or AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in the environment |
| Google Cloud Storage | A service-account key file, named in GOOGLE_APPLICATION_CREDENTIALS |
| Source Cooperative | Temporary S3 keys from your repository’s View credentials page. They expire |
Not sure? Ask it:
“Help me set up write access to my Source Cooperative repository. Do not print my keys, and do not save them in any file in this repository.”
⌂ Home · Building a virtual Icechunk store