Skills, signed knowledge and deterministic checks for Earth science, installed as plugins into Claude Code and Claude Cowork. Each capability is procedures an agent can run, facts about data signed by the people who steward it, and checks that emit receipts with no language model in the path. A personal open-source project; not a NASA, JPL, or PO.DAAC product.
Claude Code:
claude plugin marketplace add open-science-pillars/marketplace
claude plugin install ocean-science@open-science-pillarsClaude Cowork: from Customize > Plugins > Add marketplace, add the
marketplace by repository, open-science-pillars/marketplace; install
the capability you want from it. It is the same plugin, and it brings
its dependencies (the foundation and the provider knowledge) with it.
Available: core, ocean-science, nasa-daac-knowledge. Developing: hydrology, land-ice, atmospheric-physics, each with a release you can install. Nine sphere repositories are planned and not installable.
A Pillar is a sphere. A domain capability is a discipline inside one;
provider knowledge is signed by its stewards and serves every sphere;
planned means visible and not installable.
Rendered by build-kit's osp.py sphere-view --into from every repository's
.osp/repository.yaml; edit the files, not this block.
Atmosphere
- atmospheric-composition (planned): Atmospheric Composition
- atmospheric-physics (developing): Atmospheric Physics
Biosphere
- land-ecosystems (planned): Land Ecosystems
- ocean-biology (planned): Ocean Biology
Cryosphere
Geosphere
- land-surface (planned): Land Surface
- solid-earth (planned): Solid Earth
Hydrosphere
- hydrology (developing): Terrestrial Hydrology; also Cryosphere
- ocean-science (available): Ocean Physics
- precipitation (planned): Precipitation Science; also Atmosphere
Provider knowledge (signed by its stewards; cuts across spheres)
- nasa-daac-knowledge (available): Provider knowledge bundles (PO.DAAC, ESDIS, NSIDC, GES DISC, ASDC, OB.DAAC, LP DAAC, ORNL DAAC), signed by their stewards; installed as a dependency of the domain capabilities
- partner-knowledge (planned): Provider knowledge from non-NASA stewards, signed by them; none engaged yet
Composites (cross-sphere)
- composites (planned): Cross-sphere composites, each with its own steward, joint knowledge and validation; none yet
Foundation and tooling (serve every sphere)
- .github (available): Organization profile, issue and pull request templates, governance
- agent-evals (available): The organization's one benchmark repository; each product's cases, fixtures and results under its own directory (ecco/ first), governed by one charter
- archive-observatory (available): Data engineers and archive operators: metadata compliance instruments, classified on their own terms rather than by sphere
- build-kit (available): Maintainers: the development harness, the roadmap and the metadata tooling
- core (available): The foundation capability every domain capability depends on
- evals (available): Eval runner, graders, suite manifests and the scoreboard
- knowledge-template (available): Template: a copy renames repository.name before it validates
- marketplace (available): The plugin catalog and the canonical documentation
- plugin-template (available): Template: a copy renames repository.name (and package.yaml) before it validates
- tutorials (available): Timed walkthroughs and the browser demo
A capability is four kinds of thing: knowledge bundles, skills, deterministic checks and connectors; the glossary defines each of them, and every other term, in plain language.
New here? The tutorials are timed and fresh-install-tested (10, 20, and 30 minute tracks), and the demo folder has a browser-runnable companion. The marketplace README is the catalog: what is available, how to update, and the documentation map. Contributing starts at CONTRIBUTING; who reviews what, and how decisions are taken, is in GOVERNANCE (lazy consensus with owning teams, DCO sign-off on every commit).
Questions: GitHub Discussions on the marketplace repo.