From olam
Create a new isolated development world (local Docker or Cloudflare Sandbox). Use when the user says "create a world", "new world", "spin up an environment", "start a fresh sandbox", "I need an isolated workspace for a task", or wants to dispatch an agent into a sandboxed branch. Selects the compute backend from the project's Olam config; both modes flow through one MCP tool.
How this skill is triggered — by the user, by Claude, or both
Slash command
/olam:create [world name][world name]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Provision an isolated development world. The backend is selected by
Provision an isolated development world. The backend is selected by
the loaded Olam config (compute.default): docker (local) or
cloudflare (CF Sandbox). Both flow through the same MCP tool.
The definitive contract for Cloudflare worlds lives at
docs/CF_WORLDS_SPEC.md
in the source repo. Skills must not diverge from it.
No additional credentials needed beyond a running Docker daemon.
Confirm the current project's .env.local contains:
OLAM_WORKER_URL — https://<your-worker>.workers.devOLAM_PYLON_ORG_URL — Pylon org URL the MCP mints scoped tokens againstOLAM_PYLON_ORG_ID — canonical org slug (matches pylon-cli's --org)OLAM_CF_ACCESS_CLIENT_ID — CF Access service token idOLAM_CF_ACCESS_CLIENT_SECRET — CF Access service token secretThe MCP reads these from .env.local at the Olam project root (the
directory containing .olam/config.yaml or olam.yaml). There is
no global Olam config. If any var is missing, the MCP fails at
startup with the exact missing key — ask your admin for the value and
re-export.
Parse the argument as the world name. If no argument is provided, ask the user for a world name.
Optionally ask whether to scope to specific repos and/or include a task description. For CF mode, a task triggers auto-dispatch after in-container auth completes.
Call olam_create:
name — the world namerepos (optional) — array of repo namestask (optional) — task descriptionbranchName (optional) — override default branchPresent the result. For CF mode specifically, show:
sessionIddashboardUrl (https://<your-worker>.workers.dev/sandbox/<id>/)Remind the user that dispatch is available via /olam:dispatch <world-id> <prompt>.
OLAM_CF_ACCESS_CLIENT_ID is valid and that the caller's identity is in the allow-list./session/start — container boot failed. Tail with npx wrangler tail <worker-name> --format pretty and surface the last error line.better-sqlite3 ABI mismatch — the Dockerfile's Node version drifted from the cloudflare/sandbox runtime. Align the builder image's Node version with the sandbox runtime..env.local at the project root.olam_create returns "name already exists" — pick a different name or call olam-destroy on the existing world first.olam-list.olam-destroy.olam-dispatch. This skill creates net-new worlds.olam-connect (admin-hosted path) or run olam setup (standard path).olam-dispatch — send a task to a running world.olam-list — show worlds you've already created.olam-status — inspect a single world in depth.olam-destroy — tear down a world.npx claudepluginhub pleri/olam-cliProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.