skill-release-manager

What This Skill Does

The skill-release-manager is a powerful orchestration tool designed to streamline the entire lifecycle of an OpenClaw skill release. Manual deployments are often error-prone, involving repetitive steps such as updating manifest files, committing version changes, managing Git subtrees, and triggering remote registry updates. This skill automates these processes, acting as a unified CLI bridge between your local development environment and the global distribution channels. By handling versioning, remote synchronization, and registry publication in a single execution command, it allows developers to focus on building features rather than managing deployment pipelines.

Installation

To integrate this utility into your development environment, ensure you have the OpenClaw agent running and authenticated. Execute the following command in your terminal: clawhub install openclaw/skills/skills/autogame-17/skill-release-manager

Ensure that you have skill-publisher installed within your workspace, as the release manager relies on it for repository synchronization. Additionally, verify that your local environment is authenticated with the clawhub CLI before initiating a release.

Use Cases

This skill is ideal for professional developer workflows and teams managing multiple OpenClaw extensions. It is particularly effective for teams following Semantic Versioning (SemVer), as it allows for rapid patching, minor feature releases, and major architectural shifts without manual file editing. Use it when you need to deploy an update to a public repository while simultaneously registering that version in the ClawHub catalog, ensuring that your users always have access to the latest, verified code updates.

Example Prompts

1. "OpenClaw, use skill-release-manager to patch the private-evolver skill and push the updates to the repository at https://github.com/autogame-17/evolver.git with the note: Fixed minor dependency bug."
2. "Release a new minor version for the skill at skills/my-custom-assistant. Sync it to my remote repo and publish the new build to ClawHub now."
3. "Hey, run a major release for the project located in skills/automation-bridge. Use version 2.0.0 and include the release notes about the new API integration."

Tips & Limitations

Always ensure your git workspace is clean before running the release manager; uncommitted changes may cause conflict during the automated version bump process. While the tool is highly efficient, it currently requires direct network access to both GitHub and the ClawHub registry, so ensure your firewall settings allow traffic from your local agent. Note that the skill assumes standard folder structures; if your repository uses non-standard subdirectories for manifest files, you may need to verify the pathing before execution. Always review your release notes for accuracy, as these become immutable once pushed to the GitHub repository.