tessl-release-manager

To manage Git release tags and versioning for published skills, you need a lifecycle manager that dictates version bumps and automates tag creation. This ensures local repository changes align correctly with the Tessl registry and GitHub workflows.

You should bump your skill version when changes impact code, documentation, or evaluation criteria. A release manager evaluates modifications to SKILL.md or bundled scripts to determine if a version increment and new release tag are required.

To validate skill publishing to the registry, use specific validation commands that verify the publish state. This checks whether repository changes have successfully synced with the Tessl registry during the CI/CD pipeline.

Automating skill lifecycle management within a CI/CD pipeline requires aligning Git repository changes with registry workflows. A dedicated manager handles creation, refinement, evaluation, versioning, and deploying automatically as part of the pipeline.

You need to initiate new evaluation scenarios for a skill when adding new capabilities or covering missed failure modes. This ensures the updated skill meets quality criteria before you trigger versioning and release tagging.

Your Tessl registry state may not match local changes if repository updates are not aligned with registry workflows. Proper release management validates publish states and synchronizes Git tags to prevent misalignment.