Skip to content
rd-skills
Documentation

Authoring skills

Marketplace Index

The marketplace index and catalog are local, source-derived discovery views.

docs/MARKETPLACE.md

The marketplace index and catalog are local, source-derived discovery views. They are not a separate package format, duplicated registry, user-specific toolbox, or official marketplace publication.

Find Skills

  1. Open the generated Marketplace Catalog.
  2. Start with a Professional Skill when looking for complete engineering judgment and a stable Primary Route.
  3. Use Foundation and Domain entries only to understand selector-owned Layer 3 coverage. Their presence in the catalog does not make them Host top-level Skills and does not authorize catalog preloading.
  4. Confirm routing and installation behavior in the source registries and generated Runtime manifest. The catalog is not their authority.

Marketplace schema v3 is fail-closed. Every item carries explicit task_routable metadata: a boolean for Professional Skills and null for all other layers. Consumers must reject older payloads rather than infer that field. The payload retains profile: recommended only as fixed compatibility metadata.

Layers

TypeRuntime delivery
Control Skilltop-level; one entry
Professional Skilltop-level; 25 Primary Route owners
product Foundation Skillcapability modifier, compiled only behind a Professional selector
authoring-only / internal Foundation Skillsource and routing-validation metadata only
Domain Skillmodifier-only, compiled only behind a Professional selector

Foundation and Domain items never enter Host top-level discovery, installation, or top-level OpenAI zip packaging. The fixed flow is Primary Professional, selector, zero to three JIT Layer 3 items, then only required References.

Source Fields

Every registry entry provides:

  • name and source path;
  • Foundation source delivery_scope;
  • Domain routing_mode: modifier-only and Professional owners;
  • Professional task_routable as an explicit boolean;
  • role_support;
  • trigger, boundary, and anti-trigger signals as applicable;
  • required inputs and output contracts, including role maps where required;
  • escalation signals;
  • structured Reference Contract v2 entries.

Professional entries name Layer 3 candidates, but a concrete selector signal decides which candidate is loaded. Product Foundation and every Domain owner mapping must agree with the Professional registry. Task and Review agents consume Main's fixed Primary Route; neither reruns global routing.

Export And Validate

python3 scripts/export-marketplace-index.py --out /tmp/rd-skills-marketplace-index.json
python3 scripts/generate-marketplace-catalog.py --out docs/MARKETPLACE_CATALOG.md
python3 scripts/validate-marketplace-index.py

The exporter reads the four source registries and matches the one Runtime contract. The catalog must be regenerated by its producer; do not hand-edit it or use it to claim external availability.