Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/palantir-install-auth

@820dfc8
Run it yourself

Select and configure a Palantir OSDK or Platform SDK with the correct Developer Console OAuth grant and restrictions. Use when bootstrapping a user application, backend service, or direct platform API client. Trigger with "install Palantir SDK" or "Foundry OAuth".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/palantir-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈257 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈288 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Palantir SDK Selection and OAuth Setup

Overview

Choose the SDK from the job: a generated OSDK for application-specific Ontology access, or the Platform SDK for broader Foundry/AIP REST APIs. Then configure OAuth through Developer Console with the minimum grant, scope, resources, and operations.

Prerequisites

  • Identify the application type, language, Foundry environment, acting user or service user, required APIs, and accountable owner.
  • List the minimum Ontology entities or Platform API operations before creating credentials.
  • Read references/official-docs.md and use Developer Console's generated Start developing instructions for the target application.
  • Prepare an approved secret store and non-production verification resource.

Current Contract

  • Foundry APIs use OAuth 2.0 bearer tokens.
  • Authorization Code grant is for applications acting on behalf of users; Client Credentials grant is for backend services acting as a service user.
  • Developer Console application restrictions limit available Ontology resources or Platform SDK operations in addition to requested scopes and principal permissions.
  • Temporary user API tokens may support development, but production applications should use the appropriate OAuth grant.

Authentication

Never ask for, print, or commit a bearer token, client secret, authorization code, or refresh token. Store secrets only in an approved manager. Record the client ID only where allowed, and inventory grant type, redirect URLs, requested scopes, application restrictions, service-user permissions, owners, and rotation.

Instructions

  1. Choose generated OSDK or Platform SDK and document why the other surface is insufficient or unnecessary.

  2. Create or select the Developer Console application and configure the user-delegated or backend-service grant.

  3. Restrict the client to the required Ontology entities or Platform SDK operations and request the minimum scopes.

  4. Install and pin the generated/package SDK plus its compatible client using the application-specific instructions.

  5. Verify a bounded read in the target environment, test denial outside the intended restriction, and record secret rotation and revocation.

Tool Discipline

  • Use Glob to locate candidate repositories, manifests, configurations, and evidence without widening scope.
  • Use Grep to find relevant identifiers, declarations, permissions, errors, and stale claims.
  • Use Read to inspect the smallest required files and authoritative evidence.
  • Use Write only for a new approved local draft, test, manifest, or evidence artifact.
  • Use Edit only for a bounded approved change whose rollback is known.
  • Do not use file tools as a substitute for authenticated Foundry operations or owner approval.

Approval Boundaries

The application owner approves the OAuth client and redirect behavior; the Ontology or platform owner approves resource restrictions; the security owner approves secret storage; the data owner approves the verification read.

Output

An SDK decision, pinned dependency set, Developer Console configuration inventory, grant and principal, scope/restriction matrix, secret-store references, positive/negative verification, and rotation/revocation ownership.

Error Handling

Condition Response
A token works outside intended resources Tighten application restrictions and principal permissions, revoke affected credentials, and retest.
A client-credentials request is forbidden Check service-user permissions, scopes, and application restrictions independently.
Generated code disagrees with a copied example Use the target application's generated instructions and current SDK package as authoritative.
A secret appears in source or logs Revoke and rotate it immediately, remove it from history, and regenerate sanitized evidence.

Examples

Example 1

Bootstrap a TypeScript OSDK user application with Authorization Code grant, one selected object type, one Action, explicit redirect URLs, and a negative test for an unselected resource.

Example 2

Configure a Python Platform SDK backend service with Client Credentials grant, only the required operation restrictions and scopes, a secret-manager reference, and a bounded read verification.

Validation

  • The chosen SDK corresponds to the required API surface.
  • Grant type and acting principal match the application architecture.
  • Scopes, application restrictions, and Foundry permissions are all minimum and separately documented.
  • Dependencies are pinned to the generated/current compatible versions.
  • Revocation, rotation, and negative-access tests succeed.

Resources

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides standard instructions for installing and configuring the Palantir Foundry SDKs. It follows industry security best practices by recommending environment variable management for secrets and referencing official Palantir documentation and packages.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
version
2.0.0
argument-hint
[application-and-language]
model
inherit
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
compatibility
Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change
tags
[
  "saas",
  "palantir",
  "foundry",
  "installation",
  "oauth"
]

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/palantir-install-auth