company-skill-bundle-management

Skill precedence follows a strict hierarchy: company skills override workspace skills, which override bundled sets. This rule automatically determines which version injects and takes effect during a name collision across your environment.

Mode boundaries separate active and passive skill behaviors to strictly control logic injection. Enforcing these boundaries prevents bundled skills from accidentally triggering active workflows reserved for company or workspace levels.

Elevate skill logic to a workflow or Company Skills Run when simple precedence or mode boundaries cannot resolve complex conflicts. This promotion action handles advanced merging, splitting, or overriding needs that exceed standard skill injection capabilities.

Analyze your current skill ecosystem, identify naming collisions, and establish a canonical ownership plan. This proactive management clarifies precedence rules and keeps mode boundaries tight across company and workspace levels.

Skill ownership directly dictates precedence application by establishing whether a skill belongs to the company, workspace, or a bundle. Defining this ownership is the primary step to determine which version takes effect during any conflict.

A bundled skill should not override a workspace skill because workspace precedence strictly outranks bundle precedence. If this occurs, check your mode boundaries and verify your canonical ownership plan to correct the injection behavior.