Agent skill · software engineering · jeremylongshore
palantir-multi-env-setup
Configure development, test, and production Foundry environments using spaces, DevOps products, Marketplace installations, and explicit parameters. Use when release-managing workflows across environments. Trigger with "Foundry environments" or "Palantir dev test prod".
Why this skill is useful
Adds executable scripts and configurations for managing multi-environment setups in Palantir Foundry that are not commonly found in public documentation.
What it needs
Requires gcloud installed locally. Requires palantir account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir DevOps Environment Separation Overview Represent long-lived environments with Foundry spaces and promote versioned products through DevOps and Marketplace. Use Global Branching for isolated changes within an environment, not as a substitute for every long-lived environment boundary. Prerequisites Identify the enrollment, DevOps store, source products, target spaces, owners, dependencies, security policies, external systems, and approval chain. Inventory environment-specific sources, sinks, URLs, OAuth clients, markings, organizations, schedules, and release windows. Read references/official-docs.md and inspect the current product dependency and parameter contracts. Establish the development source product and at least one non-production installation. Current Contract Spaces provide environment separation for development, test, and production workflows. DevOps products package resources and their dependencies; downstream products should resolve inputs from the corresponding target environment. Marketplace installations can use release channels, locks, maintenance windows, and parameter inputs. Supported Developer Console application parameters can be remapped during installation, but Ontology API-name behavior and source-code parameters need explicit review. Authentication Give each environment an appropriately restricted OAuth application or mapped Developer Console application according to the supported product contract. Do not copy production client secrets into development or embed environment credentials in packaged source. Instructions 1. Define each environment as a space with owners, security policy, external integration boundary, approval workflow, and recovery objective. 2. Package the workflow into bounded DevOps products with explicit inputs, outputs, dependencies, and parameter contracts. 3. Install upstream products before downstream dependents in test, resolving every input from the matching environment. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-multi-env-setup