Agent skill · software engineering · jeremylongshore
palantir-core-workflow-b
Build and verify an Ontology-backed application with a generated OSDK, bounded object queries, and validated Actions. Use when implementing object reads, links, aggregations, Functions, or writeback. Trigger with "Palantir OSDK" or "Ontology Action".
Why this skill is useful
Adds executable scripts for querying and manipulating Palantir Foundry Ontology objects that are not publicly documented.
What it needs
Requires npm, 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 Ontology Application Workflow Overview Use the generated Ontology SDK as the typed contract for a Developer Console application. Keep reads, Functions, and Actions distinct, and validate writeback before execution when the generated SDK and action support it. Prerequisites Identify the Developer Console application, Foundry environment, selected Ontology entities, grant type, application restrictions, and data owner. Generate or select the OSDK language and version required by the application; do not guess object, property, link, Action, or Function API names. Read references/official-docs.md and the application-specific generated documentation in Developer Console. Prepare test objects and a non-production Action path. Current Contract An OSDK is generated for a selected subset of an Ontology and supports TypeScript, Python, Java, and other-language generation paths. Application access is the intersection of the acting user or service user, OAuth scopes, and Developer Console restrictions. In TypeScript OSDK 2.x, generated definitions are passed to the client for object operations, Actions, and Functions. Action validation and returned edits are explicit options; validation-only and returned-edits modes cannot be assumed interchangeable. Authentication Use the Developer Console grant chosen for the application: authorization code for user-delegated applications or client credentials for a backend service. Never embed a client secret or bearer token. Record scopes and resource restrictions separately from the Foundry permissions of the user or service user. Instructions 1. Define the user job and list the minimum object types, interfaces, links, Actions, and Functions the application requires. 2. Configure the Developer Console application and generate the OSDK with only those Ontology resources. 3. Implement a bounded object query with explicit filters, selected properties, deterministic ordering, and pagination. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-core-workflow-b