anyhost

name	anyhost
description	Use inside an external user's application repository to deploy or productionize an AI-built app with Anyhost: connect GitHub, configure environments, manage env/secrets, provision managed services, deploy, verify health/logs, and return dev/prod URLs.

Anyhost Production Skill

Anyhost is the production cloud for AI-built apps. This skill is for the user's app repository, not for developing the Anyhost product.

Use this skill when the user asks to:

• deploy an app with Anyhost
• make an AI-built app production-ready
• connect a repo to Anyhost
• set up dev/prod environments
• add or verify managed Postgres, Redis, or object storage
• configure runtime env vars or secrets
• inspect Anyhost context, logs, health, URLs, or deployment status
• deploy to dev or prod
• debug a production issue using Anyhost context
• prepare export, handoff, or portability information

Start Here

1. Read references/cli.md.
2. Install or verify the Anyhost CLI.
3. Authenticate and link the user's repository when Anyhost state or deployment is needed.
4. Read .anyhost/context.json through anyhost context.
5. Select only the references needed for the task:
   • Repository binding, commands, auth: references/cli.md
   • Context file and API contract: references/context.md
   • Dev/prod separation: references/environments.md
   • Env vars, secrets, Postgres, Redis, storage: references/managed-services.md
   • Build/deploy flow: references/deploy.md
   • Safety and launch verification: references/production-checks.md
   • Logs, health, debugging, incident context: references/ops-context.md
   • Ownership, export, portability: references/export-portability.md
6. If deployment state, managed resources, or production evidence materially changes, read .agents/specs/artifacts.md and write a deployment report.

Core Rules

• Work in the user's current app repo.
• Treat .anyhost/context.json as Anyhost product authority.
• Prefer CLI commands over direct HTTP endpoints.
• Do not invent resources, credentials, or provider state.
• Never commit .anyhost/, .env, secrets, tokens, or provider credentials.
• Do not reveal secrets unless the user explicitly needs the raw value.
• Do not deploy production without explicit user confirmation.
• Keep provider details secondary. Report app URL, environment, health, logs, resources, and risk first.

Default Flow

1. Inspect repo and git status.
2. Install/verify CLI.
3. anyhost login
4. anyhost setup-agent
5. anyhost context
6. Verify repository, workspace, project, environments, resources, and permissions.
7. Prepare app build/runtime config.
8. Configure env/secrets and request/wait for managed services as needed.
9. Run local checks.
10. Commit and push deployable changes.
11. anyhost deploy -e dev
12. anyhost context
13. Verify URL, health, logs, and resources.
14. Ask before production.
15. anyhost deploy -e prod --yes
16. Report status, URLs, verification, risks, and next steps.