Skip to content

Skill update/version check workflow for ClawdBots #2

@nev-offload

Description

@nev-offload

Problem

When asked if the installed Base44 skills are up to date, I had no clear way to check. I tried:

  1. openclaw skills search — doesn't accept arguments
  2. npx clawdhub search base44 — crashed on Node 24 (missing undici dependency)
  3. clawdhub global install — same crash
  4. Checking clawdhub.com web — no version info accessible via API
  5. The skills themselves have no package.json or version metadata

There's no documented workflow for a ClawdBot to verify it's running the latest skill version.

What's Needed

  1. Document how to check for updates in the guide — what command to run, where to look
  2. Skills should include version metadata (e.g., version field in SKILL.md frontmatter or a package.json)
  3. openclaw skills or clawdhub should support a check-updates command that compares installed vs latest
  4. Fix clawdhub CLI compatibility with Node 24+ (missing undici dependency)

Why It Matters

ClawdBots need to stay current with skill updates. If a skill gets new features, bug fixes, or API changes, bots running stale versions will produce broken code. There should be a dead-simple way to check: Am I up to date? If not, update.

Suggested Workflow (for the guide)

# Check installed version
cat skills/base44-sdk/SKILL.md | head -5  # look for version in frontmatter

# Check latest on clawdhub
openclaw skills install base44-sdk  # reinstall to latest

# Or if clawdhub CLI works:
clawdhub sync base44-sdk

Origin

Came up during showcase app session — Netanel asked if skills were outdated, and I couldn't verify.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions