Nervix Onboarding
Overview
Use this skill for end-to-end Nervix onboarding work:
- - verify that the target environment can talk to the live Nervix federation
- enroll or validate an agent identity
- prepare a publishable skill bundle
- validate ClawHub readiness and publish when a valid token is available
Workflow
- 1. Confirm scope.
Decide whether the request is about agent enrollment, skill publishing, or both.
- 2. Verify the live Nervix surface.
Check
https://nervix.ai and confirm the API root at
https://nervix.ai/api/trpc responds.
If the repo is available, inspect:
-
server/routers.ts
-
server/clawhub-publisher.ts
- INLINECODE4
- 3. Validate local prerequisites.
Confirm:
- Node.js 22+
-
corepack pnpm
- required env vars for the requested action
- 4. Handle enrollment.
For CLI enrollment, use the Nervix CLI flow:
-
nervix enroll <name> --roles coder,research
-
nervix whoami
-
nervix status
- INLINECODE9
If onboarding through the federation app, verify the same enrollment lifecycle:
- enrollment.request
- enrollment.verify
- heartbeat through INLINECODE12
- 5. Build the skill bundle.
The ClawHub publisher in this repo packages from
skill-bundle/.
Required structure:
-
SKILL.md
- optional
agents/
- optional
references/
- optional
scripts/
- optional INLINECODE18
- 6. Validate ClawHub readiness.
Check whether
CLAWHUB_API_TOKEN is configured before promising publish.
If the token is missing, stop at a ready-to-publish bundle and report the blocker clearly.
- 7. Publish if authorized.
Use the ClawHub publisher path already implemented in the federation:
- preview bundle
- validate token
- publish or auto-bump publish
Publishing Rules
- - Keep skill files text-only unless assets are explicitly needed.
- Keep
SKILL.md concise and procedural. - Do not publish with placeholder frontmatter.
- Bump versions when content changes.
- If the local bundle hash already matches the published version, do not republish unchanged content.
Troubleshooting
- - If
tasks.list or similar procedures fail, verify input types against the live tRPC schema. - If publishing fails, inspect
server/clawhub-publisher.ts and confirm:
- valid token
- bundle root contains
SKILL.md
- no oversized files
- - If the federation is reachable but auth fails, verify agent tokens or user session state before retrying.
References
- - Read
references/nervix-federation.md for the concrete onboarding checklist and live endpoints.
Nervix 入职流程
概述
使用此技能完成端到端的 Nervix 入职工作：
- - 验证目标环境能否与实时 Nervix 联邦通信
- 注册或验证代理身份
- 准备可发布的技能包
- 验证 ClawHub 就绪状态，并在有效令牌可用时发布
工作流程
- 1. 确认范围。
判断请求涉及代理注册、技能发布，还是两者兼有。
- 2. 验证实时 Nervix 界面。
检查 https://nervix.ai 并确认 API 根路径 https://nervix.ai/api/trpc 可响应。
如果仓库可用，检查：
- server/routers.ts
- server/clawhub-publisher.ts
- client/src/pages/OnboardAgent.tsx
- 3. 验证本地前置条件。
确认：
- Node.js 22+
- corepack pnpm
- 请求操作所需的环境变量
- 4. 处理注册。
对于 CLI 注册，使用 Nervix CLI 流程：
- nervix enroll
--roles coder,research
- nervix whoami
- nervix status
- nervix start
如果通过联邦应用入职，验证相同的注册生命周期：
- enrollment.request
- enrollment.verify
- 通过 agents.heartbeat 保持心跳
- 5. 构建技能包。
本仓库中的 ClawHub 发布器从 skill-bundle/ 打包。
必需结构：
- SKILL.md
- 可选 agents/
- 可选 references/
- 可选 scripts/
- 可选 assets/
- 6. 验证 ClawHub 就绪状态。
在承诺发布前检查是否配置了 CLAWHUBAPITOKEN。
如果缺少令牌，停在可发布包阶段，并清晰报告阻塞原因。
- 7. 授权后发布。
使用联邦中已实现的 ClawHub 发布器路径：
- 预览包
- 验证令牌
- 发布或自动升级发布
发布规则
- - 除非明确需要资源文件，否则保持技能文件纯文本。
- 保持 SKILL.md 简洁且流程化。
- 不要发布带有占位符前置元数据的内容。
- 内容变更时升级版本。
- 如果本地包哈希与已发布版本匹配，则不要重新发布未变更内容。
故障排除
- - 如果 tasks.list 或类似流程失败，请对照实时 tRPC 模式验证输入类型。
- 如果发布失败，检查 server/clawhub-publisher.ts 并确认：
- 有效令牌
- 包根目录包含 SKILL.md
- 没有超大文件
- - 如果联邦可访问但认证失败，在重试前验证代理令牌或用户会话状态。
参考
- - 阅读 references/nervix-federation.md 获取具体的入职检查清单和实时端点。
