Submit a package

Listing a package takes one name + repo entry in catalog.yaml. Your code stays in your own repository; the catalog reads its manifest and rebuilds this site daily.

1 · Describe the entry

What are you listing?

Primitives, services and skills all go under packages:.

Must match package.name in your manifest exactly.

Public repository with a root-level manifest on its default branch.

2 · Copy the YAML

packages:
  - name: robonix.service.mapping
    repo: https://github.com/syswonder/service-map-rbnx

3 · Open the pull request

GitHub forks the catalog for you and turns the edit into a pull request. Paste your entry into the matching section, keeping the list in alphabetical order.

Edit catalog.yaml on GitHub Open a request instead

Not comfortable with YAML? The second button files an issue with your details filled in, and a maintainer adds the entry.

What CI checks

  • The repository is public and has a root-level package_manifest.yaml (or robonix_manifest.yaml for a robot).
  • package.name in that manifest matches the name you submit here.
  • version, description, license, tags and maintainers are all present.
  • Maintainers are written as Name <email@domain>.
  • Every declared capability names a real Robonix contract.
  • For robots, each dependency resolves to a cataloged repository or a path inside the robot repository itself.

Manifest template

package:
  name: robonix.service.mapping
  version: 0.4.0
  description: Map and SLAM service package.
  license: MulanPSL-2.0
  tags: [service, mapping, slam]
  maintainers:
    - Your Name <you@example.com>

capabilities:
  - name: robonix/service/map/save_map
Full packaging guide