Published skills return success but are not visible in search #70

Open
opened 2026-02-15 17:15:30 -05:00 by yindo · 2 comments
Owner

Originally created by @coolmanns on GitHub (Feb 5, 2026).

Description

clawdhub publish returns success with an ID, but the published skill never appears in search results or on the ClawHub website.

Steps to Reproduce

  1. Login: clawdhub whoamicoolmanns
  2. Publish a skill:
clawdhub publish ./skills/postiz --slug postiz-pro --name "Postiz Pro" --version 1.0.0 --changelog "Initial publish"
  1. CLI returns success:
✔ OK. Published postiz-pro@1.0.0 (k977525jwkhkkx6c3srgns0hdd80k9gt)
  1. Search for it:
clawdhub search "postiz-pro"
  1. Skill does not appear in results.

Additional Context

  • Tried 6+ different slugs over multiple sessions: postiz-extended, postiz-ext, social-scheduler-extended, postiz-clawed, postiz-pro
  • All return success + ID, none appear in search
  • Re-publishing the same slug+version correctly returns Version already exists (so the backend stored something)
  • First publish of the session (remarkable-tablet) DID persist and is visible
  • All subsequent publishes in the same and later sessions vanish
  • clawdhub whoami confirms auth is valid
  • Running clawdhub from npm global install on Linux (Node v22.22.0)

Expected Behavior

Published skills should appear in clawdhub search and on clawhub.com after a successful publish.

Environment

  • clawdhub CLI (npm global)
  • Node v22.22.0
  • Linux x64
  • Account: coolmanns
Originally created by @coolmanns on GitHub (Feb 5, 2026). ## Description `clawdhub publish` returns success with an ID, but the published skill never appears in search results or on the ClawHub website. ## Steps to Reproduce 1. Login: `clawdhub whoami` → `coolmanns` ✅ 2. Publish a skill: ```bash clawdhub publish ./skills/postiz --slug postiz-pro --name "Postiz Pro" --version 1.0.0 --changelog "Initial publish" ``` 3. CLI returns success: ``` ✔ OK. Published postiz-pro@1.0.0 (k977525jwkhkkx6c3srgns0hdd80k9gt) ``` 4. Search for it: ```bash clawdhub search "postiz-pro" ``` 5. **Skill does not appear in results.** ## Additional Context - Tried **6+ different slugs** over multiple sessions: `postiz-extended`, `postiz-ext`, `social-scheduler-extended`, `postiz-clawed`, `postiz-pro` - All return success + ID, none appear in search - Re-publishing the same slug+version correctly returns `Version already exists` (so the backend *stored* something) - First publish of the session (`remarkable-tablet`) DID persist and is visible - All subsequent publishes in the same and later sessions vanish - `clawdhub whoami` confirms auth is valid - Running clawdhub from npm global install on Linux (Node v22.22.0) ## Expected Behavior Published skills should appear in `clawdhub search` and on clawhub.com after a successful publish. ## Environment - clawdhub CLI (npm global) - Node v22.22.0 - Linux x64 - Account: coolmanns
Author
Owner

@ImrKhn03 commented on GitHub (Feb 5, 2026):

Also experiencing this issue with proactive-tasks skill.

Published successfully twice (v1.0.0 and v1.0.1), got confirmation with skill IDs:

  • k974jkr78w6he3h0w1m3bwt1vx80j2cm (v1.0.0)
  • k9785hrfs27arvv1v21tphffnx80jn5j (v1.0.1)

Skill does not appear in search or at https://clawdhub.com/skills/proactive-tasks ("Skill not found").

Confirming the same behavior - publish succeeds, backend stores it, but it's not indexed/visible.

Monitoring this issue for updates. 👀

@ImrKhn03 commented on GitHub (Feb 5, 2026): Also experiencing this issue with `proactive-tasks` skill. Published successfully twice (v1.0.0 and v1.0.1), got confirmation with skill IDs: - k974jkr78w6he3h0w1m3bwt1vx80j2cm (v1.0.0) - k9785hrfs27arvv1v21tphffnx80jn5j (v1.0.1) Skill does not appear in search or at https://clawdhub.com/skills/proactive-tasks ("Skill not found"). Confirming the same behavior - publish succeeds, backend stores it, but it's not indexed/visible. Monitoring this issue for updates. 👀
Author
Owner

@brookswood commented on GitHub (Feb 5, 2026):

I am running into the exact same issue here

@brookswood commented on GitHub (Feb 5, 2026): I am running into the exact same issue here
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#70