← ClaudeAtlas

code-agent-deploylisted

Deploys a local project and returns the address it can be opened at. Identifies the project, makes it ready to deploy, packs the source and hands it to the deployment platform to build and run (no Docker needed on this computer), repairs and retries from what the server reports, and afterwards shows status and logs and rolls back. For anything reached through a URL - websites, web applications, backend API services. The user only needs a deploy key and never touches a server.
lageyun/web-deploy · ★ 2 · DevOps & Infrastructure · score 75
Install: claude install-skill lageyun/web-deploy
# WEB DEPLOY: the deployment skill ## Goal When the user says "deploy this project", take it from the local project to an address that opens, without making the user deal with Docker, servers or networking. The user only has to: 1. Run `appcli auth set-key` once in a terminal, the first time, and paste their own deploy key. They create it on the platform console's Deploy keys page (`/keys`); on a platform that is not open for registration an administrator issues it. 2. Confirm once the diff that makes the project ready to deploy. 3. On the first deployment, confirm which local file the runtime parameters are read from (when there are any). 4. On the first deployment, decide whether to migrate local data (asked only when local data is found; the default is no). Commands, manifest fields, output and error codes are defined in the [appcli reference](references/appcli-reference.md). **Language.** This skill is written in English; talk to the user in the language they use. The platform console is in Chinese, so its pages are named here by their path (`/keys`, `/plans`): name the page in the user's language and give the path. The questions and the report formats below are given in English; put them into the user's language as well. ## Rules that are never broken 1. Every deployment goes through the deployment platform, by running appcli. No SSH, no SCP, no direct connection to a server, no remote Docker. 2. Never read, print or ask for the deploy key. When it is missing, ask