check-cross-refs

Schema cross-reference validation checks whether declared cross_refs point to existing core entities like products, audiences, and offers in the active workspace. This resolves targets and reports outcomes, preventing broken workspace extensions before scaffolding continues.

Schemas fail to resolve referenced brand entities when cross_refs point to invalid path patterns or non-existent core entities. Validation reports distinguish blocking issues caused by invalid paths from warnings for missing future entities.

To check for unresolved entity references, ask the agent to parse declared cross_refs in the draft schema and verify referenced products, audiences, or offers exist in the active workspace. The skill reports successful resolutions and blocking issues.

The best way to prevent broken workspace extensions is to validate schema cross-references against existing workspace brand data before the extension is created. This detects unresolved entity references early in the brand workspace extension workflow.

Yes, you need access to existing workspace brand data and draft schemas containing cross_refs fields. The validation process resolves cross-references against core entities already present in the active workspace to report accurate outcomes.

When a schema cross-reference points to a missing future entity, the validation process generates a warning rather than a blocking issue. This distinguishes non-critical unresolved references from invalid path patterns that halt scaffolding.