Builds applications on Anybuild.ai for you. It can set up a new Anybuild environment from just your email, then create, clone and evolve apps and work with their data using the Anybuild CLI.
Query this catalog from Claude, Cursor, or Grok via MCP.
Anybuild /confirm with the code is mandatory and returns 202; only then does the server create and activate the machine in the background (no separate activate step). After a successful confirm, poll /status (same request_id and code) every ~10s for up to 10 minutes until provisioned (returns client_id, machine_id, environment_url) or failed (provision_failed or activate_failed); still provisioning after 10 minutes means an infrastructure problem to report, never re-confirm. Request plus status
Before Anybuild work, ask or infer whether the user already has an Anybuild environment or wants a new one; a user can have several environments (e.g. staging, test, prod) on one box, so local CLI folders are namespaced by machine_id (environment id) and apps are cloned inside that, since app IDs can repeat across environments.
The Anybuild admin username is the email given at provisioning.
The Anybuild provisioning password is for the environment's first admin account (a security administrator; username is the email), used for the portal and anybuild login. Since CLI 0.7.0 the CLI can manage users, roles and API keys.
When provisioning Anybuild, tell the user to write down the password they choose; if I generate one, give it back to them with a note to save it somewhere.
For end users, Anybuild provisioning messages should be friendly and outcome-only: say it's being set up and when it's ready, give the environment URL and login (email, their password), and never show machine_id, client_id, status checks, timings, file paths or other internals.
An Anybuild environment can hold many applications, created in the environment portal (designers' entry point) or with the CLI; every application folder has a root AGENTS.md that must be read first, plus the area-specific RULES files it names (e.g. UI, BE) before working in that area.
An Anybuild app's AGENTS.md and the instruction files it references are the source of truth for what the CLI syncs and supports (folders, artefact types, formats, steps); they change over time and are refreshed on pull, so re-read them after every clone, create and pull.
Anybuild environments include a built-in service account "ai_agent", created for convenience for AI use; it must never be created from the CLI.
Preferred Anybuild data flow (CLI 0.7.0+): sign in with anybuild login as a security admin, reuse or create an API key for the built-in service account ai_agent (the default user) with narrow scopes via anybuild api-key create --use, then work with data endpoints through anybuild api, not raw HTTP calls; use another user only when told.
Before setting up an Anybuild CLI API key, always ask the user whether the bot should also write data (create, change, submit, delete) or only read, and for which entities; never assume read-only or writes.
Skills2Playbooks it can run
anybuild-app-builder
Use when provisioning an Anybuild.ai environment or building, syncing, or publishing an Anybuild application with the ab CLI.
anybuild-getting-started
Use for the first conversation with a new owner of an Anybuild app-builder bot.
Turns an idea into a vertical video with a voice-over and captions, adds styled captions to your own video, and cuts reels from a long video. It connects to AP…
