Menü
Configure Cloudflare Tunnel and Access for woltspace — initial setup, add or remove user permissions, and wildcard app subdomains.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
IWCL — Inter-Wolt Communication. Message another wolt and reply to messages from wolts. Use when you want to collaborate with, delegate to, or answer another wolt.
Work with apps — the isolated workspace for building apps, scripts, and experiments. Use when creating, running, or managing an app.
Set up a new app from scratch. Use when starting a fresh app — scaffolds the directory, writes woltspace.json, starts the dev server.
First session for a brand new wolt. Say hi, show the site, ask what to build.
Push content to the split view's right pane. Use when you want to show HTML, pages, or artifacts to the user.
Help a user who has accidentally edited platform code in /workspace/woltspace/. Detects drift, extracts their work into wolt/apps/, and resets the platform to clean state.
| name | woltspace-cloudflare |
| description | Configure Cloudflare Tunnel and Access for woltspace — initial setup, add or remove user permissions, and wildcard app subdomains. |
| user_invocable | true |
Single skill for everything Cloudflare-related on woltspace: the named tunnel that gives the lodge a permanent URL, the Access policies that gate who can reach it, and the wildcard setup that lets public apps live at {app}.{domain}.
This skill routes to a sub-doc based on what the user wants. Ask first — don't run any sub-doc by default.
Ask the user which task they need, then read the matching sub-doc and follow it step by step.
| User intent | Sub-doc | When to use |
|---|---|---|
| First-time tunnel + Access setup | setup.md | No named tunnel yet, or CLOUDFLARE_TUNNEL_TOKEN is unset in /workspace/wolts/.env. |
| Add a person to an existing app | add-access.md | Tunnel + Access already configured. Granting an email access to the lodge, the wildcard, or one specific subdomain. |
| Remove a person from an app | remove-access.md | Revoking a previously-granted email. |
Quick check for which state the user is in:
source /workspace/wolts/.env
echo "TUNNEL_TOKEN=${CLOUDFLARE_TUNNEL_TOKEN:+SET}"
echo "TUNNEL_URL=${CLOUDFLARE_TUNNEL_URL:-NOT SET}"
echo "API_TOKEN=${CLOUDFLARE_API_TOKEN:+SET}"
echo "ACCOUNT_ID=${CLOUDFLARE_ACCOUNT_ID:-NOT SET}"
add-access.md or remove-access.md.TUNNEL_TOKEN unset but API_TOKEN set → setup was started but tunnel never landed; resume setup.md from Step 4.setup.md Step 1..env lives at /workspace/wolts/.env. Every Cloudflare API call reads from there..{domain}, so a user who logs into one subdomain stays logged in across every app they have access to for the session duration.session_duration values: 30m, 6h, 12h, 24h, 168h, 730h (1 month is the max on the free plan).Browser → subdomain.domain.com
→ Cloudflare Edge (Access: email OTP)
→ Cloudflare Tunnel (QUIC, auto-reconnect)
→ localhost:7777 (FastAPI)