axi

/axi — Agent eXperience Interface Router

AXI is not a protocol. It is 10 design principles for agent-ergonomic CLIs that beat both raw CLI and MCP on success, cost, duration, and turns (axi.md, kunchenguid/axi).

This skill is the main router for the AXI catalog (official + community). It picks the right AXI, installs/runs it agent-first (npx -y <axi>), and teaches the principles when you build or review agent-facing CLIs.

North Star

Depth	File
10 principles (full spec)	rules/principles.md
Official + community catalog	rules/catalog.md
AXI vs MCP vs raw CLI vs mktg tools	rules/prefer-axi.md
Build / review an AXI	rules/build.md
Benchmark numbers	rules/benchmarks.md
Upstream build-skill snapshot	references/upstream-axi-skill.md

Workflow (escalation)

1. Unclear — User wants "the right tool." Detect domain → route via the table. Explain out loud.
2. Use — An AXI exists for the domain. Prefer npx -y <axi> … (zero global install). Fall back to global binary if already on PATH.
3. Ambient — Repeated sessions in one domain → suggest <axi> setup hooks (SessionStart) after explicit user opt-in.
4. Build / review — Designing an agent-facing CLI → load rules/principles.md + rules/build.md. Do not invent a parallel MCP server first.
5. Missing AXI — No catalog entry → prefer the least-bad existing path (mktg skill, raw CLI, MCP) per rules/prefer-axi.md, and offer to scaffold a new AXI.

On Activation (every time)

1. Restate the domain in one sentence ("You need GitHub PR/CI triage" / "You need live browser extraction").
2. Probe availability (non-blocking):
   • which gh-axi chrome-devtools-axi 2>/dev/null; npx -y gh-axi --version 2>/dev/null | head -1
   • Optional: mktg doctor --json --fields checks and note cli-gh, cli-gh-axi, cli-chrome-devtools-axi.
3. Route via the AXI Routing Table. Always say why: "I'm using gh-axi instead of raw gh / GitHub MCP because AXI wins on cost and success for GitHub tasks."
4. Prefer content-first invocation: run the AXI with no args once to see live state + help[] next steps, then follow those templates.
5. If the user is building a CLI for agents → skip catalog routing; open principles + build rules.
6. Never silently fall back to MCP when an AXI exists for that domain.