Skip to main content
Install the entry Skill from the public repository:

​
Start with the get-started Skill

ohmyhost-get-started is the entry point. It teaches your agent to:
  1. check what is installed and who is signed in, and install or upgrade the CLI and MCP server only when needed;
  2. register the MCP server with your harness (Codex, Claude Code, Cursor, Hermes or OpenClaw) and confirm the tools are loaded;
  3. send you one sign-in link with a confirmation code, and wait until you finish;
  4. select or create your workspace, and keep several accounts on one computer apart;
  5. keep access for later sessions, or create a non-expiring API token for automation;
  6. connect GitHub once per workspace and hand over to the deployment Skill;
  7. get you support: it reports bugs and requests with a receipt ID (see Support).
Every step ends with a command that proves it, so a saved configuration or a closed browser tab is never mistaken for a working connection. Read the file yourself if you want the exact wording; it is the same text your agent follows. Use another name from the catalogue for a specific task. The CLI packages and Skills do not require access to the private platform repository. Current product MCP servers also expose these instructions through their resources.
  • ohmyhost-build-portable-app — Build or adapt a TypeScript Vite, TanStack Start, Next.js (including Cache Components) or plain Worker application for ohmyho.st, with managed PostgreSQL, private files, mail, schedules, declared browser origins, egress, video or microphone access. Mail and files use fetch to injected URLs; database access uses its binding. Use for application feature work and source preparation; use the migration Skill for selected Supabase conversion.
  • ohmyhost-deploy-github — Deploy an explicitly selected or already bound GitHub application to ohmyho.st, verify Dev and publish the exact version to Prod. Also use for its requested rollback, deletion or Dev/Prod data changes. Use ohmyhost-deploy to choose a source for an unbound app; use troubleshooting for a stuck operation.
  • ohmyhost-deploy — Develop, version, preview and publish an application with ohmyho.st from a local checkout or a connected native chat. Reuse the saved project and source, select managed source or GitHub only when needed, and switch an existing project only on request. Use troubleshooting for a stuck deployment.
  • ohmyhost-domains-and-mail — Choose a project’s check.omh.st address, connect a custom domain or a sender domain for sending and receiving email, provide manual DNS records, check DNS, HTTPS or DKIM readiness, or retire a mail domain. Use when an address, hostname or sender is being chosen, configured, pending or removed, or when a Free workspace wants its own domain through the ohmyho.st flag.
  • ohmyhost-export-database — Request and download an on-demand password-encrypted SQL ZIP from ohmyho.st. Use for a customer database backup or export; does not restore or overwrite another database.
  • ohmyhost-get-started — Connect a customer agent or native chat to ohmyho.st, verify the intended account and workspace, and continue an application from its saved source. Use managed OAuth for a remote chat and the existing local login for a terminal agent. Also use for account selection, customer support, or private automation credentials; use ohmyhost-deploy once access is ready.
  • ohmyhost-manage-database — Read or update authorized ohmyho.st project data, open time-bound psql access, change compute or Dev/Prod data assignments, reset isolated Dev, and prepare admitted schema or backend RLS migrations. Use for SQL operations, database sizing, idle costs, shared data or schema promotion.
  • ohmyhost-migrate-supabase-postgres — Migrate customer-selected Supabase capabilities in a TypeScript application to portable PostgreSQL and the ohmyho.st runtime. Use when real Supabase database, Auth, Storage, Functions or Realtime usage needs conversion; not merely because an SDK is installed.
  • ohmyhost-troubleshoot-deployment — Diagnose a failed or stalled ohmyho.st deployment, an app URL returning 402, 403, 404, 429, 502 or 503 from ohmyho.st, a cron that did not run, or mail/file client errors gateway_unavailable, gateway_timeout, gateway_route_denied or gateway_not_enabled. Resume eligible operations, report a product bug or feature request, and follow replies. Use for queued, publishing, mail-wait, build, health-check and runtime errors; a failed operation names its deployment_id for deployment_logs. Not for starting a new release.
  • ohmyhost-usage-and-budgets — Explain ohmyho.st measured usage, remaining credits and project spending limits, and buy credits or Paid when the owner asks. Use for cost reports, low-credit questions, an app paused with HTTP 402, budget changes, top-ups, Paid, auto-recharge, invoices, referral links or powered-by flag credits.
Skills preserve the customer’s selected application, auth provider and Dev/Prod decision. They call the public CLI/MCP contract, inspect actual status and report missing behavior through feedback. Installation alone does not authenticate the agent. Machine-readable catalogue · Connect MCP.