Skip to content

fix(skills): use registry-backed search for skills discovery#929

Merged
xiaket merged 2 commits intosipeed:mainfrom
dwizzle204:fix/skills-search-registry-404
Mar 1, 2026
Merged

fix(skills): use registry-backed search for skills discovery#929
xiaket merged 2 commits intosipeed:mainfrom
dwizzle204:fix/skills-search-registry-404

Conversation

@dwizzle204
Copy link
Contributor

@dwizzle204 dwizzle204 commented Feb 28, 2026

📝 Description

Fixes skills search returning 404 by removing the stale hardcoded skills index lookup and using configured skill registries (ClawHub) for discovery.

This keeps search aligned with the registry system already used elsewhere in skills workflows.

🗣️ Type of Change

  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 📖 Documentation update
  • ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

  • 🤖 Fully AI-generated (100% AI, 0% Human)
  • 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
  • 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

Fixes #928

📚 Technical Context (Skip for Docs)

  • Reference URL: skills search returns HTTP 404 in v0.2.0 (ClawHub registry mismatch) #928
  • Reasoning:
    • skills search currently calls a hardcoded URL (https://raw.githubusercontent.com/sipeed/picoclaw-skills/main/skills.json) that returns 404.
    • Registry search infrastructure already exists (RegistryManager, ClawHubRegistry) and should be the source of truth.
    • This patch switches skills search to registry-backed search and preserves existing error prefix (Failed to fetch skills list) for CLI consistency.

🧪 Test Environment

  • Hardware: x86_64 Linux VM
  • OS: Ubuntu 20.04
  • Model/Provider: N/A (CLI skills command path)
  • Channels: N/A

📸 Evidence (Optional)

Click to view Logs/Screenshots

Local verification:

  • go generate ./...
  • make check

☑️ Checklist

  • My code/docs follow the style of this project.
  • I have performed a self-review of my own changes.
  • I have updated the documentation accordingly.

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
@xiaket xiaket added the type: bug Something isn't working label Mar 1, 2026
Copy link
Collaborator

@xiaket xiaket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please take a look and let me know when it's ready.

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
@dwizzle204
Copy link
Contributor Author

Addressed all requested changes in c0c7964, replied to each thread, and resolved all three review threads. Ready for re-review. Thanks!

Copy link
Collaborator

@xiaket xiaket left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@xiaket xiaket merged commit cadcdc0 into sipeed:main Mar 1, 2026
2 checks passed
vvr3ddy added a commit to vvr3ddy/picoclaw that referenced this pull request Mar 1, 2026
Changes from upstream:
- fix(channel): config cleanup and regex precompile (sipeed#911, sipeed#916)
- fix(github_copilot): improve error handling (sipeed#919)
- fix(wecom): context leaks and data race fixes (sipeed#914, sipeed#918)
- fix(tools): HTTP client caching and response body cleanup (sipeed#940)
- feat(tui): Add configurable Launcher and Gateway process management (sipeed#909)
- feat(migrate): Update migration system with openclaw support (sipeed#910)
- fix(skills): Use registry-backed search for skills discovery (sipeed#929)
- build: Add armv6 support to goreleaser (sipeed#905)
- docs: Sync READMEs and channel documentation
@Orgmar
Copy link
Contributor

Orgmar commented Mar 2, 2026

@dwizzle204 Switching skills search from the stale hardcoded index to the registry system is the right call. Having search aligned with how skills are actually managed avoids those confusing 404s.

We're putting together the PicoClaw Dev Group on Discord for contributors to collaborate. If you'd like to join, send an email to support@sipeed.com with the subject [Join PicoClaw Dev Group] dwizzle204 and we'll send you the invite link.

liangzhang-keepmoving pushed a commit to liangzhang-keepmoving/picoclaw that referenced this pull request Mar 2, 2026
)

* fix(skills): use registry-backed search for skills discovery

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

* fix(skills): address review comments for registry search

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

---------

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
Co-authored-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
hyperwd pushed a commit to hyperwd/picoclaw that referenced this pull request Mar 5, 2026
)

* fix(skills): use registry-backed search for skills discovery

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

* fix(skills): address review comments for registry search

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

---------

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
Co-authored-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
Pluckypan pushed a commit to Pluckypan/picoclaw that referenced this pull request Mar 6, 2026
)

* fix(skills): use registry-backed search for skills discovery

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

* fix(skills): address review comments for registry search

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>

---------

Signed-off-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
Co-authored-by: dwizzle204 <25712917+dwizzle204@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

skills search returns HTTP 404 in v0.2.0 (ClawHub registry mismatch)

3 participants