AiResource entity for AI content assets

When you register an AI content asset as an AiResource entity, the asset becomes discoverable in the RHDH Software Catalog alongside Components, APIs, and other entity kinds.

Platform Engineers can publish governed, authoritative AI content assets, and developers can find and adopt those assets by using the same search and filtering that they already use for other catalog entities.

Important

The AiResource entity is a Developer Preview feature. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.

For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Support Scope.

In RHDH, an AI content asset is a source code repository or an OCI image that contains the skills and rules that AI coding tools and autonomous agents use. Teams that build agentic coding workflows with tools such as Claude Code, GitHub Copilot, and Cursor often keep these assets in isolated repositories or ad hoc bundles. As a result, other teams cannot discover the assets, which leads to duplicated effort and inconsistent AI behavior across the organization.

The AiResource entity is a Backstage Software Catalog entity kind that you can use to register, share, and discover AI content assets in Red Hat Developer Hub (RHDH).

Note

There is no dedicated user interface for AiResource entities. Entities appear in the Software Catalog like any other kind, and you can filter for them by setting Kind = AiResource .

What an AiResource entity registers

An AiResource entity registers an asset, not the individual skills or rules inside it. The unit of registration is the source repository or OCI image that contains the content, which is analogous to how the Component entity kind registers a source code repository.

The AiResource entity supports two asset location types, which you set in the backstage.io/source-location annotation:

  • git:: A source code repository that a developer can browse, for example a repository that contains .claude/skills/ or .cursor/rules/ directories.
  • oci:: An OCI image reference in a container registry, for example oci://quay.io/my-org/skills/pdf-processor:v1.2.0 .

What an AiResource entity does not do

The AiResource entity has the following boundaries:

  • Individual skills and rules are files and folders within the asset. They are not registered as separate catalog entities.
  • The catalog does not ingest content from OCI images. It records the image reference only.
  • The AiResource entity is catalog-only. Runtime integration with AI agents that consume the assets is not included.

For an OCI image asset, the catalog stores the image reference only. RHDH does not pull, extract, run, or index the content inside the image, and it does not verify that the reference is reachable when the entity is ingested.