validate-bundle
Skill2 starsChanged yesterdayMITView on GitHub
Use immediately after `./make-dist.sh` to verify the standalone bundle is shippable. Runs structural checks (no dev data leak, no retired falcon-extras files, native binaries absent, eyas-mcp wheels staged, BUILD-INFO matches package.json) and an optional smoke-boot. Trigger phrases: "validate the bundle", "is the zip shippable", "check make-dist output", "verify the standalone build".
- Reads credentials
- Deletes or force-pushes
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-remediationsSkill
- audit-write-toolsSkill
- cost-summarySkill
- dev-serverSkill
- patch-contextSkill
- verify-featureSkill
- verify-patchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 53
All structural checks ✓. If boot enabled, /api/health returned 200 within 60s and /login + /register both rendered.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
validate-bundle
Catches the failure modes we've hit on real ship days. Each check below maps to a specific bug we've already paid for.
Run
bash .claude/skills/validate-bundle/run.shThat script auto-locates the most recent project-eyas-v*.zip in the repo root, runs every check below, and exits non-zero on any failure.
To target a specific bundle:
bash .claude/skills/validate-bundle/run.sh path/to/project-eyas-vX.Y.Z.zipChecks performed
Structural (fatal on miss)
- No dev
data/leak.unzip -lmust NOT showproject-eyas-vX/data/auth.json,data/cost-log.jsonl,data/perf-log.jsonl, ordata/dev.log. Next.js NFT tracing previously copied the dev host'sdata/into the standalone tree; recipients then saw the dev's password hash + cost log.make-dist.shscrubs$STAGE/data— this check verifies the scrub. - No retired
falcon-extras/files orvendor/falcon-extras-wheels/. The sidecar was removed; every Eyas tool runs in-process. Anything under those paths means a stale staging step crept back intomake-dist.sh. - No platform-specific native bindings. Anything matching
*.node(e.g.@node-rs/argon2-linux-x64-gnu/argon2.linux-x64-gnu.node) means a native module slipped back into the bundle. We migrated off@node-rs/argon2tocrypto.scryptto avoid this; if a.nodefile appears, a new dep brought a native binding back. - eyas-mcp wheels staged.
vendor/falcon-mcp-wheels/must contain at least one.whl. Without wheels the recipient's offline install path falls back to PyPI, which corp-blocked networks can't reach. BUILD-INFO.txtandbuild-info.jsonpresent and consistent. Both must exist;build-info.json.appVersionmust equalpackage.json.version. Catches version drift after a forgottennpm versionbump.server.jsat bundle root. The bundle's entrypoint. Without it,start.sherrors with the "may be corrupt" message. 7b. Gateway lock, if requested. The lock is opt-in (ANTHROPIC_GATEWAY_BASE_URLatmake-dist.shtime). An unlocked default build passes. A bundle whosebuild-info.jsonclaims a lock must carryforcedGatewayUrlin its compiled.next/output, or the check fails.REQUIRE_GATEWAY_LOCK=1makes an unlocked bundle fail too.start.shis executable (mode bit set in zip).
Smoke-boot (skippable)
Beyond structural checks, the only definitive proof the bundle works is launching it. The skill optionally:
- Extracts the zip to a
/tmp/<bundle-name>-validate-$$/dir. - Writes a minimal
.envcontaining onlyAUTH_SESSION_SECRET=<random>(no real Falcon/Anthropic creds — the bundle now supports running with empty credentials, deferring config to/register). - Starts
node server.jsin the background. - Polls
http://127.0.0.1:<port>/api/healthuntil 200 (timeout 60s). - Asserts
/loginand/registerboth render (HTTP 200, contains "CrowdStrike — For Internal Use Only" classification banner copy). - Kills the process, removes the temp dir.
Pass this stage (SKIP_BOOT=0, the default) only after the structural checks all pass — there's no point booting a bundle that's missing files.
To skip boot (faster, structural-only): SKIP_BOOT=1 bash .claude/skills/validate-bundle/run.sh.
Pass criteria
All structural checks ✓. If boot enabled, /api/health returned 200 within 60s and /login + /register both rendered.
Fail handling
| Check | Likely cause | Fix |
data/ leak | NFT trace re-copying the dev tree's data dir | Re-check make-dist.sh has rm -rf "$STAGE/data" after the standalone copy |
Retired falcon-extras files present | A sidecar staging step was restored in make-dist.sh | Remove it; nothing under falcon-extras/ ships |
Native .node file | New dep with a per-platform binary | Replace with a JS / WASM equivalent (cross-platform standalone is the constraint; see auth scrypt migration as precedent) |
| Wheels missing | Build host doesn't have python3, or PyPI was unreachable during build | Re-run on a host with PyPI access; the warning is in make-dist.sh stderr |
| Gateway lock not in compiled output | The build-flags.ts bake didn't take before npm run build | Rebuild with ANTHROPIC_GATEWAY_BASE_URL set and no dev server running |
BUILD-INFO.txt version drift | npm version bump didn't happen, or versions.json wasn't updated | Bump appropriately and rebuild |
Boot fails on /api/health | Bundle is structurally sound but server crashes on startup | Read node server.js stderr from the temp dir; common cause is a missing optional dep |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

