Agent skill · software engineering · jeremylongshore
juicebox-multi-env-setup
Configure Juicebox multi-environment.
Why this skill is useful
Provides specific environment configuration patterns and validation scripts for Juicebox that the AI wouldn't reliably generate on its own.
What it needs
Requires jq, npm installed locally. Requires juicebox account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Juicebox Multi-Environment Setup Overview Juicebox AI analysis requires environment separation to enforce workspace isolation, control data access, and prevent accidental exports of sensitive datasets. Development works with sample datasets and strict result limits for fast iteration, staging connects to full production data but disables export functionality, and production enables all features with full export capabilities. Each environment uses isolated workspaces so analysis experiments in dev never affect production workspace state or user-facing reports. Environment Configuration Environment Files Environment Validation Promotion Workflow Environment Matrix Setting Dev Staging Prod --------- ----- --------- ------ Dataset Sample (100 records) Full dataset Full dataset Result Limit 5 20 50 Export Enabled No No Yes Workspace Isolated dev Isolated staging Production API Tier Free Standard Enterprise Report Sharing Disabled Internal only Full access Error Handling Issue Cause Fix ------- ------- ----- 403 on export endpoint Export disabled in non-prod env Expected; exports only work in production Workspace not found Workspace ID mismatch for env Verify JBWORKSPACE matches Juicebox admin panel Result limit exceeded Query returns more than env cap Reduce query scope or increase limit in config Stale sample data in dev Dev dataset not refreshed Run npm run seed:dev to reload sample data API key scope error Key generated for wrong workspace Regenerate API key in correct workspace settings Prerequisites Approved environment boundaries, sandbox-only synthetic fixtures, secret references rather than literal keys, source/destination allowlists, suppression controls, and a tested rollback revision. Instructions 1. Keep development and staging datasets synthetic; reject cross-environment credentials, sources, destinations, and real-record exports. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/juicebox-multi-env-setup--5c78bc