How do I install the Openhost skill?

Run npx skillmds@latest add cloud-in-a-bottle/openhost in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openhost safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openhost?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openhost free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openhost?

cloud-in-a-bottle (@cloud-in-a-bottle) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openhost by cloud-in-a-bottle — Agent Skill

Name: Openhost
Author: cloud-in-a-bottle

Openhost

Reference for building and debugging openhost apps. Use when the user mentions openhost, an openhost app, compute_space, the openhost.toml manifest, or asks how openhost routes/builds/runs apps. Reads the curated docs from the cloned openhost repo at $OPENHOST_DIR (default ~/openhost).

File contents

openhost reference

This workbench has a cloned copy of the openhost repo. Always read from the local clone, not from the web. The clone lives at $OPENHOST_DIR (default ~/openhost).

Read these first, in order

When the user asks anything openhost-shaped, read these files before answering:

~/openhost/claude.md — project orientation, structure, how to run tests.
~/openhost/style_guide.md — code style for the repo.
~/openhost/README.md — user-facing overview.
~/openhost/docs/ — design docs and specs (list the directory, then read what's relevant).
~/openhost/apps/test_app/ — minimal example app (Dockerfile + openhost.toml + server.py).

Building a new openhost app

A minimal app is three files in apps/<name>/:

openhost.toml — manifest (name, port, health_check, resources).
Dockerfile — how to build the container image.
a server that listens on the port and serves the health_check route.

For a complete tiny example, read ~/openhost/apps/test_app/.

Debugging an openhost app

The router lives in ~/openhost/compute_space/src/compute_space/web/proxy.py.
App lifecycle (build, run, route) is in ~/openhost/compute_space/src/compute_space/core/apps.py.
Logs / observability code lives under ~/openhost/compute_space/src/compute_space/core/.

Things to remember

pixi run -e dev pytest -x for the lightweight test suite. --run-containers for the full one.
Apps are routed by subdomain. Each gets its own user namespace via rootless podman.
Auth is JWT RS256 — apps verify with a public key passed in as an env var.

If the clone is missing

If $OPENHOST_DIR does not exist, tell the user — the entrypoint normally clones it on first container start. They can clone manually:

git clone https://github.com/imbue-openhost/openhost ~/openhost

---name: openhostdescription: Reference for building and debugging openhost apps. Use when the user mentions openhost, an openhost app, compute_space, the openhost.toml manifest, or asks how openhost routes/builds/runs apps. Reads the curated docs from the cloned openhost repo at $OPENHOST_DIR (default ~/openhost).---# openhost referenceThis workbench has a cloned copy of the openhost repo. **Always read from the local clone**, not from the web. The clone lives at `$OPENHOST_DIR` (default `~/openhost`).## Read these first, in orderWhen the user asks anything openhost-shaped, read these files before answering:1. `~/openhost/claude.md` — project orientation, structure, how to run tests.2. `~/openhost/style_guide.md` — code style for the repo.3. `~/openhost/README.md` — user-facing overview.4. `~/openhost/docs/` — design docs and specs (list the directory, then read what's relevant).5. `~/openhost/apps/test_app/` — minimal example app (Dockerfile + openhost.toml + server.py).## Building a new openhost appA minimal app is three files in `apps/<name>/`:- `openhost.toml` — manifest (name, port, health_check, resources).- `Dockerfile` — how to build the container image.- a server that listens on the port and serves the health_check route.For a complete tiny example, read `~/openhost/apps/test_app/`.## Debugging an openhost app- The router lives in `~/openhost/compute_space/src/compute_space/web/proxy.py`.- App lifecycle (build, run, route) is in `~/openhost/compute_space/src/compute_space/core/apps.py`.- Logs / observability code lives under `~/openhost/compute_space/src/compute_space/core/`.## Things to remember- `pixi run -e dev pytest -x` for the lightweight test suite. `--run-containers` for the full one.- Apps are routed by subdomain. Each gets its own user namespace via rootless podman.- Auth is JWT RS256 — apps verify with a public key passed in as an env var.## If the clone is missingIf `$OPENHOST_DIR` does not exist, tell the user — the entrypoint normally clones it on first container start. They can clone manually:```git clone https://github.com/imbue-openhost/openhost ~/openhost```

Frequently asked questions