cui-marketplace-reference-patterns

Architecture standards for marketplace skills ensure self-contained components with proper encapsulation. Use Skill references instead of direct external reads, internalize external content, and validate skill dependencies to maintain clean reference patterns and ensure skills work independently across deployments.

Prohibited patterns include escape sequences, cross-skill reads, and direct external file access. Instead, use Skill invocations as dependencies, rely on trusted external URLs for supplementary guidance, and categorize all references to maintain proper encapsulation and prevent skills from breaking when moved or bundled.

Reference other skills as explicit dependencies rather than embedding external content or reading across skill boundaries. This approach ensures skills remain self-contained, validates the dependency graph during development, and enables marketplace bundling and validation workflows to compute architecture scores accurately.

Internal standards provide local references to safe skill documentation; external URLs link to trusted supplementary resources; skill dependencies declare explicit invocations to other marketplace skills. This separation ensures encapsulation, enables validation workflows to detect reference violations, and allows architecture scoring to identify remediation needs.

No. Marketplace skills must use Skill references instead of direct external file reads to maintain self-containment and portability. External file reads violate reference patterns and cause validation failures; use skill invocations or trusted external URLs documented in metadata to access external resources.

Reference patterns are validated throughout development and deployment workflows to ensure skills remain portable and self-contained. Clean patterns enable successful bundling, accurate architecture scoring, and automated remediation recommendations; violations block validation until skills internalize content or convert reads to proper skill dependencies.