ecosystem-lifecycle

Automate skill classification by running a governance workflow that categorizes components as generic or project-specific and propagates generic skills to the hub. This maintains ecosystem integrity by enforcing frontmatter validation and content checks.

Auto-provision missing local skills by running a workflow that imports components from the global library or flags coverage gaps for creation. This ensures consistent coverage across projects when a technology lacks a local skill.

Self-healing verifies user-reported rule violations and proposes fixes with traceable evidence. It uses a structured envelope for auditable decisions and logging to maintain quality and coverage across projects.

Run governance checks after ecosystem-creation completes, when rule violations are reported, or when a technology lacks a local skill. This triggers classification, self-healing, and auto-provisioning to maintain ecosystem integrity.

You can audit and log skill classification changes using a structured envelope that records governance decisions. This workflow tracks classifications and changes across projects to maintain ecosystem quality and coverage.

Ecosystem lifecycle validation enforces frontmatter validation and content checks on all skill components. It applies governance workflows to classify, self-heal, and auto-provision skills to maintain consistent coverage.