What makes SkillHub Manager notable?

1.2K downloads. Trust evidence available

How should SkillHub Manager be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

SkillHub Manager

Manage and publish agent skills on SkillHub and ClawHub. Best for developers and operators who need a repeatable workflow to search skills, inspect packages,...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.3release · observed Apr 19, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s177mgnzkjxtm73sg9mgwxwc9n83nygc:skillhub-manager

Install using `clawhub skill install s177mgnzkjxtm73sg9mgwxwc9n83nygc:skillhub-manager` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/codeblackhole1024/skillhub-manager before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/snapshot"

Documentation

CLAWHUB

23,580 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: skillhub-manager
description: Manage and publish agent skills on SkillHub and ClawHub. Best for developers and operators who need a repeatable workflow to search skills, inspect packages, authenticate securely, and publish local skill folders to a registry.
version: 1.0.3
author: Agent Skill Master
license: MIT
metadata:
hermes:
tags: [skillhub, clawhub, skills, publishing, registry, authentication]
---

# SkillHub Manager

This skill gives you the ability to interact with a SkillHub ecosystem using the `clawhub` CLI. It supports previewing available skills and uploading/publishing new skills securely to the server.

## Overview

SkillHub instances host agents, profiles, and skills securely. As an AI Agent, you might be asked to publish a local folder as a skill, or to preview an existing skill to see what it does.

No need to write raw HTTP REST requests; SkillHub provides full compatibility with the `npx clawhub` toolchain.

Before using this skill for any live action, you must ask the user for the SkillHub address they want to use. Do not assume the default registry unless the user explicitly confirms it.

If the user has not provided a SkillHub address yet, ask for it first. After the user gives the address, use that address consistently for login, search, inspect, and publish commands.

## Mandatory Interaction Pattern

Before any registry action, follow this exact sequence:

1. Ask: `Please provide the SkillHub address you want me to use.`
2. Wait for the user's reply.
3. Repeat the address back to the user in a confirmation message.
4. State whether you will use plain `npx clawhub ...` or `CLAWHUB_REGISTRY=<address> npx clawhub ...`.
5. Only after that confirmation message may you run login, search, inspect, explore, or publish.

Example confirmation:
- `Confirmed. I will use SkillHub at https://your-registry.example and run subsequent clawhub commands with CLAWHUB_REGISTRY set to that address.`

If the user says to use the default hosted registry, confirm that explicitly before proceeding.

Never skip the repeat-back confirmation step.

## General Authentication & Environment

All SkillHub actions must point to the intended registry.

You must explicitly ask the user which SkillHub address to use before running any registry command.

Once the user provides the address:
- if it is the default hosted registry, you may use plain `npx clawhub <command>`
- if it is a custom or self-hosted registry, set `CLAWHUB_REGISTRY=<user-provided-url>` for every command

Examples:
- default registry: `npx clawhub <command>`
- custom registry: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub <command>`

Never silently pick a registry on behalf of the user.

**Is Login Required?**
- Viewing public skills: usually no login required.
- Publishing or interacting with private/team spaces: login required.

*If you need to login before publishing:*
- explicit token: `npx clawhub login --token <TOKEN>`
- custom registry plus token: `CLAW

README.md

# SkillHub Manager

English

SkillHub Manager helps agents and developers search, inspect, and publish skills through SkillHub compatible registries such as ClawHub. It is designed for repeatable registry workflows instead of ad hoc HTTP calls.

What it solves
- Publishes a local skill folder through the clawhub CLI
- Searches and previews registry-hosted skills
- Documents authentication patterns for token-based publishing
- Asks the user for the SkillHub address before touching any registry
- Keeps registry targeting explicit through environment variables

Who needs it
- Developers maintaining reusable skills
- Operators running a private SkillHub registry
- Agents that need a safe, documented publishing workflow

Key features
- Search and inspect commands for existing skills
- Token-based login guidance
- Publish workflow for local skill packages
- Mandatory SkillHub address confirmation before use
- Repeat-back confirmation of the chosen SkillHub address before execution
- Registry override support with CLAWHUB_REGISTRY

When to use
- When a user asks to submit or publish a skill
- When you need to inspect a skill before installing it
- When you need a repeatable SkillHub or ClawHub workflow

Main files
- SKILL.md: core operating instructions for the agent
- references/workflows.md: step by step command examples

Interaction rule
- Ask the user for the SkillHub address first
- Wait for the answer
- Repeat the address back for confirmation
- Then run the clawhub command with either the default registry or CLAWHUB_REGISTRY

中文

SkillHub Manager 用于帮助代理和开发者通过兼容 SkillHub 的注册表，例如 ClawHub，完成技能的搜索、预览和发布。它强调可重复执行的注册表工作流，而不是临时拼接 HTTP 请求。

解决的问题
- 通过 clawhub CLI 发布本地 skill 文件夹
- 搜索和预览注册表中的技能
- 记录基于 token 的认证方式
- 在执行任何注册表操作前先询问用户 SkillHub 地址
- 通过环境变量显式指定目标注册表

适用人群
- 维护可复用技能的开发者
- 运行私有 SkillHub 注册表的运维人员
- 需要安全、可审计发布流程的代理

关键能力
- 搜索与 inspect 工作流
- 基于 token 的登录说明
- 本地 skill 包发布流程
- 使用前必须确认 SkillHub 地址
- 执行前必须先复述并确认用户提供的地址
- 通过 CLAWHUB_REGISTRY 覆盖目标注册表

适用场景
- 用户要求提交或发布 skill
- 安装前需要先检查 skill 内容
- 需要一套可复用的 SkillHub 或 ClawHub 工作流

交互规则
- 先询问用户 SkillHub 地址
- 等待用户回复
- 复述该地址并再次确认
- 然后再执行默认 registry 或带 CLAWHUB_REGISTRY 的命令

_meta.json

{
  "ownerId": "kn73z9tzb0z9znh3pt9y6pp3zn8265vy",
  "slug": "skillhub-manager",
  "version": "1.0.3",
  "publishedAt": 1776589408581
}

references/workflows.md

# SkillHub Manager Workflows

The following are standard operational workflows for managing skills in SkillHub compatible registries.

Before running any workflow below, ask the user for the SkillHub address they want to use. Do not assume a registry in advance.

After the user provides the address:
- if the user confirms the default hosted registry, use plain `npx clawhub ...`
- if the user provides a custom or self-hosted SkillHub address, prepend `CLAWHUB_REGISTRY=<url>` to every command below

Mandatory preflight interaction:
1. Ask for the SkillHub address.
2. Wait for the reply.
3. Repeat the address back in a confirmation message.
4. State the exact command style you will use next.
5. Only then execute the command.

## 1. Publishing a Skill (Submit / Upload)
When asked to submit or publish a skill package or directory to SkillHub, use the `publish` command.

1. Ensure the target skill codebase is prepared inside a local folder such as `./my-skill`.
2. Ask the user which SkillHub address to use and wait for the answer.
3. Repeat the address back and confirm the exact command style you will use.
4. Validate whether you already have a working token:
```bash
npx clawhub whoami
```
5. If authentication is missing, log in with an API token:
```bash
npx clawhub login --token <TOKEN>
```
6. Run the publishing command:
```bash
# Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>
npx clawhub publish ./my-skill --slug my-skill --name "My Awesome Skill" --version 1.0.0
```
7. When targeting a custom or self-hosted registry, add the registry override:
```bash
CLAWHUB_REGISTRY=https://your-registry.example npx clawhub publish ./my-skill --slug my-skill --name "My Awesome Skill" --version 1.0.0
```
8. Verify the result with:
```bash
npx clawhub inspect my-skill
```

## 2. Previewing a Skill (Inspect)
When a user wants to preview or inspect a specific skill from the remote registry, use the `inspect` command to view its metadata.

```bash
npx clawhub inspect <skill-slug>
```

You can view recently updated skills via exploration:
```bash
npx clawhub explore --limit 10
```

## 3. Searching for a Skill
If a user asks what skills are available regarding a specific topic, use the `search` command.

```bash
npx clawhub search <query>
```

## 4. Practical Notes
- Always ask for the SkillHub address before login, search, inspect, explore, or publish.
- Always repeat the address back to the user before executing the first registry command.
- Use explicit `--slug`, `--name`, `--version`, and `--tags` values when publishing so the release is reproducible.
- Keep `README.md` and `SKILL.md` in sync before publishing.
- Prefer `npx clawhub whoami` before any publish attempt so you can fail fast on expired tokens.
- Use `CLAWHUB_REGISTRY` only after the user has provided a non-default registry.

skill-card.md

## Description:

Manage and publish agent skills on SkillHub and ClawHub. Best for developers and operators who need a repeatable workflow to search skills, inspect packages, authenticate securely, and publish local skill folders to a registry.

This skill is ready for commercial/non-commercial use.

## Publisher:

[codeblackhole1024](https://clawhub.ai/user/codeblackhole1024)

### License/Terms of Use:

MIT-0

## Use Case:

Developers, operators, and agents use this skill to search, inspect, authenticate with, and publish skills to SkillHub-compatible registries such as ClawHub through a repeatable CLI workflow.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can guide authenticated registry publishing with tokens and local skill files.

Mitigation: Use a least-privileged environment and confirm authentication state before publishing.

Risk: The skill uses unpinned `npx clawhub` CLI commands.

Mitigation: Use a vetted or pinned `clawhub` CLI version for publishing workflows.

Risk: The skill accepts custom registry URLs before login, search, inspect, or publish actions.

Mitigation: Verify the registry URL before sending credentials or source content.

## Reference(s):

- [SkillHub Manager Workflows](references/workflows.md)

## Skill Output:

**Output Type(s):** [guidance, shell commands, configuration]

**Output Format:** [Markdown with inline bash code blocks]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Prompts the user to confirm the target SkillHub registry before registry actions.]

## Skill Version(s):

1.0.3 (source: server release metadata and SKILL.md frontmatter)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.