agentleFS
mihai-dinculescumihai-dinculescu/tapo/.claude/skills/release-openclaw-skill/SKILL.md

release-openclaw-skill

Skill877 starsChanged 5 days agoMITView on GitHub

Release a new version of the OpenClaw skill in `tapo-mcp/openclaw-skill/` by bumping its version, committing, and publishing via `npx clawhub`

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Determine the new version: Read:

    line 12
  2. Very specific:

    If the new version differs from the existing version: in tapo-mcp/openclaw-skill/SKILL.md, update the frontmatter.

    line 19
  3. Very specific:

    Update the "v0.X.X or later" minimum-server pin in the Setup section of tapo-mcp/openclaw-skill/SKILL.md to match the current tapo-mcp …

    line 20
  4. Distinctive:

    Determine the changelog summary: Look at recent commits affecting the skill directory:

    line 22
  5. Very specific:

    Commit pending changes: If the version bump (or any other prep) left uncommitted changes, run /commit with message chore(tapo-mcp): release …

    line 30
  6. Distinctive:

    Publish: Ask the user for confirmation, then:

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release OpenClaw skill

Release a new version of the OpenClaw skill in tapo-mcp/openclaw-skill/ to ClawHub.

Steps

  1. Determine the new version. Read:

    • The current skill version from the version: field in tapo-mcp/openclaw-skill/SKILL.md frontmatter.
    • The current 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.

  2. Bump the version.
    • If the new version differs from the existing version: in tapo-mcp/openclaw-skill/SKILL.md, update the frontmatter.
    • Update the "v0.X.X or later" minimum-server pin in the Setup section of 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.
  3. 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.

  4. 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.
  5. 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>"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.