setup-a0-cli
Install, connect or troubleshoot A0 CLI host access, local files and remote tools.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- setup-a0-cli
- triggers
- [ "install A0", "connect local files", "enable host connector", "A0 CLI setup", "host vs container" ]
- description
- Install, connect or troubleshoot A0 CLI host access, local files and remote tools.
03 SKILL.md 正文
A0 CLI Host Setup
a0 runs on the user's host machine; Agent Zero stays in Docker or its sandbox.
Keep The Conversation Short
- Match the user's brevity. For a brief question, reply with one short sentence and at most one command block.
- Give only the next useful step, then wait for the result. Do not dump installation, connection, fallback, troubleshooting, and success details into one response.
- Ask only for information needed now. For a fresh install, ask only which host OS they use. Ask about previous commands and errors only when they say they already tried or something failed.
- Do not add headings, checklists, expected-output prose, warnings, alternatives, or explanations unless they help with the user's current step or the user asks for detail.
Fresh Install
If the host OS is unknown, ask only:
Which computer are you installing it on: Windows, macOS, or Linux?
Once known, give the matching command and tell them to run a0 when it finishes.
macOS / Linux host terminal:
curl -LsSf https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.sh | sh
Windows PowerShell:
irm https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.ps1 | iex
If the user is inside /a0, docker exec, or another container shell, stop there: tell them to exit and run the installer in their normal computer terminal. Do not give container installation commands.
If a0 is not found after installation, ask them to open a new terminal and try a0 again.
Connect
Running a0 opens a host picker and discovers local Docker instances when possible. Tell the user to select the instance it finds.
If manual entry is needed:
- Use the exact URL the user currently uses to open Agent Zero, including its actual port.
- Never guess, prescribe, or describe any port as common or default. Do not turn a documentation example into the user's address.
- If the URL is unknown, ask the user to copy it from their browser or Docker's published-port mapping.
- A tunnel URL is pasted exactly as shown and does not need a port appended.
Mention AGENT_ZERO_HOST only if the user asks to prefill the picker. Use their exact known URL, never an invented example.
Troubleshoot Only When Needed
-
For a failed attempt, ask for the command, whether it ran on the host or in Docker, and the exact output.
-
If the installer URL is unreachable but
uvworks, use:uv tool install --upgrade git+https://github.com/agent0ai/a0-connector -
A connector
404usually means the running Agent Zero build lacks the bundled_a0_connector; tell the user to update Agent Zero. -
If discovery fails, ask for the exact Agent Zero URL or suggest a Flare Tunnel only then. The Flare Tunnel flow is
Settings > External Services > Flare Tunnel→Create Tunnel→ paste the shown HTTPS URL intoa0.
Response Examples
User: "How to enable host connector"
Which computer are you installing it on: Windows, macOS, or Linux?
User: "Linux"
Run this in your normal Linux terminal, then run
a0and select the Agent Zero instance it finds.curl -LsSf https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.sh | sh
User: "It asks for a custom URL"
Paste the exact URL you currently use to open Agent Zero in your browser, including its port.
04 同仓库更多 Skills
higgsfield-websites
Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1/R2/KV/DO/Containers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references/website-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references/app-flow.md), `game` (realtime multiplayer rooms — references/game-flow.md). Routes to the right flow; each carries its own rules and deploy/publish gates. Use when: "build me a website", "make a landing page", "create a web app", "build a SaaS dashboard / portfolio", "make me a game", "deploy this site", "publish". Also owns GAME ART: "make a spritesheet", "tileable texture", "animate a 3D character", game music/SFX — see the game-* references. NOT for: single image/video/audio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback