{"id":"b002fe95-e09f-4e5b-b224-cd5d2389c7dc","entityType":"agent","slug":"clawhub-codeblackhole1024-skillhub-manager","name":"SkillHub Manager","canonicalUrl":"https://www.xpersona.co/agent/clawhub-codeblackhole1024-skillhub-manager","canonicalPath":"/agent/clawhub-codeblackhole1024-skillhub-manager","generatedAt":"2026-10-11T07:39:34.294Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":null},"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,...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s177mgnzkjxtm73sg9mgwxwc9n83nygc:skillhub-manager","sourceUrl":"https://clawhub.ai/codeblackhole1024/skillhub-manager","homepage":"https://clawhub.ai/codeblackhole1024/skills/skillhub-manager","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/codeblackhole1024/skillhub-manager","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/codeblackhole1024/skills/skillhub-manager","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"SkillHub Manager technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":null},"stars":null,"forks":null,"downloads":1152,"packageName":null,"latestVersion":"1.0.3","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:05:09.998Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T05:05:10.011Z","lastCrawledAt":"2026-10-11T05:05:09.998Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T05:05:09.998Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.3","createdAt":"2026-04-19T09:03:28.581Z","changelog":"Add strict ask-confirm-execute SkillHub address workflow","fileCount":5,"zipByteSize":5890},{"version":"1.0.1","createdAt":"2026-04-19T08:39:22.410Z","changelog":"Fix registry guidance and add README","fileCount":4,"zipByteSize":3805},{"version":"1.0.0","createdAt":"2026-04-19T08:37:05.295Z","changelog":"Initial public release","fileCount":4,"zipByteSize":3482}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s177mgnzkjxtm73sg9mgwxwc9n83nygc:skillhub-manager","setupComplexity":"low","setupSteps":["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":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:39:34.294Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-codeblackhole1024-skillhub-manager/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":null},"readme":"Skill: SkillHub Manager\n\nOwner: codeblackhole1024\n\nSummary: Manage and publish agent skills on SkillHub and ClawHub. Best for developers and operators who need a repeatable workflow to search skills, inspect packages,...\n\nTags: authentication:1.0.3, clawhub:1.0.3, latest:1.0.3, publishing:1.0.3, registry:1.0.3, skillhub:1.0.3, skills:1.0.3\n\nVersion history:\n\nv1.0.3 | 2026-04-19T09:03:28.581Z | user\n\nAdd strict ask-confirm-execute SkillHub address workflow\n\nv1.0.1 | 2026-04-19T08:39:22.410Z | user\n\nFix registry guidance and add README\n\nv1.0.0 | 2026-04-19T08:37:05.295Z | user\n\nInitial public release\n\nArchive index:\n\nArchive v1.0.3: 5 files, 5890 bytes\n\nFiles: README.md (2761b), references/workflows.md (2901b), skill-card.md (1941b), SKILL.md (3564b), _meta.json (135b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: skillhub-manager\ndescription: 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.\nversion: 1.0.3\nauthor: Agent Skill Master\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [skillhub, clawhub, skills, publishing, registry, authentication]\n---\n\n# SkillHub Manager\n\nThis 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.\n\n## Overview\n\nSkillHub 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.\n\nNo need to write raw HTTP REST requests; SkillHub provides full compatibility with the `npx clawhub` toolchain.\n\nBefore 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.\n\nIf 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.\n\n## Mandatory Interaction Pattern\n\nBefore any registry action, follow this exact sequence:\n\n1. Ask: `Please provide the SkillHub address you want me to use.`\n2. Wait for the user's reply.\n3. Repeat the address back to the user in a confirmation message.\n4. State whether you will use plain `npx clawhub ...` or `CLAWHUB_REGISTRY=<address> npx clawhub ...`.\n5. Only after that confirmation message may you run login, search, inspect, explore, or publish.\n\nExample confirmation:\n- `Confirmed. I will use SkillHub at https://your-registry.example and run subsequent clawhub commands with CLAWHUB_REGISTRY set to that address.`\n\nIf the user says to use the default hosted registry, confirm that explicitly before proceeding.\n\nNever skip the repeat-back confirmation step.\n\n## General Authentication & Environment\n\nAll SkillHub actions must point to the intended registry.\n\nYou must explicitly ask the user which SkillHub address to use before running any registry command.\n\nOnce the user provides the address:\n- if it is the default hosted registry, you may use plain `npx clawhub <command>`\n- if it is a custom or self-hosted registry, set `CLAWHUB_REGISTRY=<user-provided-url>` for every command\n\nExamples:\n- default registry: `npx clawhub <command>`\n- custom registry: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub <command>`\n\nNever silently pick a registry on behalf of the user.\n\n**Is Login Required?**\n- Viewing public skills: usually no login required.\n- Publishing or interacting with private/team spaces: login required.\n\n*If you need to login before publishing:*\n- explicit token: `npx clawhub login --token <TOKEN>`\n- custom registry plus token: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub login --token <TOKEN>`\n- if the environment already provides `SKILLHUB_API_TOKEN`, `CLAWHUB_API_TOKEN`, or `CLAWHUB_TOKEN`, validate first with `npx clawhub whoami`\n- if no working token is available, ask the user for one before proceeding\n\n## Commands\n\nSee [references/workflows.md](references/workflows.md) for full syntax and step-by-step examples of:\n1. Publishing a skill (`npx clawhub publish`)\n2. Previewing and Inspecting a skill (`npx clawhub inspect`)\n3. Searching for skills (`npx clawhub search`)\n\nFile v1.0.3:README.md\n\n# SkillHub Manager\n\nEnglish\n\nSkillHub 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.\n\nWhat it solves\n- Publishes a local skill folder through the clawhub CLI\n- Searches and previews registry-hosted skills\n- Documents authentication patterns for token-based publishing\n- Asks the user for the SkillHub address before touching any registry\n- Keeps registry targeting explicit through environment variables\n\nWho needs it\n- Developers maintaining reusable skills\n- Operators running a private SkillHub registry\n- Agents that need a safe, documented publishing workflow\n\nKey features\n- Search and inspect commands for existing skills\n- Token-based login guidance\n- Publish workflow for local skill packages\n- Mandatory SkillHub address confirmation before use\n- Repeat-back confirmation of the chosen SkillHub address before execution\n- Registry override support with CLAWHUB_REGISTRY\n\nWhen to use\n- When a user asks to submit or publish a skill\n- When you need to inspect a skill before installing it\n- When you need a repeatable SkillHub or ClawHub workflow\n\nMain files\n- SKILL.md: core operating instructions for the agent\n- references/workflows.md: step by step command examples\n\nInteraction rule\n- Ask the user for the SkillHub address first\n- Wait for the answer\n- Repeat the address back for confirmation\n- Then run the clawhub command with either the default registry or CLAWHUB_REGISTRY\n\n中文\n\nSkillHub Manager 用于帮助代理和开发者通过兼容 SkillHub 的注册表，例如 ClawHub，完成技能的搜索、预览和发布。它强调可重复执行的注册表工作流，而不是临时拼接 HTTP 请求。\n\n解决的问题\n- 通过 clawhub CLI 发布本地 skill 文件夹\n- 搜索和预览注册表中的技能\n- 记录基于 token 的认证方式\n- 在执行任何注册表操作前先询问用户 SkillHub 地址\n- 通过环境变量显式指定目标注册表\n\n适用人群\n- 维护可复用技能的开发者\n- 运行私有 SkillHub 注册表的运维人员\n- 需要安全、可审计发布流程的代理\n\n关键能力\n- 搜索与 inspect 工作流\n- 基于 token 的登录说明\n- 本地 skill 包发布流程\n- 使用前必须确认 SkillHub 地址\n- 执行前必须先复述并确认用户提供的地址\n- 通过 CLAWHUB_REGISTRY 覆盖目标注册表\n\n适用场景\n- 用户要求提交或发布 skill\n- 安装前需要先检查 skill 内容\n- 需要一套可复用的 SkillHub 或 ClawHub 工作流\n\n交互规则\n- 先询问用户 SkillHub 地址\n- 等待用户回复\n- 复述该地址并再次确认\n- 然后再执行默认 registry 或带 CLAWHUB_REGISTRY 的命令\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn73z9tzb0z9znh3pt9y6pp3zn8265vy\",\n  \"slug\": \"skillhub-manager\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1776589408581\n}\n\nFile v1.0.3:references/workflows.md\n\n# SkillHub Manager Workflows\n\nThe following are standard operational workflows for managing skills in SkillHub compatible registries.\n\nBefore running any workflow below, ask the user for the SkillHub address they want to use. Do not assume a registry in advance.\n\nAfter the user provides the address:\n- if the user confirms the default hosted registry, use plain `npx clawhub ...`\n- if the user provides a custom or self-hosted SkillHub address, prepend `CLAWHUB_REGISTRY=<url>` to every command below\n\nMandatory preflight interaction:\n1. Ask for the SkillHub address.\n2. Wait for the reply.\n3. Repeat the address back in a confirmation message.\n4. State the exact command style you will use next.\n5. Only then execute the command.\n\n## 1. Publishing a Skill (Submit / Upload)\nWhen asked to submit or publish a skill package or directory to SkillHub, use the `publish` command.\n\n1. Ensure the target skill codebase is prepared inside a local folder such as `./my-skill`.\n2. Ask the user which SkillHub address to use and wait for the answer.\n3. Repeat the address back and confirm the exact command style you will use.\n4. Validate whether you already have a working token:\n   ```bash\n   npx clawhub whoami\n   ```\n5. If authentication is missing, log in with an API token:\n   ```bash\n   npx clawhub login --token <TOKEN>\n   ```\n6. Run the publishing command:\n   ```bash\n   # Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>\n   npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n7. When targeting a custom or self-hosted registry, add the registry override:\n   ```bash\n   CLAWHUB_REGISTRY=https://your-registry.example npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n8. Verify the result with:\n   ```bash\n   npx clawhub inspect my-skill\n   ```\n\n## 2. Previewing a Skill (Inspect)\nWhen a user wants to preview or inspect a specific skill from the remote registry, use the `inspect` command to view its metadata.\n\n```bash\nnpx clawhub inspect <skill-slug>\n```\n\nYou can view recently updated skills via exploration:\n```bash\nnpx clawhub explore --limit 10\n```\n\n## 3. Searching for a Skill\nIf a user asks what skills are available regarding a specific topic, use the `search` command.\n\n```bash\nnpx clawhub search <query>\n```\n\n## 4. Practical Notes\n- Always ask for the SkillHub address before login, search, inspect, explore, or publish.\n- Always repeat the address back to the user before executing the first registry command.\n- Use explicit `--slug`, `--name`, `--version`, and `--tags` values when publishing so the release is reproducible.\n- Keep `README.md` and `SKILL.md` in sync before publishing.\n- Prefer `npx clawhub whoami` before any publish attempt so you can fail fast on expired tokens.\n- Use `CLAWHUB_REGISTRY` only after the user has provided a non-default registry.\n\nFile v1.0.3:skill-card.md\n\n## Description:\n\nManage 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.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[codeblackhole1024](https://clawhub.ai/user/codeblackhole1024)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, 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.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can guide authenticated registry publishing with tokens and local skill files.\n\nMitigation: Use a least-privileged environment and confirm authentication state before publishing.\n\nRisk: The skill uses unpinned `npx clawhub` CLI commands.\n\nMitigation: Use a vetted or pinned `clawhub` CLI version for publishing workflows.\n\nRisk: The skill accepts custom registry URLs before login, search, inspect, or publish actions.\n\nMitigation: Verify the registry URL before sending credentials or source content.\n\n## Reference(s):\n\n- [SkillHub Manager Workflows](references/workflows.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Prompts the user to confirm the target SkillHub registry before registry actions.]\n\n## Skill Version(s):\n\n1.0.3 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers 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.\n\nArchive v1.0.1: 4 files, 3805 bytes\n\nFiles: README.md (2017b), references/workflows.md (2153b), SKILL.md (2247b), _meta.json (135b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: skillhub-manager\ndescription: 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.\nversion: 1.0.1\nauthor: Agent Skill Master\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [skillhub, clawhub, skills, publishing, registry, authentication]\n---\n\n# SkillHub Manager\n\nThis 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.\n\n## Overview\n\nSkillHub 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.\n\nNo need to write raw HTTP REST requests; SkillHub provides full compatibility with the `npx clawhub` toolchain.\n\n## General Authentication & Environment\n\nAll SkillHub actions must point to the intended registry.\n\nUse the default clawhub CLI target when the user does not specify a custom registry. Only set `CLAWHUB_REGISTRY` or pass `--registry <url>` when targeting a non-default or self-hosted SkillHub instance.\n\nExamples:\n- default registry: `npx clawhub <command>`\n- custom registry: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub <command>`\n\n**Is Login Required?**\n- Viewing public skills: usually no login required.\n- Publishing or interacting with private/team spaces: login required.\n\n*If you need to login before publishing:*\n- explicit token: `npx clawhub login --token <TOKEN>`\n- custom registry plus token: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub login --token <TOKEN>`\n- if the environment already provides `SKILLHUB_API_TOKEN`, `CLAWHUB_API_TOKEN`, or `CLAWHUB_TOKEN`, validate first with `npx clawhub whoami`\n- if no working token is available, ask the user for one before proceeding\n\n## Commands\n\nSee [references/workflows.md](references/workflows.md) for full syntax and step-by-step examples of:\n1. Publishing a skill (`npx clawhub publish`)\n2. Previewing and Inspecting a skill (`npx clawhub inspect`)\n3. Searching for skills (`npx clawhub search`)\n\nFile v1.0.1:README.md\n\n# SkillHub Manager\n\nEnglish\n\nSkillHub 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.\n\nWhat it solves\n- Publishes a local skill folder through the clawhub CLI\n- Searches and previews registry-hosted skills\n- Documents authentication patterns for token-based publishing\n- Keeps registry targeting explicit through environment variables\n\nWho needs it\n- Developers maintaining reusable skills\n- Operators running a private SkillHub registry\n- Agents that need a safe, documented publishing workflow\n\nKey features\n- Search and inspect commands for existing skills\n- Token-based login guidance\n- Publish workflow for local skill packages\n- Registry override support with CLAWHUB_REGISTRY\n\nWhen to use\n- When a user asks to submit or publish a skill\n- When you need to inspect a skill before installing it\n- When you need a repeatable SkillHub or ClawHub workflow\n\nMain files\n- SKILL.md: core operating instructions for the agent\n- references/workflows.md: step by step command examples\n\n中文\n\nSkillHub Manager 用于帮助代理和开发者通过兼容 SkillHub 的注册表，例如 ClawHub，完成技能的搜索、预览和发布。它强调可重复执行的注册表工作流，而不是临时拼接 HTTP 请求。\n\n解决的问题\n- 通过 clawhub CLI 发布本地 skill 文件夹\n- 搜索和预览注册表中的技能\n- 记录基于 token 的认证方式\n- 通过环境变量显式指定目标注册表\n\n适用人群\n- 维护可复用技能的开发者\n- 运行私有 SkillHub 注册表的运维人员\n- 需要安全、可审计发布流程的代理\n\n关键能力\n- 搜索与 inspect 工作流\n- 基于 token 的登录说明\n- 本地 skill 包发布流程\n- 通过 CLAWHUB_REGISTRY 覆盖目标注册表\n\n适用场景\n- 用户要求提交或发布 skill\n- 安装前需要先检查 skill 内容\n- 需要一套可复用的 SkillHub 或 ClawHub 工作流\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn73z9tzb0z9znh3pt9y6pp3zn8265vy\",\n  \"slug\": \"skillhub-manager\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1776587962410\n}\n\nFile v1.0.1:references/workflows.md\n\n# SkillHub Manager Workflows\n\nThe following are standard operational workflows for managing skills in SkillHub compatible registries.\n\nUse the default clawhub registry unless the user explicitly provides a custom registry URL. For self-hosted registries, prepend `CLAWHUB_REGISTRY=<url>` to the commands below.\n\n## 1. Publishing a Skill (Submit / Upload)\nWhen asked to submit or publish a skill package or directory to SkillHub, use the `publish` command.\n\n1. Ensure the target skill codebase is prepared inside a local folder such as `./my-skill`.\n2. Validate whether you already have a working token:\n   ```bash\n   npx clawhub whoami\n   ```\n3. If authentication is missing, log in with an API token:\n   ```bash\n   npx clawhub login --token <TOKEN>\n   ```\n4. Run the publishing command:\n   ```bash\n   # Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>\n   npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n5. When targeting a custom or self-hosted registry, add the registry override:\n   ```bash\n   CLAWHUB_REGISTRY=https://your-registry.example npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n6. Verify the result with:\n   ```bash\n   npx clawhub inspect my-skill\n   ```\n\n## 2. Previewing a Skill (Inspect)\nWhen a user wants to preview or inspect a specific skill from the remote registry, use the `inspect` command to view its metadata.\n\n```bash\nnpx clawhub inspect <skill-slug>\n```\n\nYou can view recently updated skills via exploration:\n```bash\nnpx clawhub explore --limit 10\n```\n\n## 3. Searching for a Skill\nIf a user asks what skills are available regarding a specific topic, use the `search` command.\n\n```bash\nnpx clawhub search <query>\n```\n\n## 4. Practical Notes\n- Use explicit `--slug`, `--name`, `--version`, and `--tags` values when publishing so the release is reproducible.\n- Keep `README.md` and `SKILL.md` in sync before publishing.\n- Prefer `npx clawhub whoami` before any publish attempt so you can fail fast on expired tokens.\n- Use `CLAWHUB_REGISTRY` only when the user actually wants a non-default registry.\n\nArchive v1.0.0: 4 files, 3482 bytes\n\nFiles: README.md (2017b), references/workflows.md (1595b), SKILL.md (2087b), _meta.json (135b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: skillhub-manager\ndescription: 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.\nversion: 1.0.0\nauthor: Agent Skill Master\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [skillhub, clawhub, skills, publishing, registry, authentication]\n---\n\n# SkillHub Manager\n\nThis 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.\n\n## Overview\n\nSkillHub 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.\n\nNo need to write raw HTTP REST requests; SkillHub provides full compatibility with the `npx clawhub` toolchain.\n\n## General Authentication & Environment\n\nAll SkillHub actions must point to the target registry. The default is `http://localhost:18081`. \n\nWhenever invoking `npx clawhub`, you MUST prefix the execution with the registry location:\n`CLAWHUB_REGISTRY=http://localhost:18081 npx clawhub <command>`\n\n**Is Login Required?**\n- Viewing public skills: No login necessary.\n- Publishing or interacting with private/team spaces: **Login Required!**\n\n*If you need to login before publishing:*\nIf the user provides an API_TOKEN, pass it like this:\n`CLAWHUB_REGISTRY=http://localhost:18081 npx clawhub login --token <TOKEN>`\nIf the user has pre-set the `$SKILLHUB_API_TOKEN` environment variable, you can use:\n`CLAWHUB_REGISTRY=http://localhost:18081 npx clawhub login --token $SKILLHUB_API_TOKEN`\nIf no token is provided, ask the user for their API token before proceeding.\n\n## Commands\n\nSee [references/workflows.md](references/workflows.md) for full syntax and step-by-step examples of:\n1. Publishing a skill (`npx clawhub publish`)\n2. Previewing and Inspecting a skill (`npx clawhub inspect`)\n3. Searching for skills (`npx clawhub search`)\n\nFile v1.0.0:README.md\n\n# SkillHub Manager\n\nEnglish\n\nSkillHub 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.\n\nWhat it solves\n- Publishes a local skill folder through the clawhub CLI\n- Searches and previews registry-hosted skills\n- Documents authentication patterns for token-based publishing\n- Keeps registry targeting explicit through environment variables\n\nWho needs it\n- Developers maintaining reusable skills\n- Operators running a private SkillHub registry\n- Agents that need a safe, documented publishing workflow\n\nKey features\n- Search and inspect commands for existing skills\n- Token-based login guidance\n- Publish workflow for local skill packages\n- Registry override support with CLAWHUB_REGISTRY\n\nWhen to use\n- When a user asks to submit or publish a skill\n- When you need to inspect a skill before installing it\n- When you need a repeatable SkillHub or ClawHub workflow\n\nMain files\n- SKILL.md: core operating instructions for the agent\n- references/workflows.md: step by step command examples\n\n中文\n\nSkillHub Manager 用于帮助代理和开发者通过兼容 SkillHub 的注册表，例如 ClawHub，完成技能的搜索、预览和发布。它强调可重复执行的注册表工作流，而不是临时拼接 HTTP 请求。\n\n解决的问题\n- 通过 clawhub CLI 发布本地 skill 文件夹\n- 搜索和预览注册表中的技能\n- 记录基于 token 的认证方式\n- 通过环境变量显式指定目标注册表\n\n适用人群\n- 维护可复用技能的开发者\n- 运行私有 SkillHub 注册表的运维人员\n- 需要安全、可审计发布流程的代理\n\n关键能力\n- 搜索与 inspect 工作流\n- 基于 token 的登录说明\n- 本地 skill 包发布流程\n- 通过 CLAWHUB_REGISTRY 覆盖目标注册表\n\n适用场景\n- 用户要求提交或发布 skill\n- 安装前需要先检查 skill 内容\n- 需要一套可复用的 SkillHub 或 ClawHub 工作流\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn73z9tzb0z9znh3pt9y6pp3zn8265vy\",\n  \"slug\": \"skillhub-manager\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1776587825295\n}\n\nFile v1.0.0:references/workflows.md\n\n# SkillHub Manager Workflows\n\nThe following are standard operational workflows for managing operations in a SkillHub Instance. You must always prepend `CLAWHUB_REGISTRY=http://localhost:18081` to route the OpenClaw commands to the user's specific backend.\n\n## 1. Publishing a Skill (Submit / Upload)\nWhen asked to *submit* or *publish* a skill package or directory to SkillHub, use the `publish` command.\n\n1. Ensure you have the target skill codebase prepared inside a local folder (e.g., `./my-skill`).\n2. Log into the registry using the API Token:\n   ```bash\n   CLAWHUB_REGISTRY=http://localhost:18081 npx clawhub login --token <TOKEN>\n   ```\n3. Run the publishing command:\n   ```bash\n   # Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>\n   CLAWHUB_REGISTRY=http://localhost:18081 npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n   *Note: For team spaces, use `--slug team-space--my-skill`*\n\n## 2. Previewing a Skill (Inspect)\nWhen a user wants to preview or inspect a specific skill from the remote registry, use the `inspect` command to view its metadata.\n\n```bash\nCLAWHUB_REGISTRY=http://localhost:18081 npx clawhub inspect <skill-slug>\n```\n\nYou can view the latest skills available on the hub via exploration:\n```bash\nCLAWHUB_REGISTRY=http://localhost:18081 npx clawhub explore --limit 10\n```\n\n## 3. Searching for a Skill\nIf a user asks what skills are available regarding a specific topic, use the `search` command.\n\n```bash\nCLAWHUB_REGISTRY=http://localhost:18081 npx clawhub search <query> --limit 5\n```","readmeExcerpt":"Skill: SkillHub Manager Owner: codeblackhole1024 Summary: Manage and publish agent skills on SkillHub and ClawHub. Best for developers and operators who need a repeatable workflow to search skills, inspect packages,... Tags: authentication:1.0.3, clawhub:1.0.3, latest:1.0.3, publishing:1.0.3, registry:1.0.3, skillhub:1.0.3, skills:1.0.3 Version history: v1.0.3 | 2026-04-19T09:03:28.581Z | user Add strict ask-confirm-","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"npx clawhub whoami"},{"language":"bash","snippet":"npx clawhub login --token <TOKEN>"},{"language":"bash","snippet":"# Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>\n   npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0"},{"language":"bash","snippet":"CLAWHUB_REGISTRY=https://your-registry.example npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0"},{"language":"bash","snippet":"npx clawhub inspect my-skill"},{"language":"bash","snippet":"npx clawhub inspect <skill-slug>"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: skillhub-manager\ndescription: 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.\nversion: 1.0.3\nauthor: Agent Skill Master\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [skillhub, clawhub, skills, publishing, registry, authentication]\n---\n\n# SkillHub Manager\n\nThis 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.\n\n## Overview\n\nSkillHub 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.\n\nNo need to write raw HTTP REST requests; SkillHub provides full compatibility with the `npx clawhub` toolchain.\n\nBefore 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.\n\nIf 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.\n\n## Mandatory Interaction Pattern\n\nBefore any registry action, follow this exact sequence:\n\n1. Ask: `Please provide the SkillHub address you want me to use.`\n2. Wait for the user's reply.\n3. Repeat the address back to the user in a confirmation message.\n4. State whether you will use plain `npx clawhub ...` or `CLAWHUB_REGISTRY=<address> npx clawhub ...`.\n5. Only after that confirmation message may you run login, search, inspect, explore, or publish.\n\nExample confirmation:\n- `Confirmed. I will use SkillHub at https://your-registry.example and run subsequent clawhub commands with CLAWHUB_REGISTRY set to that address.`\n\nIf the user says to use the default hosted registry, confirm that explicitly before proceeding.\n\nNever skip the repeat-back confirmation step.\n\n## General Authentication & Environment\n\nAll SkillHub actions must point to the intended registry.\n\nYou must explicitly ask the user which SkillHub address to use before running any registry command.\n\nOnce the user provides the address:\n- if it is the default hosted registry, you may use plain `npx clawhub <command>`\n- if it is a custom or self-hosted registry, set `CLAWHUB_REGISTRY=<user-provided-url>` for every command\n\nExamples:\n- default registry: `npx clawhub <command>`\n- custom registry: `CLAWHUB_REGISTRY=https://your-registry.example npx clawhub <command>`\n\nNever silently pick a registry on behalf of the user.\n\n**Is Login Required?**\n- Viewing public skills: usually no login required.\n- Publishing or interacting with private/team spaces: login required.\n\n*If you need to login before publishing:*\n- explicit token: `npx clawhub login --token <TOKEN>`\n- custom registry plus token: `CLAW"},{"path":"README.md","content":"# SkillHub Manager\n\nEnglish\n\nSkillHub 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.\n\nWhat it solves\n- Publishes a local skill folder through the clawhub CLI\n- Searches and previews registry-hosted skills\n- Documents authentication patterns for token-based publishing\n- Asks the user for the SkillHub address before touching any registry\n- Keeps registry targeting explicit through environment variables\n\nWho needs it\n- Developers maintaining reusable skills\n- Operators running a private SkillHub registry\n- Agents that need a safe, documented publishing workflow\n\nKey features\n- Search and inspect commands for existing skills\n- Token-based login guidance\n- Publish workflow for local skill packages\n- Mandatory SkillHub address confirmation before use\n- Repeat-back confirmation of the chosen SkillHub address before execution\n- Registry override support with CLAWHUB_REGISTRY\n\nWhen to use\n- When a user asks to submit or publish a skill\n- When you need to inspect a skill before installing it\n- When you need a repeatable SkillHub or ClawHub workflow\n\nMain files\n- SKILL.md: core operating instructions for the agent\n- references/workflows.md: step by step command examples\n\nInteraction rule\n- Ask the user for the SkillHub address first\n- Wait for the answer\n- Repeat the address back for confirmation\n- Then run the clawhub command with either the default registry or CLAWHUB_REGISTRY\n\n中文\n\nSkillHub Manager 用于帮助代理和开发者通过兼容 SkillHub 的注册表，例如 ClawHub，完成技能的搜索、预览和发布。它强调可重复执行的注册表工作流，而不是临时拼接 HTTP 请求。\n\n解决的问题\n- 通过 clawhub CLI 发布本地 skill 文件夹\n- 搜索和预览注册表中的技能\n- 记录基于 token 的认证方式\n- 在执行任何注册表操作前先询问用户 SkillHub 地址\n- 通过环境变量显式指定目标注册表\n\n适用人群\n- 维护可复用技能的开发者\n- 运行私有 SkillHub 注册表的运维人员\n- 需要安全、可审计发布流程的代理\n\n关键能力\n- 搜索与 inspect 工作流\n- 基于 token 的登录说明\n- 本地 skill 包发布流程\n- 使用前必须确认 SkillHub 地址\n- 执行前必须先复述并确认用户提供的地址\n- 通过 CLAWHUB_REGISTRY 覆盖目标注册表\n\n适用场景\n- 用户要求提交或发布 skill\n- 安装前需要先检查 skill 内容\n- 需要一套可复用的 SkillHub 或 ClawHub 工作流\n\n交互规则\n- 先询问用户 SkillHub 地址\n- 等待用户回复\n- 复述该地址并再次确认\n- 然后再执行默认 registry 或带 CLAWHUB_REGISTRY 的命令"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn73z9tzb0z9znh3pt9y6pp3zn8265vy\",\n  \"slug\": \"skillhub-manager\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1776589408581\n}"},{"path":"references/workflows.md","content":"# SkillHub Manager Workflows\n\nThe following are standard operational workflows for managing skills in SkillHub compatible registries.\n\nBefore running any workflow below, ask the user for the SkillHub address they want to use. Do not assume a registry in advance.\n\nAfter the user provides the address:\n- if the user confirms the default hosted registry, use plain `npx clawhub ...`\n- if the user provides a custom or self-hosted SkillHub address, prepend `CLAWHUB_REGISTRY=<url>` to every command below\n\nMandatory preflight interaction:\n1. Ask for the SkillHub address.\n2. Wait for the reply.\n3. Repeat the address back in a confirmation message.\n4. State the exact command style you will use next.\n5. Only then execute the command.\n\n## 1. Publishing a Skill (Submit / Upload)\nWhen asked to submit or publish a skill package or directory to SkillHub, use the `publish` command.\n\n1. Ensure the target skill codebase is prepared inside a local folder such as `./my-skill`.\n2. Ask the user which SkillHub address to use and wait for the answer.\n3. Repeat the address back and confirm the exact command style you will use.\n4. Validate whether you already have a working token:\n   ```bash\n   npx clawhub whoami\n   ```\n5. If authentication is missing, log in with an API token:\n   ```bash\n   npx clawhub login --token <TOKEN>\n   ```\n6. Run the publishing command:\n   ```bash\n   # Usage: npx clawhub publish <path> --slug <slug> --name <Title> --version <SemVer>\n   npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n7. When targeting a custom or self-hosted registry, add the registry override:\n   ```bash\n   CLAWHUB_REGISTRY=https://your-registry.example npx clawhub publish ./my-skill --slug my-skill --name \"My Awesome Skill\" --version 1.0.0\n   ```\n8. Verify the result with:\n   ```bash\n   npx clawhub inspect my-skill\n   ```\n\n## 2. Previewing a Skill (Inspect)\nWhen a user wants to preview or inspect a specific skill from the remote registry, use the `inspect` command to view its metadata.\n\n```bash\nnpx clawhub inspect <skill-slug>\n```\n\nYou can view recently updated skills via exploration:\n```bash\nnpx clawhub explore --limit 10\n```\n\n## 3. Searching for a Skill\nIf a user asks what skills are available regarding a specific topic, use the `search` command.\n\n```bash\nnpx clawhub search <query>\n```\n\n## 4. Practical Notes\n- Always ask for the SkillHub address before login, search, inspect, explore, or publish.\n- Always repeat the address back to the user before executing the first registry command.\n- Use explicit `--slug`, `--name`, `--version`, and `--tags` values when publishing so the release is reproducible.\n- Keep `README.md` and `SKILL.md` in sync before publishing.\n- Prefer `npx clawhub whoami` before any publish attempt so you can fail fast on expired tokens.\n- Use `CLAWHUB_REGISTRY` only after the user has provided a non-default registry."},{"path":"skill-card.md","content":"## Description:\n\nManage 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.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[codeblackhole1024](https://clawhub.ai/user/codeblackhole1024)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, 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.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can guide authenticated registry publishing with tokens and local skill files.\n\nMitigation: Use a least-privileged environment and confirm authentication state before publishing.\n\nRisk: The skill uses unpinned `npx clawhub` CLI commands.\n\nMitigation: Use a vetted or pinned `clawhub` CLI version for publishing workflows.\n\nRisk: The skill accepts custom registry URLs before login, search, inspect, or publish actions.\n\nMitigation: Verify the registry URL before sending credentials or source content.\n\n## Reference(s):\n\n- [SkillHub Manager Workflows](references/workflows.md)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, shell commands, configuration]\n\n**Output Format:** [Markdown with inline bash code blocks]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Prompts the user to confirm the target SkillHub registry before registry actions.]\n\n## Skill Version(s):\n\n1.0.3 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers 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."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1653,"uniquenessScore":36,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:05:10.011Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:39:34.294Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"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!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"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","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}