Nullhubx Admin

Use this skill whenever the task involves nullhubx, NullHubX-managed instances, providers, components, or orchestration routes.

Workflow:

1. Do not ask the user for the exact nullhubx command or endpoint if nullhubx can discover it.
2. Start with nullhubx routes --json to discover the current route contract.
3. Use nullhubx api <METHOD> <PATH> for the actual operation.
4. Prefer a read operation first unless the user already gave a precise destructive intent.
5. After a mutation, verify with a follow-up GET.

Rules:

• Prefer nullhubx api over deleting files directly when NullHubX owns the cleanup.
• If a route or payload is unclear, inspect nullhubx routes --json again instead of guessing or asking the user for syntax.
• Use --pretty for user-facing inspection output.
• Use --body or --body-file for JSON request bodies.
• If path segments come from arbitrary ids or names, percent-encode them before building the request path.
• Do not claim a route exists until it is confirmed by or a successful request.