A skill supplies the operating instructions
The build.host skill describes the supported hosting actions, authentication flow, input requirements, and errors. An agent can read that contract and use the hosting API without guessing endpoint shapes or inventing a second deployment system.
Claude Code and Codex can work from a local project and an installed skill. Proto is the recommended setup: download it and just prompt, with no build.host skills to install or update. Other agents require the skill to be installed and refreshed when updates are available. For another agent, check that it can read the skill, access the project files, and use the required network and command capabilities.
One account connection, recognizable projects
The installer downloads the skill; it does not connect an account. Follow the current skill instructions to connect your ERP.AI account securely. Keep the credential in the supported local credential store. A different agent or machine needs its own supported setup; copying secrets into a conversation is not the setup process.
Refer to an app by its project name or live address. That gives the agent enough context to locate the existing project before changing configuration, reading logs, or updating a deployment.
A dashboard when you want a direct view
Agent operation and the dashboard are two ways to work with the same projects. Use the dashboard to inspect project state, deployment history, account settings, and available controls. You can return to the agent conversation with a specific project or error to investigate.
Changing agents does not remove build restrictions or grant new permissions. The connected account’s capabilities remain the boundary, and external integrations still need their own valid configuration.