What problem does it solve?
Releasing a new version of the Tapo OpenClaw skill involves several error-prone manual steps: reading the current skill and server versions, updating frontmatter and minimum-version pins, summarizing changes, committing, and publishing to ClawHub. This Skill orchestrates that entire release workflow so nothing is missed.
Core Features & Use Cases
- Version Coordination: Reads the skill version from
tapo-mcp/openclaw-skill/SKILL.md and the server version from tapo-mcp/Cargo.toml, then suggests a matching version and updates both the version: field and the minimum-server pin.
- Changelog Generation: Inspects recent git commits touching the skill directory and proposes a one-sentence release summary passed to
--changelog at publish time.
- Commit and Publish: Commits pending changes with a conventional release message and publishes via
npx clawhub publish with the correct slug, tags, and version.
- Use Case: After merging feature changes into
tapo-mcp/openclaw-skill/, invoke this Skill to bump the version to match the new tapo-mcp release, commit the change, and publish the updated skill to ClawHub in one guided flow.
Quick Start
Release a new version of the OpenClaw skill in tapo-mcp/openclaw-skill to ClawHub, bumping its version to match the current tapo-mcp server version.