Agent skill · software engineering · jeremylongshore
palantir-deploy-integration
Choose and execute a Foundry-native deployment path for OSDK applications, products, or container workloads. Use when publishing a Developer Console app, DevOps product, or Compute Module. Trigger with "deploy to Foundry" or "Palantir Compute Module".
Why this skill is useful
Adds executable deployment scripts and cloud integration patterns for Palantir Foundry that are not commonly known.
What it needs
Requires docker, 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 Application and Compute Deployment Overview Select the deployment primitive from the workload instead of defaulting to an external cloud runtime. Use Developer Console and Marketplace for OSDK applications, DevOps products for release-managed resources, or Compute Modules for compatible container workloads inside Foundry. Prerequisites Identify the workload, owners, target environment, runtime needs, data access, availability objective, and rollback requirement. Determine whether it is an OSDK website/application, a packaged Foundry product, a container-backed function, or a container-backed pipeline. Read references/official-docs.md and the target enrollment's in-platform Compute Module or DevOps instructions. Prepare a versioned artifact and non-production target. Current Contract Compute Modules run interactive container images in Foundry and support container-backed functions, pipelines, and custom integrations. Compute Module images must meet documented platform, user, tag/digest, and port requirements. Developer Console applications can be packaged through Marketplace with OAuth client metadata and resource restrictions. DevOps/Marketplace installation can remap supported environment parameters, while Ontology API-name handling still requires deliberate design. Authentication Use Developer Console OAuth for application access and Foundry's approved artifact/deployment authentication for publishing. Keep client secrets and bearer tokens in approved secret surfaces; do not bake them into images, code repositories, product parameters, or website assets. Instructions 1. Classify the workload and select Developer Console/Marketplace, a DevOps product, or a Compute Module with a written rationale. 2. Inventory dependencies, OAuth grants, resource restrictions, parameters, markings, artifact repository, and target-space ownership. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-deploy-integration--7c51db