메뉴
Use when browsing, querying, or reasoning about what datasets exist in a STAC catalog — especially before concluding a dataset is missing or absent. Triggers include STAC browser URLs, s3 stac-collection.json links, or any question about what data is available in a catalog.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | stac-navigation |
| description | Use when browsing, querying, or reasoning about what datasets exist in a STAC catalog — especially before concluding a dataset is missing or absent. Triggers include STAC browser URLs, s3 stac-collection.json links, or any question about what data is available in a catalog. |
Never conclude a dataset is missing until you have walked the full tree from the root catalog down.
Stopping at a sub-collection and declaring something absent is the primary failure mode.
The STAC Browser URL encodes the underlying JSON endpoint:
https://radiantearth.github.io/stac-browser/#/external/<S3-URL>
Fetch the <S3-URL> part directly. Example:
Browser URL: https://radiantearth.github.io/stac-browser/#/external/s3-west.nrp-nautilus.io/public-data/stac/catalog.json
Fetch: https://s3-west.nrp-nautilus.io/public-data/stac/catalog.json
1. Fetch ROOT catalog first
→ Walk ALL child links
→ Then walk into sub-collections as needed
2. If given a sub-collection URL, ALSO fetch its parent link
→ Never reason from a sub-collection alone
A dataset may be a child of the root catalog but NOT linked from a sub-collection — both are valid locations.
https://s3-west.nrp-nautilus.io/public-data/stac/catalog.jsonpublic-high-seas/stac-collection.json (child of root)Each STAC JSON has a links array. Relevant rel values:
| rel | Meaning |
|---|---|
root | Top-level catalog — always fetch this first |
parent | Walk up if you started mid-tree |
child | Walk down to find datasets |
item | Leaf-level data asset |
"The high-seas sub-collection only shows 4 datasets, so the others must be missing."
Wrong. The root catalog may link those datasets directly. Always check the root.
Map of the boettiger-lab data-and-agent stack — which GitHub repo owns which piece of the data → STAC → MCP → LLM-agent chain. Use when unsure which repo to edit for a given problem, when routing cross-repo issues, or when the root cause could plausibly be in more than one layer.
Manage S3 object storage on the NRP (National Research Platform) Nautilus cluster, which uses Ceph S3 (not AWS). Covers public vs internal endpoints, rclone usage, bucket creation, public-read policies, CORS configuration, credential handling, and syncing to source.coop. Use when working with S3 buckets on NRP Nautilus, uploading or downloading data, configuring bucket access, or syncing datasets to source.coop.
Use when storing, versioning, or sharing large files alongside a GitHub repo — model checkpoints, datasets, build artifacts, binaries, fixtures — and you want collaborators to use their GitHub access rather than separate cloud credentials. Covers ghcr.io, oras CLI, content-addressing, public/private access, and the tradeoffs vs git-lfs, S3 buckets, and GitHub Releases.
Analyze geo-agent app behavior from LLM proxy and MCP server logs, identify inefficiencies, and trace root causes to the correct layer: STAC metadata, MCP tool descriptions, geo-agent framework, or app system prompt. TRIGGER when: reviewing agent behavior, analyzing LLM logs, improving system prompts based on observed failures, debugging tool-use loops, or optimizing query patterns in geo-agent apps.
Deploy and manage workloads on the NRP Nautilus Kubernetes cluster. Covers batch jobs (opportunistic priority class, resource requests, GPU node avoidance), ingress with HAProxy CORS and timeout annotations, NRP usage policies, and credential wiring. TRIGGER when the user mentions: kubectl, k8s, kubernetes, NRP, Nautilus, rollout, restart deployment, apply yaml, pod, job, namespace, ingress, or any cluster operation. Namespace is 'biodiversity'. Always load this skill BEFORE running any kubectl command.
Apply preferred branch-protection rulesets and squash-merge-only settings to GitHub repos. Two profiles: 'standard' (no approval required) for smaller projects and 'strict' (1 approval, dismiss stale reviews) for larger ones. TRIGGER when: setting up a new repo, applying branch protection, configuring merge settings, or the user mentions rulesets.