clawhub-nextclaw
Skill263 starsChanged 37 days agoMITView on GitHub
Use when the user wants to search external ClawHub skills or install a ClawHub skill into a NextClaw workspace's skills directory without treating ClawHub as the NextClaw marketplace.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/code-citation-clickable.mdcCursor rule
- .cursor/rules/commit-message-english.mdcCursor rule
- autonomous-maintainability-campaignSkill
- autonomous-requirement-discoverySkill
- delivering-delegated-linear-issuesSkill
- development-deliverySkill
- development-designSkill
- development-implementationSkill
- development-lifecycleSkill
- development-retrospectiveSkill
- development-reviewSkill
- development-task-understandingSkill
- development-validationSkill
- idea-search-funnelSkill
- nextclaw-agent-instructions-governanceSkill
- nextclaw-product-blog-storytellingSkill
- nextclaw-product-visual-assetsSkill
- x-twitter-birdSkill
- aigen-image-generationSkill
- bb-browserSkill
- browser-controlSkill
- claude-code-narp-runtimeSkill
- codex-narp-runtimeSkill
- find-skillsSkill
- gemigo-cliSkill
- impeccableSkill
- lark-cliSkill
- linear-cliSkill
- mmx-cliSkill
- nextclaw-skin-studioSkill
- opencliSkill
- proxy-local-ai-subscriptionsSkill
- publish-to-nextclaw-marketplaceSkill
- skillhub-guideSkill
- superpowersSkill
- ui-ux-pro-maxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 10 are distinctive, and 14 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill when the user wants to use ClawHub as an external skill source for NextClaw.
- Distinctive: line 14
search ClawHub skills when needed,
- Distinctive: line 18
Do not blur the ecosystems:
- Very specific: line 24
Do not describe a ClawHub skill as a NextClaw marketplace skill unless it has separately been published to the NextClaw marketplace.
- Very specific: line 28
Default to the current NextClaw workspace as the install target.
- Very specific: line 30
If the workspace is ambiguous, clarify it before installing.
- Very specific: line 31
Do not silently install into a random repo or into OpenClaw's default ~/.openclaw/workspace.
- Very specific: line 48
Do not rely on raw clawhub install <slug> without an explicit workspace.
- Distinctive: line 62
search for possible skills,
- Distinctive: line 66
If the user does not know the exact slug, search first.
- Very specific: line 70
Default to the active NextClaw workspace.
- Very specific: line 76
Use --workdir <workspace> --dir skills so the target is explicit.
- Distinctive: line 105
If the user is unsure, present the likely matches before installing.
- Distinctive: line 115
If the upstream skill is flagged as suspicious and the user explicitly wants to proceed, rerun with:
- Very specific: line 121
Do not add --force by default.
- Very specific: line 123
If clawhub is not installed, use the same command shape through npm:
- Distinctive: line 146
Keep calling ClawHub an external source, not our official marketplace.
- Distinctive: line 147
Search before install when the exact slug is uncertain.
- Very specific: line 149
Never silently install into the repo root unless the repo root is the intended NextClaw workspace.
- Very specific: line 150
Do not use --force unless the user explicitly accepts the risk or the task is a deterministic overwrite request.
- Distinctive: line 151
If ClawHub backend resolution fails, stop and report the missing runtime instead of pretending the install succeeded.
- Distinctive: line 163
If that also fails, report that Node/npm access is missing or blocked.
- Very specific: line 179
Keep the warning visible. Only continue with --force when the user explicitly wants that risk.
- Very specific: line 180
Only continue with --force when the user explicitly wants that risk.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ClawHub For NextClaw
Overview
Use this skill when the user wants to use ClawHub as an external skill source for NextClaw.
This skill has one job:
- search ClawHub skills when needed,
- install a selected ClawHub skill into the intended NextClaw workspace's
skills/directory, - and keep the boundary explicit.
Do not blur the ecosystems:
- NextClaw marketplace is our own marketplace.
- ClawHub is an external upstream skill registry.
- This skill is only an external importer for NextClaw users.
Do not describe a ClawHub skill as a NextClaw marketplace skill unless it has separately been published to the NextClaw marketplace.
Default Boundary
Default to the current NextClaw workspace as the install target.
If the workspace is ambiguous, clarify it before installing.
Do not silently install into a random repo or into OpenClaw's default ~/.openclaw/workspace.
The safe path in this skill is to always drive ClawHub with an explicit NextClaw workspace:
clawhub --workdir <nextclaw-workspace> --dir skills install <skill-slug>That pins ClawHub to <workspace>/skills/<slug>.
Backend Choice
Prefer this order:
- local
clawhubcommand if already installed npm exec --yes clawhub -- ...
Do not rely on raw clawhub install <slug> without an explicit workspace.
Why:
- ClawHub otherwise may fall back to an OpenClaw workspace such as
~/.openclaw/workspace - the user explicitly wants the skill installed into NextClaw's own
skills/directory
Workflow
1. Decide the goal
Classify the request into one of these:
- readiness check,
- search for possible skills,
- install a known skill,
- troubleshoot an existing imported ClawHub skill.
If the user does not know the exact slug, search first.
2. Confirm the target workspace
Default to the active NextClaw workspace.
Typical target:
<workspace>/skills/
Use --workdir <workspace> --dir skills so the target is explicit.
3. Run readiness check
Use:
clawhub --workdir <nextclaw-workspace> --dir skills search "code review" --limit 1Success means:
- the target workspace is clear,
- and a small real
searchrequest succeeds.
4. Search ClawHub
Use:
clawhub --workdir <nextclaw-workspace> --dir skills search "<keywords>"Optional limit:
clawhub --workdir <nextclaw-workspace> --dir skills search "<keywords>" --limit 5If the user is unsure, present the likely matches before installing.
5. Install into NextClaw
Use:
clawhub --workdir <nextclaw-workspace> --dir skills install <skill-slug>If the upstream skill is flagged as suspicious and the user explicitly wants to proceed, rerun with:
clawhub --workdir <nextclaw-workspace> --dir skills install <skill-slug> --forceDo not add --force by default.
If clawhub is not installed, use the same command shape through npm:
npm exec --yes clawhub -- --workdir <nextclaw-workspace> --dir skills install <skill-slug>6. Verify post-install result
After install, verify:
<workspace>/skills/<slug>/SKILL.mdexists- ClawHub created
<workspace>/.clawhub/lock.json - the installed skill is now visible to NextClaw as a workspace skill
For local verification you can also use:
nextclaw skills installed --workdir <nextclaw-workspace>
nextclaw skills info <skill-slug> --workdir <nextclaw-workspace>Safe Execution Rules
- Keep calling ClawHub an external source, not our official marketplace.
- Search before install when the exact slug is uncertain.
- Always pin
--workdir <workspace> --dir skills. - Never silently install into the repo root unless the repo root is the intended NextClaw workspace.
- Do not use
--forceunless the user explicitly accepts the risk or the task is a deterministic overwrite request. - If ClawHub backend resolution fails, stop and report the missing runtime instead of pretending the install succeeded.
Troubleshooting
ClawHub is not installed
Use:
npm exec --yes clawhub -- ...If that also fails, report that Node/npm access is missing or blocked.
Install went into ~/.openclaw/workspace
That means ClawHub was run without an explicit NextClaw workspace.
Fix by rerunning with:
--workdir <nextclaw-workspace> --dir skillsSkill is flagged as suspicious
ClawHub may block non-interactive install unless --force is provided.
Keep the warning visible.
Only continue with --force when the user explicitly wants that risk.
Search or install fails
Check:
- network access,
- npm registry reachability if using
npm exec, - ClawHub registry reachability,
- and whether the slug really exists.
Success Criteria
This skill is working correctly when:
- the user can search ClawHub from inside a NextClaw workflow,
- installation lands in the intended NextClaw workspace's
skills/directory, - the boundary between external ClawHub and NextClaw marketplace stays explicit,
- and install success is verified by real filesystem results instead of assumption.
Resources
- ClawHub npm package: https://www.npmjs.com/package/clawhub
- ClawHub docs: https://docs.openclaw.ai/zh-CN/tools/clawhub
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.