Agent skill · software engineering · jeremylongshore
palantir-migration-deep-dive
Plan and execute a phased migration of data pipelines, Ontology applications, or external integrations into Foundry. Use when replacing a legacy system or moving workloads across Foundry environments. Trigger with "Palantir migration" or "Foundry cutover".
Why this skill is useful
Adds executable scripts for data migration and API version upgrades specific to Palantir Foundry that are not publicly documented.
What it needs
Requires node, pip 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 Foundry Migration and Cutover Overview Migrate contracts and evidence, not just bytes. Inventory data semantics, identities, access controls, pipeline transactions, Ontology entities, applications, and operational dependencies before dual-running a bounded slice. Prerequisites Name source and target owners, business workflows, datasets, schemas, identities, controls, service objectives, retention, and rollback deadline. Choose the target Foundry primitives: connectors, transforms, Ontology resources, OSDK application, DevOps product, or Compute Module. Read references/official-docs.md and document features or resources that do not map directly. Establish a frozen baseline and approved non-production landing zone. Current Contract Foundry applications and resources can be packaged and promoted with DevOps and Marketplace across environment spaces. Developer Console application installation remaps supported parameters, but API-name consistency and dependencies still require explicit handling. Incremental transforms have transaction-history requirements and must reconcile with snapshot behavior. Access control combines project roles, mandatory controls, Ontology policies, and application restrictions. Authentication Inventory source and target identities, OAuth grant types, service users, scopes, and application restrictions as separate migration contracts. Store secrets in approved managers, rotate them through a staged cutover, and never copy source credentials into the target environment. Instructions 1. Inventory source contracts: identifiers, schemas, update/delete semantics, volumes, SLAs, consumers, permissions, audit requirements, and failure modes. 2. Design target datasets, transforms, Ontology entities, Actions, applications, and controls with an explicit mapping for every source contract. 3. Load a bounded historical slice, then establish incremental capture or repeatable deltas with reconciliation keys. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-migration-deep-dive--0d3c21