Skip to main content
Use registry__get_related_artifacts when you already know an artifact handle and need to see what it depends on, what follows it, its alternatives, and the artifacts that point back to it.
  • Inputs: required artifact_id; optional session_id; plus rationale when Gateway enables it.
  • Handle format: <kind>_<identifier>, such as skill_....
  • Returns: the artifact’s typed relationships in both directions. A readable end carries the artifact’s name, so you can see what it points at without opening it. An edge may point into a workspace you cannot read: that end is returned with is_readable: false and no name, and following it answers 404.
  • Effect: read only.
Use registry__search_artifacts first when you need to find the artifact.