openclaw - 💡(How to fix) Fix ClawHub should support deleting or hiding individual skill versions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#78024Fetched 2026-05-06 06:17:47
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
Timeline (top)
closed ×1commented ×1

ClawHub currently exposes version history (inspect --versions, inspect --version, page Versions tab), but there does not appear to be a way to delete or hide a single mistaken version.

The CLI has:

  • clawhub publish ... --version <version>
  • clawhub inspect <slug> --versions
  • clawhub inspect <slug> --version <version>
  • clawhub delete <slug>
  • clawhub hide <slug>

But delete/hide appear to operate at the skill/listing level, not at the version level.

Root Cause

ClawHub currently exposes version history (inspect --versions, inspect --version, page Versions tab), but there does not appear to be a way to delete or hide a single mistaken version.

The CLI has:

  • clawhub publish ... --version <version>
  • clawhub inspect <slug> --versions
  • clawhub inspect <slug> --version <version>
  • clawhub delete <slug>
  • clawhub hide <slug>

But delete/hide appear to operate at the skill/listing level, not at the version level.

Code Example

clawhub delete-version <slug> --version 1.0.1
clawhub hide-version <slug> --version 1.0.1

---

clawhub delete <slug> --version 1.0.1
clawhub hide <slug> --version 1.0.1
RAW_BUFFERClick to expand / collapse

Summary

ClawHub currently exposes version history (inspect --versions, inspect --version, page Versions tab), but there does not appear to be a way to delete or hide a single mistaken version.

The CLI has:

  • clawhub publish ... --version <version>
  • clawhub inspect <slug> --versions
  • clawhub inspect <slug> --version <version>
  • clawhub delete <slug>
  • clawhub hide <slug>

But delete/hide appear to operate at the skill/listing level, not at the version level.

Requested capability

Add version-level management for skill owners, for example:

clawhub delete-version <slug> --version 1.0.1
clawhub hide-version <slug> --version 1.0.1

or equivalent options:

clawhub delete <slug> --version 1.0.1
clawhub hide <slug> --version 1.0.1

API-level support would also be useful, e.g. an authenticated endpoint to soft-delete/hide a specific version.

Motivation

Skill publishers need a safe way to correct mistakes without deleting the entire skill listing:

  • accidentally uploaded wrong files
  • bad changelog text
  • scanner false start / bad packaging
  • version published before final review
  • backfilled versions that should no longer be offered as downloads

Expected behavior

A skill owner should be able to:

  1. list versions
  2. hide or soft-delete one specific version
  3. keep the skill/listing and other versions available
  4. prevent deleting the only/latest version unless an explicit confirmation flag is used
  5. update the latest tag automatically if the latest version is removed/hidden, or require an explicit replacement target

Safety notes

Prefer soft-delete/hide over hard delete so installs remain auditable and accidental deletion can be reversed by maintainers.

Potential guardrails:

  • owner/admin only
  • require exact semver
  • require --yes for non-interactive use
  • block removing the only remaining version unless --allow-empty or similar is passed
  • if deleting the current latest, require --set-latest <version> or automatically choose the next highest SemVer version

extent analysis

TL;DR

To address the issue, implement version-level management by adding delete-version and hide-version commands or options to the existing clawhub CLI.

Guidance

  • Introduce new commands clawhub delete-version <slug> --version <version> and clawhub hide-version <slug> --version <version> to allow skill owners to manage specific versions.
  • Modify the existing clawhub delete and clawhub hide commands to accept a --version option for version-level operations.
  • Implement API-level support for authenticated endpoints to soft-delete or hide specific versions.
  • Consider adding safety features such as owner/admin only access, exact semver requirement, and --yes confirmation for non-interactive use.

Example

clawhub delete-version my-skill --version 1.0.1
clawhub hide-version my-skill --version 1.0.1

Notes

The implementation should prioritize soft-delete/hide over hard delete to maintain auditability and allow for accidental deletion reversal.

Recommendation

Apply a workaround by implementing the proposed delete-version and hide-version commands or options, as this will provide the necessary version-level management capabilities for skill owners.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

A skill owner should be able to:

  1. list versions
  2. hide or soft-delete one specific version
  3. keep the skill/listing and other versions available
  4. prevent deleting the only/latest version unless an explicit confirmation flag is used
  5. update the latest tag automatically if the latest version is removed/hidden, or require an explicit replacement target

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING