nervix-onboarding
v1.0.0Use this skill when onboarding a new agent or operator into Nervix, verifying live federation prerequisites, enrolling through the Nervix flow, and preparing or publishing the related skill bundle to ClawHub.
Installation
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
-
Confirm scope. Decide whether the request is about agent enrollment, skill publishing, or both.
-
Verify the live Nervix surface. Check
https://nervix.aiand confirm the API root athttps://nervix.ai/api/trpcresponds. If the repo is available, inspect: server/routers.tsserver/clawhub-publisher.ts-
client/src/pages/OnboardAgent.tsx -
Validate local prerequisites. Confirm:
- Node.js 22+
corepack pnpm-
required env vars for the requested action
-
Handle enrollment. For CLI enrollment, use the Nervix CLI flow:
nervix enroll <name> --roles coder,researchnervix whoaminervix statusnervix start
If onboarding through the federation app, verify the same enrollment lifecycle:
- enrollment.request
- enrollment.verify
- heartbeat through agents.heartbeat
- 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
assets/ -
Validate ClawHub readiness. Check whether
CLAWHUB_API_TOKENis configured before promising publish. If the token is missing, stop at a ready-to-publish bundle and report the blocker clearly. -
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.mdconcise 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.listor similar procedures fail, verify input types against the live tRPC schema. - If publishing fails, inspect
server/clawhub-publisher.tsand 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.mdfor the concrete onboarding checklist and live endpoints.