Agent skill

palantir-multi-env-setup

Configure Palantir Foundry across development, staging, and production environments. Use when setting up multi-environment Foundry deployments, managing per-environment credentials, or implementing environment-specific configurations. Trigger with phrases like "palantir environments", "foundry staging", "foundry dev prod", "palantir environment setup". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-multi-env-setup --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1.5.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(gcloud:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: skills/.curated/palantir-multi-env-setup/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Palantir Multi-Environment Setup ## Overview Configure Foundry integrations across dev/staging/prod environments with separate credentials, enrollment hostnames, and scope policies per environment. ## Prerequisites - Foundry enrollments for each environment (or separate projects within one enrollment) - Secrets manager (AWS SM, GCP SM, or Vault) - Familiarity with `palantir-security-basics` ## Instructions ### Step 1: Environment Configuration ```python # src/config.py import os from dataclasses import dataclass @dataclass class FoundryEnvConfig: hostname: str client_id: str client_secret: str scopes: list[str] ontology: str ENVIRONMENTS = { "development": FoundryEnvConfig( hostname=os.environ.get("DEV_FOUNDRY_HOSTNAME", "dev.palantirfoundry.com"), client_id=os.environ.get("DEV_FOUNDRY_CLIENT_ID", ""), client_secret=os.environ.get("DEV_FOUNDRY_CLIENT_SECRET", ""), scopes=["api:read-data"], # Read-only in dev ontology="dev-ontology", ), "staging": FoundryEnvConfig( hostname=os.environ.get("STG_FOUNDRY_HOSTNAME", "staging.palantirfoundry.com"), client_id=os.environ.get("STG_FOUNDRY_CLIENT_ID", ""), client_secret=os.environ.get("STG_FOUNDRY_CLIENT_SECRET", ""), scopes=["api:read-dat

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: Environment Configuration
  5. Step 2: Environment-Aware Client Factory
  6. Step 3: Environment Variables per Platform
  7. Step 4: Environment Validation
  8. Output
  9. Error Handling
  10. Resources
  11. Next Steps
Commands it runs
Docker Compose
docker-compose.yml
Kubernetes
kubectl create secret generic foundry-creds \
Cloud Run
gcloud run deploy my-app \
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the palantir-multi-env-setup skill do?

Configure Palantir Foundry across development, staging, and production environments. Use when setting up multi-environment Foundry deployments, managing per-environment credentials, or implementing environment-specific configurations. Trigger with phrases like "palantir environments", "foundry staging", "foundry dev prod", "palantir environment setup". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going