Hua/nanobot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(agent): split slash commands and harden skill sync
Some checks failed
Test Suite / test (3.11) (push) Failing after 1m11s
Details
Test Suite / test (3.12) (push) Failing after 1m16s
Details
Test Suite / test (3.13) (push) Failing after 1m14s
Details

Browse Source
This commit is contained in:
Hua
2026-03-24 13:56:02 +08:00
parent 270dff3d7f
commit 15f7d15108
16 changed files with 1140 additions and 422 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@@ -1603,7 +1603,7 @@ These commands are available inside chats handled by `nanobot agent` or `nanobot
| `/persona set <name>` | Switch persona and start a new session |
| `/skill search <query>` | Search public skills on ClawHub |
| `/skill install <slug>` | Install a ClawHub skill into the active workspace |
| `/skill uninstall <slug>` | Remove a ClawHub-managed skill from the active workspace |
| `/skill uninstall <slug>` | Remove a locally installed workspace skill from the active workspace |
| `/skill list` | List ClawHub-managed skills in the active workspace |
| `/skill update` | Update all ClawHub-managed skills in the active workspace |
| `/mcp [list]` | List configured MCP servers and registered MCP tools |
@@ -1616,10 +1616,20 @@ These commands are available inside chats handled by `nanobot agent` or `nanobot
`~/.nanobot/workspace` path. If you start nanobot with `--workspace`, skill install/uninstall/list/update
operate on that workspace's `skills/` directory.
`/skill search` queries the live ClawHub registry API directly at
`https://lightmake.site/api/skills` using the same sort order as the SkillHub web UI, so search
does not depend on `npm` or `npx`.
For `install`, `list`, and `update`, nanobot still shells out to `npx clawhub@latest`
using ClawHub global options first: `--workdir <workspace> --no-input ...`. `/skill uninstall`
removes the local `<workspace>/skills/<slug>` directory directly and best-effort prunes
`<workspace>/.clawhub/lock.json`, because current ClawHub docs do not document an uninstall
subcommand.
`/skill search` can legitimately return no matches. In that case nanobot now replies with a
clear "no skills found" message instead of leaving the channel on a transient searching state.
If `npx clawhub@latest` cannot reach the npm registry, nanobot also surfaces the registry/network
error directly so the failure is visible to the user.
If the ClawHub registry API or `npx clawhub@latest` cannot be reached, nanobot also surfaces the
underlying network or HTTP error directly so the failure is visible to the user.
<details>
<summary><b>Heartbeat (Periodic Tasks)</b></summary>