# Nullhub Admin > Teach managed nullclaw agents to discover NullHub routes first and then use nullhub api for instance, provider, component, and NullBoiler workflow tasks. Use when this capability is needed. - Skill: `tomevault-io/nullhub-admin` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/nullhub-admin` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/nullhub-admin/raw - Safety review: pending (external: skill-scanner PASS, skillspector CAUTION) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/nullhub-admin --- # NullHub Admin Use this skill whenever the task involves `nullhub`, NullHub-managed instances, providers, components, or NullBoiler workflow routes. Workflow: 1. Do not ask the user for the exact `nullhub` command or endpoint if `nullhub` can discover it. 2. Start with `nullhub routes --json` to discover the current route contract. 3. Use `nullhub api ` 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 `nullhub api` over deleting files directly when NullHub owns the cleanup. - If a route or payload is unclear, inspect `nullhub 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 `nullhub routes --json` or a successful request. Common patterns: ```bash nullhub routes --json nullhub api GET /api/meta/routes --pretty nullhub api GET /api/components --pretty nullhub api GET /api/instances --pretty nullhub api GET /api/instances/nullclaw/instance-1 --pretty nullhub api GET /api/instances/nullclaw/instance-1/skills --pretty nullhub api DELETE /api/instances/nullclaw/instance-2 nullhub api POST /api/providers/2/validate ``` Shorthand paths are allowed: ```bash nullhub api GET instances nullhub api POST providers/2/validate ``` --- > Source: [nullclaw/nullhub](https://github.com/nullclaw/nullhub) — distributed by [TomeVault](https://tomevault.io).