crystallizing

To lock a skill as an immutable production artifact, you run a crystallize workflow that seals the current battle-tested version. This process prevents unauthorized changes by applying Git tags or backups to ensure verifiable traceability and rollback capability.

Before versioning a skill as a production-grade artifact, it must satisfy defined criteria including an average score threshold, a minimum execution count, and sufficient edge-case coverage. Meeting these benchmarks ensures the skill is battle-tested and ready for immutable locking.

You should use Git tagging to freeze a validated skill version when you need to prevent accidental changes to a battle-tested workflow. This process creates a verifiable, versioned production artifact that enables reliable rollback and telemetry tracking.

Locking a skill as immutable directly enhances telemetry and traceability by enforcing record updates and logging. This ensures every production-grade artifact remains traceable throughout its lifecycle and provides verifiable rollback capability if issues arise.

The best way to prevent accidental changes to a battle-tested skill is crystallizing it into an immutable production artifact. This approach uses Git tagging or backups to seal the current version, maintaining strict version control and enabling rollback if needed.