Agent skill

Clawhub Nextclaw

A skill your agent uses 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…

MITAuto-check passed

Install Clawhub Nextclaw

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clawhub-nextclaw .claude/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .claude/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/clawhub-nextclaw .agents/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .agents/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/clawhub-nextclaw .cursor/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .cursor/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Peiiii/nextclaw.git --path skills/clawhub-nextclaw

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/clawhub-nextclaw .gemini/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .gemini/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/clawhub-nextclaw .github/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .github/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Peiiii/nextclaw clawhub-nextclaw --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/clawhub-nextclaw .opencode/skills/clawhub-nextclaw && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "clawhub-nextclaw" agent skill from https://github.com/Peiiii/nextclaw/tree/master/skills/clawhub-nextclaw into .opencode/skills/clawhub-nextclaw/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-nextclaw", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: clawhub-nextclaw
GitHub stars: 260
Token cost: ~1.4k tokens
SKILL.md length: 601 words
Files: 2
Skills in repo: 70
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses 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…

Works in 6 steps: Decide the goal → Confirm the target workspace → Run readiness check → …
The user wants to search external ClawHub skills
SKILL.md covers Overview, Default Boundary, Backend Choice and Workflow, plus 4 more sections
Calls npm

What it does

Clawhub Nextclaw is an agent skill from Peiiii/nextclaw. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `marketplace.json`).

The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

The user wants to search external ClawHub skills
Install a ClawHub skill into a NextClaw workspaces skills directory without treating ClawHub as the NextClaw marketplace

Example prompts

“/clawhub-nextclaw”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Decide the goal
Confirm the target workspace
Run readiness check
Search ClawHub
Install into NextClaw
Verify post-install result

What it can do on your machine

Read from SKILL.md and the folder at commit 4d9d500. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- npmjs.com
- docs.openclaw.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clawhub Nextclaw loads about 1.4k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 601 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~50
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Peiiii/nextclaw at commit 4d9d500, republished under its MIT licence (© Peiiii). 601 words, ~1,361 tokens.

Download SKILL.mdSave it as .claude/skills/clawhub-nextclaw/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: clawhub-nextclaw
description: 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.

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:

bash

clawhub --workdir <nextclaw-workspace> --dir skills install <skill-slug>

That pins ClawHub to <workspace>/skills/<slug>.

Backend Choice

Prefer this order:

local clawhub command 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:

bash

clawhub --workdir <nextclaw-workspace> --dir skills search "code review" --limit 1

Success means:

the target workspace is clear,
and a small real search request succeeds.

4. Search ClawHub

Use:

bash

clawhub --workdir <nextclaw-workspace> --dir skills search "<keywords>"

Optional limit:

bash

clawhub --workdir <nextclaw-workspace> --dir skills search "<keywords>" --limit 5

If the user is unsure, present the likely matches before installing.

5. Install into NextClaw

Use:

bash

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:

bash

clawhub --workdir <nextclaw-workspace> --dir skills install <skill-slug> --force

Do not add --force by default.

If clawhub is not installed, use the same command shape through npm:

bash

npm exec --yes clawhub -- --workdir <nextclaw-workspace> --dir skills install <skill-slug>

6. Verify post-install result

After install, verify:

<workspace>/skills/<slug>/SKILL.md exists
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:

bash

nextclaw skills installed --workdir <nextclaw-workspace>
nextclaw skills info <skill-slug> --workdir <nextclaw-workspace>

Show full SKILL.md (225 more words)Show less

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 --force unless 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:

bash

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:

bash

--workdir <nextclaw-workspace> --dir skills

Skill 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

Files

SKILL.md and 1 other file in skills/clawhub-nextclaw of Peiiii/nextclaw.

SKILL.md
marketplace.json

Open the folder on GitHubat commit 4d9d500

Compare with similar skills

Clawhub Nextclaw next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clawhub Nextclaw compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Clawhub Nextclaw this skillPeiiii/nextclaw	260	—	~1.4k	Automated safety check: Pass	MIT	yesterday
Clawhubopenclaw/openclaw	392k	—	~724	Automated safety check: Pass	MIT	today
Clawhubtrpc-group/trpc-agent-go	1.9k	7 repos	~404	Automated safety check: Pass	Apache-2.0	yesterday
ClawhubPhyAgentOS/PhyAgentOS-core	2.8k	3 repos	~351	Automated safety check: Pass	MIT	yesterday
External Linksthedaviddias/Front-End-Checklist	74k	—	~773	Automated safety check: Pass	MIT	4 days ago
ClawhubHKUDS/OpenOPC	1.8k	—	~467	Automated safety check: Pass	MIT	29 days ago

Similar skills

Clawhub
openclaw/openclaw
Search ClawHub for plugins by default, or skills when explicitly requested; install, verify, update, uninstall, publish, or sync skills.
392k GitHub stars~724 tokensUpdated today
Auto-check passed
Clawhub
trpc-group/trpc-agent-go
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com.
1.9k GitHub starsUsed in 7 repos~404 tokens
Auto-check passed
Clawhub
PhyAgentOS/PhyAgentOS-core
Search and install agent skills from ClawHub, the public skill registry.
2.8k GitHub starsUsed in 3 repos~351 tokens
Agent WorkflowsAuto-check passed
External Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes…
74k GitHub stars~773 tokensUpdated 4 days ago
Research & ScienceAuto-check passed
Clawhub
HKUDS/OpenOPC
Search and install agent skills from ClawHub, the public skill registry.
1.8k GitHub stars~467 tokensUpdated 29 days ago
Agent WorkflowsAuto-check passed
Clawhub Moderation
openclaw/clawhub
A skill your agent uses for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and…
9.5k GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed

More from Peiiii/nextclaw

All 70 skills in this repo

Nextclaw Skin Studio
Peiiii/nextclaw
A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…
260 GitHub stars~1.8k tokensUpdated yesterday
Auto-check passed
Development Task Telemetry
Peiiii/nextclaw
A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…
260 GitHub stars~802 tokensUpdated yesterday
Auto-check passed
Nextclaw Product Visual Assets
Peiiii/nextclaw
当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用；也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。
260 GitHub stars~801 tokensUpdated yesterday
Auto-check passed
UI UX Pro Max
Peiiii/nextclaw
A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…
260 GitHub stars~2k tokensUpdated yesterday
Auto-check passed
Impeccable
Peiiii/nextclaw
A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…
260 GitHub stars~2.5k tokensUpdated yesterday
Auto-check passed
Nextclaw Skill Resource Hub
Peiiii/nextclaw
Curate NextClaw skill resources, including OpenClaw and community sources.
260 GitHub stars~479 tokensUpdated yesterday
Auto-check passed

Questions about Clawhub Nextclaw

What does Clawhub Nextclaw do?

A skill your agent uses 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…. Clawhub Nextclaw is an agent skill from Peiiii/nextclaw. 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.

When should I use Clawhub Nextclaw?

Clawhub Nextclaw fits situations like: the user wants to search external ClawHub skills; install a ClawHub skill into a NextClaw workspaces skills directory without treating ClawHub as the NextClaw marketplace.

How do I install Clawhub Nextclaw in Claude Code?

Run `npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a claude-code`. Or copy the skill folder (skills/clawhub-nextclaw in Peiiii/nextclaw) into .claude/skills/clawhub-nextclaw in your project. Claude Code loads it when a task matches its description.

How do I install Clawhub Nextclaw in Codex?

Run `npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a codex`. Or copy the skill folder (skills/clawhub-nextclaw in Peiiii/nextclaw) into .agents/skills/clawhub-nextclaw in your project. Codex loads it when a task matches its description.

Can I use Clawhub Nextclaw in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Peiiii/nextclaw --skill clawhub-nextclaw -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clawhub-nextclaw, .gemini/skills/clawhub-nextclaw, .github/skills/clawhub-nextclaw and .opencode/skills/clawhub-nextclaw in your project.

What does Clawhub Nextclaw need to run?

Going by SKILL.md and its folder, Clawhub Nextclaw needs the command-line tools its instructions call (npm).

Does Clawhub Nextclaw access the network?

SKILL.md names 2 domains. As links in the text: npmjs.com and docs.openclaw.ai. This is read from the text; nothing was executed.

Is Clawhub Nextclaw safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clawhub Nextclaw use?

Clawhub Nextclaw is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clawhub Nextclaw use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clawhub Nextclaw?

Skills that share tags, products or a category with Clawhub Nextclaw: Clawhub (openclaw/openclaw, 392k stars), Clawhub (trpc-group/trpc-agent-go, 1.9k stars), Clawhub (PhyAgentOS/PhyAgentOS-core, 2.8k stars) and External Links (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clawhub Nextclaw?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 9, 2026.

Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Clawhub Nextclaw

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

ClawHub For NextClaw

Overview

Default Boundary

Backend Choice

Workflow

1. Decide the goal

2. Confirm the target workspace

3. Run readiness check

4. Search ClawHub

5. Install into NextClaw

6. Verify post-install result

Safe Execution Rules

Troubleshooting

ClawHub is not installed

Install went into ~/.openclaw/workspace

Skill is flagged as suspicious

Search or install fails

Success Criteria

Resources

Files

Compare with similar skills

Similar skills

More from Peiiii/nextclaw

Questions about Clawhub Nextclaw

Install went into `~/.openclaw/workspace`