Agent skill · product strategy · jeremylongshore
palantir-reference-architecture
Design a production Foundry architecture spanning data pipelines, Ontology, OSDK or Platform APIs, deployment, governance, and operations. Use when defining a new platform integration or reviewing an existing one. Trigger with "Palantir architecture".
Why this skill is useful
Provides specific patterns and project layouts for implementing Palantir Foundry architecture that the AI wouldn't reliably generate on its own.
What it needs
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 Integration Architecture Overview Start from business decisions and data authority, then map each responsibility to a Foundry primitive. Keep ingestion, transformation, Ontology semantics, application access, deployment, and telemetry independently governable. Prerequisites Identify users, decisions, source systems, data owners, update/writeback semantics, service objectives, compliance boundaries, and recovery needs. Inventory current and proposed Foundry projects, datasets, transforms, Ontology entities, applications, products, modules, and external integrations. Read references/official-docs.md and resolve target-enrollment feature availability with platform owners. Declare trust boundaries and authoritative systems before drawing components. Current Contract Python transforms provide batch/incremental pipelines with multiple compute engines and data expectations. The Ontology represents domain objects, links, Actions, and Functions; OSDK applications receive a generated subset of it. Platform SDKs expose broader Foundry/AIP REST APIs, while OSDKs provide application-specific Ontology contracts. DevOps/Marketplace and Compute Modules cover different release-managed and interactive-container deployment needs. Authentication Define user-delegated and service authentication at each application boundary. Record OAuth grants, principals, scopes, Developer Console restrictions, secret storage, rotation, and revocation without placing credential values in the architecture artifact. Instructions 1. Define capabilities, owners, authoritative data, side effects, latency/freshness objectives, and failure domains. 2. Place ingestion and transformations into projects with explicit inputs, outputs, lineage, expectations, and compute choices. 3. Model domain semantics and writeback in the Ontology, including object/property security and Action validation. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-reference-architecture