How do I install the Nullhub Admin skill?

Run npx skillmds@latest add nullclaw/nullhub-admin in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Nullhub Admin skill do?

Teach managed nullclaw agents to discover NullHub routes first and then use nullhub api for instance, provider, component, and NullBoiler workflow tasks. It is listed under Web & Frontend on SkillMD.

Is Nullhub Admin safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Nullhub Admin?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Nullhub Admin free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Nullhub Admin?

nullclaw (@nullclaw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Nullhub Admin by nullclaw — Agent Skill

Name: Nullhub Admin
Rating: 4.2 (5 reviews)
Author: nullclaw

File contents

NullHub Admin

Use this skill whenever the task involves nullhub, NullHub-managed instances, providers, components, or NullBoiler workflow routes.

Workflow:

Do not ask the user for the exact nullhub command or endpoint if nullhub can discover it.
Start with nullhub routes --json to discover the current route contract.
Use nullhub api <METHOD> <PATH> for the actual operation.
Prefer a read operation first unless the user already gave a precise destructive intent.
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:

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:

nullhub api GET instances
nullhub api POST providers/2/validate

Frequently asked questions

Nullhub Admin