axi

Name: axi
Author: MoizIbnYousaf

27stars5forks

How to install axi?

moizibnyousaf/marketing-cli/axi

$npx -y skills add MoizIbnYousaf/marketing-cli --skill axi

Installs into the current project.

Summary

Agent eXperience Interface (AXI) router — the main entry point for agent-ergonomic CLIs. Use whenever the agent needs GitHub, browser automation, human review, quota routing, Slack, Notion, AWS/Docker/K8s, databases, or any AXI-catalog tool; when choosing AXI vs MCP vs raw CLI; w

Files · 1

View on GitHub

SKILL.md

1	# /axi — Agent eXperience Interface Router
2
3	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](https://axi.md), [kunchenguid/axi](https://github.com/kunchenguid/axi)).
4
5	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.
6
7	## North Star
8
9	\| Depth \| File \|
10	\|---\|---\|
11	\| 10 principles (full spec) \| [rules/principles.md](rules/principles.md) \|
12	\| Official + community catalog \| [rules/catalog.md](rules/catalog.md) \|
13	\| AXI vs MCP vs raw CLI vs mktg tools \| [rules/prefer-axi.md](rules/prefer-axi.md) \|
14	\| Build / review an AXI \| [rules/build.md](rules/build.md) \|
15	\| Benchmark numbers \| [rules/benchmarks.md](rules/benchmarks.md) \|
16	\| Upstream build-skill snapshot \| [references/upstream-axi-skill.md](references/upstream-axi-skill.md) \|
17
18	## Workflow (escalation)
19
20	0. Unclear — User wants "the right tool." Detect domain → route via the table. Explain out loud.
21	1. Use — An AXI exists for the domain. Prefer `npx -y <axi> …` (zero global install). Fall back to global binary if already on PATH.
22	2. Ambient — Repeated sessions in one domain → suggest `<axi> setup hooks` (SessionStart) after explicit user opt-in.
23	3. Build / review — Designing an agent-facing CLI → load [rules/principles.md](rules/principles.md) + [rules/build.md](rules/build.md). Do not invent a parallel MCP server first.
24	4. Missing AXI — No catalog entry → prefer the least-bad existing path (mktg skill, raw CLI, MCP) per [rules/prefer-axi.md](rules/prefer-axi.md), and offer to scaffold a new AXI.
25
26	## On Activation (every time)
27
28	1. Restate the domain in one sentence ("You need GitHub PR/CI triage" / "You need live browser extraction").
29	2. Probe availability (non-blocking):
30	- `which gh-axi chrome-devtools-axi 2>/dev/null; npx -y gh-axi --version 2>/dev/null \| head -1`
31	- Optional: `mktg doctor --json --fields checks` and note `cli-gh`, `cli-gh-axi`, `cli-chrome-devtools-axi`.
32	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."
33	4. Prefer content-first invocation: run the AXI with no args once to see live state + `help[]` next steps, then follow those templates.
34	5. If the user is building a CLI for agents → skip catalog routing; open principles + build rules.
35	6. Never silently fall back to MCP when an AXI exists for that domain.
36
37	## AXI Routing Table
38
39	\| Need \| AXI \| Install / run \| Layer \|
40	\|---\|---\|---\|---\|
41	\| GitHub issues, PRs, CI runs, releases, secrets, projects \| `gh-axi` \| `npx -y gh-axi` (needs `gh auth login`) \| Official \|
42	\| Browse, click, fill, extract, tables, Lighthouse \| `chrome-devtools-axi` \| `npx -y chrome-devtools-axi` \| Official \|
43	\| Human review of HTML artifacts (annotate → agent feedback) \| `lavish-axi` \| `npx skills add kunchenguid/lavish-axi` / see catalog \| Official \|
44	\| Local Claude/Codex/Cursor/Copilot/Grok quota windows \| `quota-axi` \| see [rules/catalog.md](rules/catalog.md) \| Official \|
45	\| Jujutsu history \| `jj-axi` \| community \| VCS \|
46	\| npm registry inspect \| `npm-axi` \| community \| Packages \|
47	\| SQLite inspect / capped queries \| `sqlite-axi` \| community \| Data \|
48	\| Slack read/search/draft \| `slack-axi` \| community \| Comms \|
49	\| Gmail/Calendar/Docs/Drive/Slides (draft-only mail) \| `gws-axi` \| community \| Workspace \|
50	\| Harvest time tracking \| `harvest-axi` \| community \| Ops \|
51	\| Spec-driven agent workflow (AXI-in-skill demo) \| `specops` \| community \| Process \|
52	\| Git-backed record sheets \| `gitsheets-axi` \| community \| Data \|
53	\| Metabase SQL/MBQL \| `metabase-axi` \| community \| Analytics \|
54	\| Otter.ai transcripts \| `otter-axi` \| community \| Meetings \|
55	\| Notion pages/databases \| `notion-axi` \| community \| Docs \|
56	\| ClickUp tasks \| `clickup-axi` \| community \| Tasks \|
57	\| Databricks jobs/runs \| `databricks-axi` \| community \| Data \|
58	\| AWS host/deploy \| `aws-axi` \| community \| Cloud \|
59	\| Docker app lifecycle \| `docker-axi` \| community \| Cloud \|
60	\| DynamoDB \| `dynamodb-axi` \| community \| Data \|
61	\| PostgreSQL \| `pg-axi` \| community \| Data \|
62	\| MongoDB \| `mongodb-axi` \| c

People who liked this also viewed

6 picks

Type

axi

27stars5forks

View on GitHub

How to install axi?

moizibnyousaf/marketing-cli/axi

$npx -y skills add MoizIbnYousaf/marketing-cli --skill axi

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /axi — Agent eXperience Interface Router
2
3	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](https://axi.md), [kunchenguid/axi](https://github.com/kunchenguid/axi)).
4
5	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.
6
7	## North Star
8
9	\| Depth \| File \|
10	\|---\|---\|
11	\| 10 principles (full spec) \| [rules/principles.md](rules/principles.md) \|
12	\| Official + community catalog \| [rules/catalog.md](rules/catalog.md) \|
13	\| AXI vs MCP vs raw CLI vs mktg tools \| [rules/prefer-axi.md](rules/prefer-axi.md) \|
14	\| Build / review an AXI \| [rules/build.md](rules/build.md) \|
15	\| Benchmark numbers \| [rules/benchmarks.md](rules/benchmarks.md) \|
16	\| Upstream build-skill snapshot \| [references/upstream-axi-skill.md](references/upstream-axi-skill.md) \|
17
18	## Workflow (escalation)
19
20	0. Unclear — User wants "the right tool." Detect domain → route via the table. Explain out loud.
21	1. Use — An AXI exists for the domain. Prefer `npx -y <axi> …` (zero global install). Fall back to global binary if already on PATH.
22	2. Ambient — Repeated sessions in one domain → suggest `<axi> setup hooks` (SessionStart) after explicit user opt-in.
23	3. Build / review — Designing an agent-facing CLI → load [rules/principles.md](rules/principles.md) + [rules/build.md](rules/build.md). Do not invent a parallel MCP server first.
24	4. Missing AXI — No catalog entry → prefer the least-bad existing path (mktg skill, raw CLI, MCP) per [rules/prefer-axi.md](rules/prefer-axi.md), and offer to scaffold a new AXI.
25
26	## On Activation (every time)
27
28	1. Restate the domain in one sentence ("You need GitHub PR/CI triage" / "You need live browser extraction").
29	2. Probe availability (non-blocking):
30	- `which gh-axi chrome-devtools-axi 2>/dev/null; npx -y gh-axi --version 2>/dev/null \| head -1`
31	- Optional: `mktg doctor --json --fields checks` and note `cli-gh`, `cli-gh-axi`, `cli-chrome-devtools-axi`.
32	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."
33	4. Prefer content-first invocation: run the AXI with no args once to see live state + `help[]` next steps, then follow those templates.
34	5. If the user is building a CLI for agents → skip catalog routing; open principles + build rules.
35	6. Never silently fall back to MCP when an AXI exists for that domain.
36
37	## AXI Routing Table
38
39	\| Need \| AXI \| Install / run \| Layer \|
40	\|---\|---\|---\|---\|
41	\| GitHub issues, PRs, CI runs, releases, secrets, projects \| `gh-axi` \| `npx -y gh-axi` (needs `gh auth login`) \| Official \|
42	\| Browse, click, fill, extract, tables, Lighthouse \| `chrome-devtools-axi` \| `npx -y chrome-devtools-axi` \| Official \|
43	\| Human review of HTML artifacts (annotate → agent feedback) \| `lavish-axi` \| `npx skills add kunchenguid/lavish-axi` / see catalog \| Official \|
44	\| Local Claude/Codex/Cursor/Copilot/Grok quota windows \| `quota-axi` \| see [rules/catalog.md](rules/catalog.md) \| Official \|
45	\| Jujutsu history \| `jj-axi` \| community \| VCS \|
46	\| npm registry inspect \| `npm-axi` \| community \| Packages \|
47	\| SQLite inspect / capped queries \| `sqlite-axi` \| community \| Data \|
48	\| Slack read/search/draft \| `slack-axi` \| community \| Comms \|
49	\| Gmail/Calendar/Docs/Drive/Slides (draft-only mail) \| `gws-axi` \| community \| Workspace \|
50	\| Harvest time tracking \| `harvest-axi` \| community \| Ops \|
51	\| Spec-driven agent workflow (AXI-in-skill demo) \| `specops` \| community \| Process \|
52	\| Git-backed record sheets \| `gitsheets-axi` \| community \| Data \|
53	\| Metabase SQL/MBQL \| `metabase-axi` \| community \| Analytics \|
54	\| Otter.ai transcripts \| `otter-axi` \| community \| Meetings \|
55	\| Notion pages/databases \| `notion-axi` \| community \| Docs \|
56	\| ClickUp tasks \| `clickup-axi` \| community \| Tasks \|
57	\| Databricks jobs/runs \| `databricks-axi` \| community \| Data \|
58	\| AWS host/deploy \| `aws-axi` \| community \| Cloud \|
59	\| Docker app lifecycle \| `docker-axi` \| community \| Cloud \|
60	\| DynamoDB \| `dynamodb-axi` \| community \| Data \|
61	\| PostgreSQL \| `pg-axi` \| community \| Data \|
62	\| MongoDB \| `mongodb-axi` \| c

People who liked this also viewed

6 picks

Type