Welcome to Jetson ORIN NANO SUPER repository
当製品の日本語版マニュアル資料は、こちらからご取得ください。
09.OpenClawHub Introduction (Skill Installation)
ClawHub
ClawHub is the public Skills registry for OpenClaw. It is a free service: all Skills are public and open—anyone can view, share, and reuse them. A Skill is simply a folder containing a SKILL.md file (along with supporting text files). You can browse Skills via the web application, or use the CLI to search for, install, update, and publish Skills. Website: clawhub.com

Positioning within OpenClaw
By default, the CLI installs Skills to ./skills within the current working directory. If an OpenClaw workspace is configured, clawhub will fall back to that workspace unless you override it using --workdir (or CLAWHUB_WORKDIR). OpenClaw loads workspace Skills from <workspace>/skills, and these will take effect in the next session. If you are already utilizing ~/.openclaw/skills or built-in Skills, workspace Skills take precedence. For more details regarding Skill loading, sharing, and access control, please refer to Skills.

Who Is It For? (Beginner-Friendly)
If you want to add new capabilities to your OpenClaw agents, ClawHub is the easiest way to find and install Skills. You do not need to understand how the backend works. You can:
- Search for Skills using natural language.
- Install Skills into your workspace.
- Update Skills later with a single command.
- Back up your own Skills by publishing them.
Installing the CLI
Original ClawHub CLI (International Users)
xxxxxxxxxxnpm i -g clawhubpnpm add -g clawhub

Log In to Your ClawHub Account
Why Log In?
Although ClawHub allows unauthenticated users to search for and install Skills, logging in offers the following key benefits:
- ✅ Avoid Rate Limits: Unauthenticated users may encounter download speed limits.
- ✅ Access Full Features: Certain advanced features require you to be logged in to use them.
- ✅ Publish Skills: Only logged-in users can publish their own Skills.
- ✅ Favorites and Comments: You can bookmark your favorite Skills and post comments.
- ✅ Usage Statistics: View your personal usage data.
Login Steps
Method 1: Log In via GitHub (Recommended)
This is the simplest and most secure way to log in.
1.1 Visit the ClawHub Website
Open the following URL in your browser: https://clawhub.com

1.2 Click "Login"
Click the "Login" button located in the top-right corner of the page:

1.3 Select GitHub Login
On the login page, click "Sign in with GitHub."
1.4 Authorize Access
Once authorization is successful, you will be automatically redirected back to ClawHub, where your logged-in status will be displayed.
Method 2: Log In Using a Token
If you are unable to log in via GitHub, you can use the Token method instead.
2.1 Log In to Your Account
First, follow the steps outlined in Method 1 to log in to the ClawHub website using GitHub. ##### 2.2 Accessing the Settings Page
After logging in, click your user avatar in the top-right corner of the page, then select "Settings":

2.3 Creating an API Token
On the Settings page, locate the "API Tokens" section and click "Create token":

2.4 Copying the Token
The system will generate a new API Token; click the copy button to copy this Token:

⚠️ Important Note:
- The Token is displayed only once; please be sure to copy and store it securely.
- Do not share your Token with others.
- You can delete the Token at any time from the Settings page.
2.5 Logging In via Terminal
Open your terminal and run the following command (replace YourToken with the Token you just copied):
xxxxxxxxxxclawhub login --token YourToken
Note: There is a space after --token; then, paste your Token.
Frequently Asked Questions
Issue 1: Login Prompts "Invalid Token"
Error Message:
xxxxxxxxxxError: Invalid token
Possible Causes:
- The Token was not copied completely.
- The Token has expired or been deleted.
- Extra spaces or characters were entered during input.
Solutions:
- Re-generate the Token and copy it again.
- Ensure there are no extra spaces when copying.
- Verify that the Token is complete.
Issue 2: GitHub Login Failed
Possible Causes:
- Network connection issues.
- The GitHub account's email address has not been verified.
- The browser blocked the redirect.
Solutions:
- Check your network connection.
- Confirm that your GitHub account's email address has been verified.
- Try using a different browser or Incognito mode.
Issue 3: Still Rate-Limited After Logging In
Possible Causes:
- The login session did not take effect.
- You are using the wrong CLI tool (clawhub vs skillhub).
Solutions:
- Run
clawhub whoamito confirm your login status. - Confirm that you are using the correct CLI commands.
- Log in again.
Quick Start
Using the Original ClawHub
- Install the CLI (see the previous section).
- Search for the content you need: (Users in mainland China may require a VPN/proxy)
xxxxxxxxxxclawhub search "find"

- Install a Skill:
Syntax: clawhub install <skill-slug>
xxxxxxxxxxclawhub install find
- Start a new OpenClaw session to load the newly installed Skills. ## Common Agent Workflows
Search for Skills
xxxxxxxxxxclawhub search "postgres backups"
Or using SkillHub:
xxxxxxxxxxskillhub search "postgres backups"
Download New Skills
xxxxxxxxxxclawhub install my-skill-pack
Or using SkillHub:
xxxxxxxxxxskillhub install my-skill-pack
Update Installed Skills
xxxxxxxxxxclawhub update --all
Or using SkillHub:
xxxxxxxxxxskillhub update --all
Back Up Your Skills (Publish or Sync)
For a single Skills folder:
xxxxxxxxxxclawhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0 --tags latest
Scan and back up multiple Skills at once:
xxxxxxxxxxclawhub sync --all
CLI Commands and Arguments
Global Options (apply to all commands):
--workdir <dir>: Working directory (Default: current directory; falls back to OpenClaw workspace).--dir <dir>: Skills directory, relative to the working directory (Default:skills).--site <url>: Website base URL (for browser-based login).--registry <url>: Registry API base URL.--no-input: Disable prompts (non-interactive mode).-V, --cli-version: Print CLI version.
Authentication:
clawhub login(browser flow) orclawhub login --token <token>clawhub logoutclawhub whoami
Options:
--token <token>: Paste API token.--label <label>: Label for the stored browser login token (Default:CLI token).--no-browser: Do not open the browser (requires--token).
Search:
clawhub search "query"--limit <n>: Maximum number of results.
Install:
clawhub install <slug>--version <version>: Install a specific version.--force: Overwrite if the folder already exists. Update:clawhub update <slug>clawhub update --all--version <version>: Update to a specific version (single slug only).--force: Force overwrite when local files do not match any published version.
List:
clawhub list(Reads.clawhub/lock.json)

Publish:
clawhub publish <path>--slug <slug>: Skill identifier.--name <name>: Display name.--version <version>: Semantic version number.--changelog <text>: Changelog text (can be empty).--tags <tags>: Comma-separated tags (Default:latest).
Delete/Restore (Owners/Admins only):
clawhub delete <slug> --yesclawhub undelete <slug> --yes
Sync (Scan local Skills + Publish new/updated Skills):
clawhub sync--root <dir...>: Additional root directories to scan.--all: Upload all content without prompts.--dry-run: Show what will be uploaded.--bump <type>: Version increment typepatch|minor|major(Default:patch).--changelog <text>: Changelog for non-interactive updates.--tags <tags>: Comma-separated tags (Default:latest).--concurrency <n>: Concurrency level for registry checks (Default: 4).
Environment Variables
CLAWHUB_SITE: Override the website URL.CLAWHUB_REGISTRY: Override the registry API URL.CLAWHUB_CONFIG_PATH: Override the location where the CLI stores tokens/configuration.CLAWHUB_WORKDIR: Override the default working directory.CLAWHUB_DISABLE_TELEMETRY=1: Disable telemetry for thesynccommand.For more information about ClawHub, please refer to: ClawHub - OpenClaw