Agent skill · software engineering · jeremylongshore
palantir-sdk-patterns
Implement resilient Palantir clients by choosing generated OSDK or Platform SDK, pinning contracts, and bounding authentication, pagination, retries, and writes. Use when building shared Foundry client code. Trigger with "Palantir SDK patterns".
Why this skill is useful
Adds multiple executable scripts for Palantir Foundry SDK usage that enhance integration capabilities and establish coding standards.
What it needs
Requires @osdk/client, foundry-platform-sdk 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 Boundary and Client Patterns Overview Keep application-specific Ontology access in the generated OSDK and broader platform operations in the Platform SDK. Wrap transport concerns without hiding the generated entity contract, OAuth authority, request identifiers, or Action validation. Prerequisites Identify the application job, language, required Ontology entities or Platform API operations, write behavior, and owner. Select the target Developer Console application or current official Platform SDK package and pin its version. Read references/official-docs.md, generated application documentation, and relevant migration guide. Define request deadlines, page bounds, retryable statuses, idempotency, telemetry, and secret storage. Current Contract OSDK packages are generated for selected Ontology resources and support application-specific typed access. Official Python and TypeScript Platform SDKs wrap Foundry/AIP REST APIs for broader platform operations. Authentication authority is the intersection of OAuth scope, Developer Console restrictions, and principal permissions. Generated OSDK versions can change call syntax; migration guides are part of the upgrade contract. Authentication Inject an approved token provider or OAuth client into the boundary; never accept a raw long-lived token as ordinary configuration. Log grant/principal identifiers and request IDs where permitted, but never bearer tokens, client secrets, object values, or protected payloads. Instructions 1. Write a decision record choosing OSDK or Platform SDK and list the exact required resources or operations. 2. Expose one client boundary that owns token acquisition, deadlines, request correlation, retry classification, and telemetry. 3. Implement deterministic pagination and property selection; return continuation state rather than silently loading every page. 4. Keep generated object, Action, and Function definitions visible to callers and validate Actions before approved execution. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-sdk-patterns--2df91d