release-openclaw-skill

Automates version bumping, committing, and publishing of the Tapo OpenClaw skill to ClawHub.

797|80|Updated Jun 6, 2022
One-click install
npx skills add https://github.com/mihai-dinculescu/tapo --skill release-openclaw-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-openclaw-skill
Source: https://github.com/mihai-dinculescu/tapo/tree/main/.claude/skills/release-openclaw-skill
Command: npx skills add https://github.com/mihai-dinculescu/tapo --skill release-openclaw-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about release-openclaw-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a new version of the Tapo OpenClaw skill to ClawHub?

Run the release workflow, which bumps the version in tapo-mcp/openclaw-skill/SKILL.md, commits the change, and runs npx clawhub publish with the slug tapo, version, tags, and a changelog summary. ClawHub validates that the version has not been published before.

How is the OpenClaw skill version chosen for a release?

The workflow reads the current version from the SKILL.md frontmatter and the tapo-mcp server version from tapo-mcp/Cargo.toml, then suggests matching the server version. Any semver string not previously published is accepted, since ClawHub checks uniqueness rather than monotonic ordering.

Does the skill version need to match the tapo-mcp server version?

No, they are separate fields. The skill's own version tracks releases of the skill, while the minimum-server pin in the Setup section tracks the tapo-mcp server version. The workflow updates the pin to the current server version independently of the skill version.

What happens if there is nothing to commit before publishing?

The commit step is skipped when the version bump and other preparation leave no uncommitted changes. The workflow proceeds directly to the publish confirmation and the npx clawhub publish command.

Why does ClawHub reject a publish with an existing version?

ClawHub enforces version uniqueness per skill, so republishing an already-used version string fails. Choose a new semver string that has not been published before for this skill; ordering does not need to be monotonic.