// Release a new version of the OpenClaw skill in `tapo-mcp/openclaw-skill/` by bumping its version, committing, and publishing via `npx clawhub`
Control TP-Link Tapo smart home devices (lights, plugs, power strips, hubs and sensors, cameras) via [Tapo MCP](https://github.com/mihai-dinculescu/tapo/tree/main/tapo-mcp).
Run Rust/Python/MCP checks, fix issues, then summarize findings before committing
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate
Release a new version of the tapo (Rust) and tapo-py (Python) crates together, sharing the same version number
Bump maturin to the latest release and regenerate `.github/workflows/tapo-py.yml`, preserving local customizations
Update CHANGELOG.md when the public API of the tapo (Rust), tapo-py (Python), or tapo-mcp (MCP) crates changes
| name | release-openclaw-skill |
| description | Release a new version of the OpenClaw skill in `tapo-mcp/openclaw-skill/` by bumping its version, committing, and publishing via `npx clawhub` |
Release a new version of the OpenClaw skill in tapo-mcp/openclaw-skill/ to ClawHub.
Determine the new version. Read:
version: field in tapo-mcp/openclaw-skill/SKILL.md frontmatter.tapo-mcp server version from tapo-mcp/Cargo.toml.Suggest matching the tapo-mcp version. Ask the user to confirm or supply a different version. ClawHub validates version uniqueness on publish (not monotonic ordering) — any semver string that hasn't been published before for this skill is accepted.
Bump the version.
version: in tapo-mcp/openclaw-skill/SKILL.md, update the frontmatter.tapo-mcp/openclaw-skill/SKILL.md to match the current tapo-mcp server version from step 1. This is a separate field from the skill's own version: — the pin tracks the MCP server version, not the skill version.Determine the changelog summary. Look at recent commits affecting the skill directory:
git log --oneline -10 -- tapo-mcp/openclaw-skill/
Propose a one-sentence summary of what's new in this release and ask the user to confirm or refine. This text is passed to --changelog at publish time and stored on ClawHub per version.
Commit pending changes. If the version bump (or any other prep) left uncommitted changes, run /commit with message chore(tapo-mcp): release openclaw skill vX.X.X. Skip this step if there is nothing to commit.
Publish. Ask the user for confirmation, then:
npx clawhub publish tapo-mcp/openclaw-skill \
--slug tapo \
--name "Tapo" \
--version X.X.X \
--tags "tapo,smart-home,iot,mcporter" \
--changelog "<summary from step 3>"