菜单
Use when the user wants to install, upgrade, or bootstrap the ArchAgent CLI. Trigger phrases include "install archagent", "install the archagent CLI", "set up archagent", "upgrade archagent", "archagent not found", "archagent command not found", "install the CLI", "get archagent running".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | archagent-install |
| description | Use when the user wants to install, upgrade, or bootstrap the ArchAgent CLI. Trigger phrases include "install archagent", "install the archagent CLI", "set up archagent", "upgrade archagent", "archagent not found", "archagent command not found", "install the CLI", "get archagent running". |
| allowed-tools | ["Bash(archagent:*)","Bash(brew:*)","Bash(curl:*)","Bash(bash:*)","Bash(sh:*)","Bash(pwsh:*)","Bash(powershell:*)"] |
Install or upgrade the public archagent binary from Homebrew or GitHub Releases.
Check whether the CLI is already installed:
archagent --version
If this succeeds, record the version.
If the CLI is present and the user didn't ask to upgrade, confirm the version and stop.
If the CLI is missing or the user asked to upgrade, install it using the public distribution path:
brew install ArchAstro/tools/archagent
brew upgrade ArchAstro/tools/archagent
curl -fsSL https://raw.githubusercontent.com/ArchAstro/archagents/main/install.sh | bash
irm https://raw.githubusercontent.com/ArchAstro/archagents/main/install.ps1 | iex
Verify installation:
archagent --version
On failure, help troubleshoot the public install path:
brew is expected on Linux and some macOS setups; fall back to install.sh.Permission denied usually means they need --install-dir or a user-writable target directory.command not found: archagent after install usually means the install directory is not on PATH.On success, tell the user the CLI is ready and suggest they run archagent setup to install the Claude Code/Codex plugins, then archagent auth login <email> to authenticate.
The end-to-end playbook for helping an ArchAgents org scope, build, deploy, troubleshoot, and hand off an agent. Use when the customer asks "how do we start", "what's the plan", "how do I roll this out", "what should we build first", or at the beginning of a new support engagement.
Use when the user wants to embed an ArchAgent agent into Claude Code, asks about the active embed state, wants to refresh or stop the embed, or refers to working as a specific ArchAgent agent inside Claude Code. Trigger phrases include "embed agent", "act as this agent", "be this agent", "start embed", "sync embed", "stop embed", "which agent is embedded", and "use the active agent identity".
Use when the user wants to embed an ArchAgent agent into Codex, asks about the active embed state, wants to refresh or stop the embed, or refers to working as a specific ArchAgent agent inside Codex. Trigger phrases include "embed agent", "act as this agent", "be this agent", "start embed", "sync embed", "stop embed", "which agent is embedded", and "use the active agent identity".
Use when the user wants to create or edit an ArchAstro agent's config files before deployment, including AgentTemplate files, Script configs, custom tools, routines, and environment setup. Trigger phrases include "build this agent", "write the template", "create the scripts", "set up the routines", "author this agent config".
Use when the user wants to create or edit an ArchAstro agent's config files before deployment, including AgentTemplate files, Script configs, custom tools, routines, and environment setup. Trigger phrases include "build this agent", "write the template", "create the scripts", "set up the routines", "author this agent config".
Use when the user wants to authenticate with or log in to the ArchAstro developer platform, or when the CLI reports an authentication error. Trigger phrases include "authenticate archagent", "archagent auth login", "log in to archagent", "log in to archastro", "archagent not authenticated", "archagent auth status", "sign in to archagent".