docs(compat): document first-party publish token

Signed-off-by: XiaoSeS <87064762+XiaoSeS@users.noreply.github.com>

README.md

@@ -516,6 +516,7 @@ git clone https://github.com/anthropics/skills
 
 # ...and publish it into your private SkillHub registry
 export SKILLHUB_REGISTRY=https://skillhub.your-company.com
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 npx @astron-team/skillhub@latest publish ./skills/<category>/<skill-name>
 ```
 

README_zh.md

@@ -402,6 +402,7 @@ git clone https://github.com/anthropics/skills
 
 # ……并将其发布到你的私有 SkillHub 注册中心
 export SKILLHUB_REGISTRY=https://skillhub.your-company.com
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 npx @astron-team/skillhub@latest publish ./skills/<分类>/<技能名>
 ```
 

docs/openclaw-integration-en.md

@@ -118,12 +118,15 @@ npx clawhub list --help
 The ClawHub CLI `0.23.3` publishing protocol is not compatible with SkillHub. Use the first-party SkillHub CLI:
 
 ```bash
+export SKILLHUB_REGISTRY=https://skillhub.your-company.com
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 npx @astron-team/skillhub@latest publish ./my-skill --namespace global
 npx @astron-team/skillhub@latest publish ./my-skill --namespace my-space
 ```
 
 Notes:
 - Publishing requires an API Token with the `skill:publish` scope and permission in the target namespace.
+- `clawhub login` and the SkillHub CLI do not share credentials; set `SKILLHUB_TOKEN` separately for the first-party CLI.
 - The first-party CLI uses a separate namespace option and is not affected by canonical-slug delimiter ambiguity.
 
 ## API Endpoints

docs/openclaw-integration.md

@@ -118,12 +118,15 @@ npx clawhub list --help
 ClawHub CLI `0.23.3` 的发布协议与 SkillHub 不兼容。请使用第一方 SkillHub CLI：
 
 ```bash
+export SKILLHUB_REGISTRY=https://skillhub.your-company.com
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 npx @astron-team/skillhub@latest publish ./my-skill --namespace global
 npx @astron-team/skillhub@latest publish ./my-skill --namespace my-space
 ```
 
 说明：
 - 发布需要具有 `skill:publish` scope 的 API Token，以及目标 namespace 对应权限。
+- `clawhub login` 与 SkillHub CLI 不共享凭据；请为第一方 CLI 单独设置 `SKILLHUB_TOKEN`。
 - 第一方 CLI 使用独立 namespace 参数，不受 canonical slug 分隔符歧义影响。
 
 ## API 端点说明

docs/skillhub/en/faq.md

@@ -66,7 +66,9 @@ npx clawhub search email
 npx clawhub install my-skill
 
 # Publish a skill package (the ClawHub CLI publishing protocol is not compatible)
-SKILLHUB_REGISTRY=http://your-skillhub-host:8080 npx @astron-team/skillhub@latest publish ./my-skill
+export SKILLHUB_REGISTRY=http://your-skillhub-host:8080
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
+npx @astron-team/skillhub@latest publish ./my-skill
 ```
 
 ## Q: How do I configure HTTPS?

docs/skillhub/en/guide/skill-publish.md

@@ -59,6 +59,7 @@ Ensure skill package conforms to SkillHub specification:
 ```bash
 # Configure the SkillHub registry
 export SKILLHUB_REGISTRY=http://localhost:8080
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 
 # Publish to default namespace
 npx @astron-team/skillhub@latest publish ./my-skill

docs/skillhub/faq.md

@@ -66,7 +66,9 @@ npx clawhub search email
 npx clawhub install my-skill
 
 # 发布技能包（ClawHub CLI 的发布协议不兼容 SkillHub）
-SKILLHUB_REGISTRY=http://your-skillhub-host:8080 npx @astron-team/skillhub@latest publish ./my-skill
+export SKILLHUB_REGISTRY=http://your-skillhub-host:8080
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
+npx @astron-team/skillhub@latest publish ./my-skill
 ```
 
 ## Q: 如何配置 HTTPS？

docs/skillhub/guide/skill-publish.md

@@ -59,6 +59,7 @@ SkillHub 提供了类似 npm 的发布体验，但增加了企业级的权限控
 ```bash
 # 配置 SkillHub 注册中心
 export SKILLHUB_REGISTRY=http://localhost:8080
+export SKILLHUB_TOKEN=YOUR_API_TOKEN
 
 # 发布到默认命名空间
 npx @astron-team/skillhub@latest publish ./my-skill