Agent skill · software engineering · jeremylongshore
palantir-upgrade-migration
Upgrade a Palantir OSDK, Platform SDK, generated application, or release-managed product through pinned contracts and reversible stages. Use when adopting a new SDK generation or product version. Trigger with "upgrade Palantir SDK".
Why this skill is useful
Adds executable scripts for upgrading the Palantir Foundry SDK and handling breaking changes that are not publicly documented.
What it needs
Requires git, pip installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir SDK and Application Upgrade Overview Treat generated OSDK changes and official Platform SDK releases as contract migrations. Freeze the old and new artifacts, read the relevant migration guide or release notes, update one boundary, and prove compatibility in a non-production environment. Prerequisites Identify the current and target package/product versions, generated Developer Console application, language/runtime, call sites, owners, and target environments. Capture lockfiles, generated metadata, OAuth restrictions, tests, representative queries/Actions, and prior product or image version. Read references/official-docs.md and the language-specific migration guide or official release history. Prepare a branch and non-production installation with a documented downgrade. Current Contract Generated OSDK packages are tied to selected Ontology resources and compatible client versions. TypeScript OSDK migration guides document syntax changes for object access, Actions, batch Actions, and Functions/queries. Official Platform SDK repositories publish immutable releases and generated API changes. DevOps/Marketplace release management can promote and roll back versioned products across environments. Authentication Do not change grant type, scopes, resource restrictions, service-user permissions, or secrets as an incidental SDK upgrade. If an auth change is required, review and test it as a separate security migration. Instructions 1. Freeze the old state and create a compatibility inventory of imports, generated entities, operations, scopes, runtime, and tests. 2. Review official migration/release evidence and classify source, generated-code, runtime, and behavior changes. 3. Update the pinned SDK/client or product on a branch without unrelated refactors. 4. Run unit/contract tests plus representative reads, pagination, Actions in validation-only mode, auth denials, throttling, and error mapping. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-upgrade-migration