Agent skill · software engineering · jeremylongshore
palantir-local-dev-loop
Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds. Use when iterating on transforms or OSDK code. Trigger with "Foundry local development".
Why this skill is useful
Adds specific commands and project structure for local development with Palantir Foundry that the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. Requires foundry account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir Local and In-Platform Development Loop Overview Keep pure logic fast and local while treating Foundry preview, checks, and builds as separate evidence. A local mock can verify application logic, but it cannot prove Foundry permissions, lineage, transactions, or full-data behavior. Prerequisites Identify the Code Repository or Developer Console application, language, branch, data sensitivity, and target environment. Install the supported Palantir VS Code extension or use an in-platform workspace as appropriate. Read references/official-docs.md and the repository's generated in-platform documentation. Prepare lightweight unit fixtures without production data and a sandbox branch. Current Contract Foundry Code Repositories support sandbox branches, automatic checks, unit tests, previews, pull requests, and full builds. Preview can use sample or subset data; a full build runs on platform data and commits pipeline output. The VS Code extension can preview, debug, synchronize, and initiate Foundry builds from a local workspace. Local tests should isolate business logic and avoid relying on live external resources. Authentication Use the approved Palantir VS Code or Developer Console sign-in for the intended environment. Keep generated OAuth settings and any test credentials in approved local secret storage, and never place tokens or production object data in fixtures, logs, or repository files. Instructions 1. Separate pure transformation or application logic from Foundry adapters and generated SDK code. 2. Write deterministic unit tests using synthetic fixtures and run them before any platform request. 3. Synchronize the sandbox branch, run Foundry checks, and preview representative inputs with protected-data rules intact. 4. Use the Foundry debugger for Python transform behavior when needed; treat observed values as diagnostic only. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-local-dev-loop