Beta Gate
Ship unfinished features to staging but never to production: a build-time flag plus a runtime guard.
Beta Gate is the two-layer system that keeps work-in-progress features visible on staging and impossible to serve in production. It was built for an Astro plus Cloudflare Pages site (the "Dry Dock") after a beta UI leaked to production through a normal deploy, and it has held ever since. Layer one is a build-time flag. Every beta surface (nav link, homepage teaser, beta pages) is gated behind a single boolean read from the shell environment at build time. Build with SHOW_BETA=1 and the beta UI is included; build without it and the output contains zero beta HTML. The flag is read via process.env, not import.meta.env, because Vite does not inject arbitrary shell variables into import.meta.env. The flag module is imported from build-time code only, never from client-side scripts. Layer two is a runtime guard in the worker entry. Before any route handling, requests to /beta* and /api/beta* on production hostnames get a plain 404. This catches the classic accident: a beta-enabled build deployed to production by mistake. Either layer alone would be enough on a careful day; together they make a leak practically impossible. The kit also documents the deploy discipline that makes it stick: staging and prod as separate targets, never two builds at once (one build's output can clobber the other's), never rebuild the output directory while an upload is in flight, and a zero-tolerance post-build check that greps the prod output for beta path strings.
Version:
Quick answer
Beta Gate is a two-layer system for shipping unfinished features to staging while making them impossible to serve in production. Layer one is a build-time flag: build with SHOW_BETA=1 and the beta UI exists, build without it and the output contains zero beta HTML. Layer two is a runtime guard in the worker that answers a plain 404 to beta routes on production hostnames, which catches a beta-enabled build deployed by mistake. It was built for an Astro plus Cloudflare Pages site after a beta UI leaked to production through a normal deploy, and it has held ever since.
At a glance
| What it is | A two-layer guard — build-time flag plus runtime 404 guard — that keeps work-in-progress features on staging only. |
|---|---|
| Who it's for | Developers on Astro plus Cloudflare Pages (or a similar static-plus-worker stack) who preview unfinished features on a staging target. |
| What you give it | Your build setup and worker entry point, and the discipline it documents: separate staging and prod targets, one build at a time. |
| What you get | Beta surfaces that vanish completely from production builds, a 404 guard if the wrong build ships, and a zero-tolerance post-build check to run. |
| Works with | Muse — install it from this listing's Install section with the copy-paste install prompt. |
| Cost | Free — Skill Harbor House License v1.0 |
| Time | An afternoon to wire the flag and the guard into an existing site; after that it is part of every build. |
Example — the accident it was built for
An example of the exact failure the two layers are designed to absorb:
- A build runs with the beta flag on, so the output contains the beta pages and nav links meant for staging.
- That build is deployed to the production hostname by mistake — the classic slipped deploy.
- The worker guard answers 404 to every beta route on the production hostname, and the post-build grep confirms no beta paths are being served. Nothing leaks.
Install
Copy the install package below, then paste it into Muse🧪 Sandbox retest pending · Oct 14, 2026📌 Pinned version: commit aeaa0c8Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: none for installing the skill files. No account, no key, no cost. Installing is offline: nothing is sent anywhere during installation, and anything that would ever send data later must be stated before it happens. Install "Beta Gate" for me. It ships unfinished features to staging only: a build-time flag strips the beta area from production builds, and a runtime guard in the worker answers 404 to beta routes on production domains even if the wrong build gets deployed. Source: https://raw.githubusercontent.com/skill-harbor-hq/house-skills/aeaa0c837868e0972b6cfbfe3d1713b7dde80f23/beta-gate/SKILL.md Pinned version: install the code at commit aeaa0c837868e0972b6cfbfe3d1713b7dde80f23 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Helper files, in the same skill folder in the repository (beta-gate/): references/astro-cloudflare.md, and LICENSE at the folder root. 1. Download SKILL.md, the helper files and LICENSE into a temporary folder, keeping the helper file inside a references subfolder and LICENSE beside SKILL.md. 2. Compare each file with the fingerprint from Skill Harbor's review of 2026-10-10: - SKILL.md: SHA-256 dddab817e24e5ddb5c236a73886b09cd9cf148e06ec15bd4755014e390e62945 - references/astro-cloudflare.md: SHA-256 fc9b31d0af5de62f4ce25c1edf2258cb84d6e473e9ed106d503676358bbb9c8c - LICENSE: SHA-256 d7db27db632a56a432d4f883c89507f031215e665f4806dfcd2dea15c0fb8271 If a file does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 3. Read the files and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy the files into my skills folder, in a folder named "beta-gate", keeping the helper files in their subfolders. 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do: nothing to set up now — I use it when I want a staging-only area on my site. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- aeaa0c8 · 2026-10-13
- Sandbox install test
- Sandbox retest pending · Oct 14, 2026
- Creator identity
- Verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
More house skills
This skill is made by Skill Harbor itself. See all house skills →
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.