Agent skill · software engineering · jeremylongshore
palantir-webhooks-events
Choose and implement a supported Foundry event path using OSDK object subscriptions, direct WebSocket subscriptions, monitoring webhooks, or Data Connection webhooks. Use when reacting to object or monitoring changes. Trigger with "Palantir events" or "Foundry subscription".
Why this skill is useful
Adds executable scripts for handling Palantir Foundry webhook events, including registration, signature verification, and event routing that are not available in public documentation.
What it needs
Requires foundry-platform-sdk 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 Event and Subscription Integration Overview Start from the event producer and delivery guarantee: real-time Ontology object updates use OSDK or Object Set Watcher WebSocket subscriptions, while monitoring notifications and outbound integrations use their documented webhook surfaces. Never invent a general ontology.object.created registration API. Prerequisites Identify the producer, consumer, object set or monitoring view, supported delivery surface, data sensitivity, latency objective, and recovery behavior. Confirm the generated OSDK version or direct WebSocket contract, or the configured Data Connection webhook required by monitoring. Read references/official-docs.md and verify target-enrollment feature access. Prepare a non-production object set or monitoring view and an idempotent consumer. Current Contract TypeScript OSDK subscriptions require a compatible generated OSDK/client and receive object-set updates through .subscribe. Direct Object Set Watcher subscriptions use a documented WebSocket endpoint and authenticate with a bearer token encoded in the WebSocket subprotocol format. Subscriptions can report an out-of-date state that requires reloading the full object set. Monitoring views can route notifications through webhooks configured in Data Connection; that is distinct from Ontology object subscriptions. Authentication Use the generated OSDK token provider or the documented WebSocket bearer subprotocol. For outbound webhooks, use the authentication configured by the supported Data Connection webhook. Never invent or assume a signature header; record the actual configured authentication and secret owner. Instructions 1. Classify the event need as Ontology object-set change, monitoring notification, or another documented Foundry integration. 2. Choose TypeScript OSDK subscription, direct WebSocket, or monitoring/Data Connection webhook and document why it matches. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-webhooks-events