Agent skill · data analytics · jeremylongshore
palantir-common-errors
Diagnose Foundry API, Ontology, permission, and transform-build failures from bounded evidence. Use when an operator sees authentication, authorization, throttling, missing-resource, dependency, or build errors. Trigger with "Foundry error" or "Palantir 403".
Why this skill is useful
Provides specific troubleshooting steps and code snippets for common Palantir Foundry API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires 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 Foundry Error Triage Overview Triage the failing surface before changing credentials, permissions, code, or compute. Preserve the server request identifier and Foundry build evidence so similar-looking failures are not collapsed into the same cause. Prerequisites Capture the exact status code or Foundry error name, request identifier, timestamp, endpoint or build, and affected principal. Identify whether the call uses a temporary user token, authorization-code token, or client-credentials service user. Read references/official-docs.md; use the API reference and in-platform build report as the current contract. Reproduce with a read-only request or sandbox branch whenever possible. Current Contract A 401 points to missing, malformed, expired, or otherwise unusable authentication; it does not justify broader scope. A 403 can result from the intersection of token scope, application restrictions, user/service-user permissions, project roles, and mandatory controls. Foundry documents global rate and concurrency limits, while individual endpoints may impose stricter limits and return 429 or 503. Transform preview and full build can differ because preview may use a subset of data; repository checks also evaluate dependencies and declared resources. Authentication All Foundry REST API calls use OAuth 2.0 bearer tokens. Never print or persist a token in the triage report. Record the grant type, requested scopes, Developer Console restrictions, and effective user or service-user permissions without recording credential values. Instructions 1. Classify the failure as authentication, authorization, limit/concurrency, resource identity, dependency, transform logic, or platform availability. 2. Preserve the smallest complete evidence set: request ID, build ID, branch, commit, principal type, scope names, and affected RIDs or API names. 3. For auth failures, evaluate token validity, scope, application restrictions, project role, and mandatory markings in that order. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-common-errors