agentleFS
isaaccorleyisaaccorley/geospatial-skills/skills/register-catalog/SKILL.md

register-catalog

Skill78 starsChanged 8 months agoApache-2.0View on GitHub

Register a Portolan catalog in the Portolan registry by opening a pull request that adds a catalog entry file.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the URL doesn't end in catalog.json, isn't reachable, or isn't a catalog root, stop and tell the user.

    line 36
  2. Very specific:

    Use gh to fork (if needed), branch, add the file, and open the PR — all without leaving the working directory:

    line 52
  3. Very specific:

    If the user prefers not to use GitHub, they can submit the same catalog.json URL through the web form at portolan-sdi.org.

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- freshness: last-verified: 2026-06-12, maps-to: portolan-sdi/portolan-registry -->

Register a Catalog in the Portolan Registry

You are helping a user add their Portolan catalog to the portolan-registry by opening a pull request. The registry crawls and validates submitted catalogs, then exports their metadata. (Portolan uses STAC to organize its catalog.json, but a Portolan catalog is its own thing — don't call it a STAC catalog.)

Key fact: submitters provide only the URL

A registry entry is a single YAML file with one field:

url: https://example.com/stac/catalog.json

CI auto-extracts everything else (title, description, bbox, license, counts, etc.) by crawling the catalog. Never add other fields or invent metadata — the schema forbids it (additionalProperties: false).

Step 1: Validate the catalog URL

The URL must end in catalog.json and point to a reachable Portolan catalog root.

curl -fsSL "$CATALOG_URL" | python3 -c "
import sys, json
c = json.load(sys.stdin)
assert c.get('type') == 'Catalog', f\"not a catalog root (type={c.get('type')})\"
print('OK:', c.get('id'), '-', c.get('title', '(no title)'))
"

If the URL doesn't end in catalog.json, isn't reachable, or isn't a catalog root, stop and tell the user. Do not proceed with an invalid entry.

Step 2: Derive the slug

The slug is the directory that contains catalog.json — the last path segment before the filename. No need to invent one.

# .../source-coop/nlebovits/ide-pergamino/catalog.json  ->  ide-pergamino
SLUG=$(basename "$(dirname "$CATALOG_URL")")
echo "$SLUG"

The file will be catalogs/$SLUG.yaml.

Step 3: Open the PR

Use gh to fork (if needed), branch, add the file, and open the PR — all without leaving the working directory:

# CATALOG_URL and SLUG carry over from the steps above

# Fork (no-op if already forked) and clone to a temp dir
TMP=$(mktemp -d)
gh repo fork portolan-sdi/portolan-registry \
  --clone "$TMP/portolan-registry" --remote
cd "$TMP/portolan-registry"

# Create the entry on a new branch
git checkout -b "add-$SLUG"
printf 'url: %s\n' "$CATALOG_URL" > "catalogs/$SLUG.yaml"
git add "catalogs/$SLUG.yaml"
git commit -m "Add $SLUG catalog"
git push -u origin "add-$SLUG"

# Open the PR against the upstream repo
gh pr create \
  --repo portolan-sdi/portolan-registry \
  --title "Add $SLUG catalog" \
  --body "Registers \`$CATALOG_URL\` in the Portolan registry."

Step 4: Report

Give the user the PR URL (printed by gh pr create) and explain that CI will crawl and validate the catalog, then export its metadata to exports/catalogs.json once merged.

Alternative: web submission

If the user prefers not to use GitHub, they can submit the same catalog.json URL through the web form at portolan-sdi.org.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.