Plugin skills
The 8 natural-language skills, auto-routing hooks, and the safety-guard table
Come to this page to look up the exact skill names, routing rules, and safety guards of the axhub plugin. The plugin is a thin routing layer that turns Korean and English natural language into axhub CLI commands inside Claude Code (terminal and desktop app) — all decision and execution logic lives in ax-hub-cli (the axhub binary), while the plugin connects your intent to the right skill and takes care of safety guards like preview and confirmation. The current surface is 8 natural-language skills plus auto-routing hooks. For installation and a first walkthrough, see the Ask in plain words guide.
The plugin requires CLI v0.20.0 or newer. If the CLI is missing or too old, skills stop and guide you through installation or upgrade first.
The 8 skills
Natural language is the primary path — just say what you want and the request routes to the right skill. When you want to be explicit, invoke a skill directly as a slash command: /axhub:<skill-name>.
| Skill | What it does | Typical phrases |
|---|---|---|
onboarding | First-time setup — CLI install, login, git/node checks, GitHub App, and MCP connection, in order | "set me up", "getting started" |
bootstrap | Create a brand-new app from a template in an empty folder — app, repository, and first deploy in one pass | "I want to create an app on axhub", "create a new app" |
import | Bring an existing local app (non-empty folder) into axhub and prepare its first deploy | "put this folder on axhub", "deploy my existing app" |
development | Add or change features of an existing axhub app — real-data (connector/table) screens, CRUD, UI/API work | "add search to my todo app", "build a dashboard from my data" |
deploy | Redeploy the current branch of a connected app and track status — preview → confirm → execute → verify | "deploy", "ship it again" |
diagnosis | Read-only diagnosis of a failed deployment — never redeploys or rolls back | "why did my deploy fail?", "just find the cause" |
clarity | Exact CLI operations — logs, env vars, rollback, tables, connectors, GitHub reconnect, app deletion | explicit requests like "use axhub clarity to show logs" |
update | Check and apply axhub CLI/plugin updates | "is axhub up to date?", "update axhub" |
The per-command slash set from earlier versions (/axhub:apps, /axhub:status, /axhub:logs, …) and the quality agents have been consolidated into these 8 skills. Only skill-name slashes (such as /axhub:deploy) exist today.
Auto-routing hooks
The plugin ships hooks that route requests to the right skill. Nothing to configure.
- Session start — offers a CLI/plugin update check once every 24 hours (disable with
AXHUB_NO_AUTO_UPDATE), resumes a pending onboarding MCP step, and on Windows explains the Git Bash execution contract. - Prompt routing — freshness/update wording routes to
updatefirst; bringing an existing app routes toimport; GitHub reconnect/device-code wording routes to theclarityauth flow; "check status / continue" wording resumes the in-flightbootstrap/deployflow.
Safety guards
- Hard-to-undo actions (deploy, delete, …) show a preview of what will happen and ask for one more confirmation. At the CLI level, mutating commands default to dry-run and require
--execute. - Success is evidence-based — a deploy counts as done only after the deployment record verifies (
axhub deploy verify), not when the command exits. - Secrets are collected without exposing them on screen or in command history.
- Deploy, recover, and rollback always confirm which app and which tenant first.
diagnosisis read-only and never mutates state while investigating.