Pltr Cli

What This Skill Does

The Pltr Cli skill is a robust wrapper for the official Palantir Foundry Command Line Interface (pltr-cli). It provides an AI-augmented gateway to interact with your Foundry stack directly from the OpenClaw environment. Whether you are an analyst needing to pull dataset records, an orchestrator managing complex build schedules, or a platform administrator handling user permissions and security roles, this skill bridges the gap between natural language requests and complex CLI commands. It abstracts the intricate RID-based API requirements, allowing you to focus on high-level goals like "fetch the metadata for this dataset" or "trigger the nightly build schedule."

Installation

To integrate this skill into your environment, run the following command within your terminal: clawhub install openclaw/skills/skills/anjor/pltr-cli

Ensure that your environment meets the dependency requirements, specifically having Python 3.9+ and the foundry-platform-sdk version 1.69.0 or higher installed. Once installed, initialize your connectivity via pltr configure to set up your host URL and authentication tokens.

Use Cases

• Automated Data Discovery: Quickly list files within a dataset or retrieve schema information without opening the Foundry web interface.
• Orchestration Management: Monitor the status of ongoing builds or manually trigger dependency-heavy schedules during maintenance windows.
• Ontology Operations: Perform object-level operations, such as executing specific actions or querying object types, directly from your command workspace.
• Audit and Admin: Streamline the process of retrieving user access logs, group memberships, or inspecting role assignments across your Foundry projects.
• Cross-Environment Synchronization: Seamlessly manage deployments across development and production profiles by switching contexts with the --profile flag.

Example Prompts

1. "Pltr, list all the datasets located in the project folder with RID ri.compass.main.folder.12345 and export the results to a CSV file named output.csv."
2. "Can you check the current status of the build with RID ri.orchestration.main.build.67890 and tell me if it succeeded?"
3. "Run a SQL query against the dataset ri.foundry.main.dataset.abcde to count the number of rows where the status is 'active', and show me the results in a table format."

Tips & Limitations

• RID Knowledge: While the agent can help construct commands, you must provide the correct Resource Identifiers (RIDs). Keep a text file or reference sheet of your common project and dataset RIDs handy.
• Context Switching: Always verify your current profile using pltr --profile to ensure you aren't accidentally running administrative operations in your production instance when you intended to use development.
• Security: Be cautious when handling output files containing sensitive enterprise data. Ensure your local machine environment is secured and that sensitive tokens are stored using environment variables rather than hardcoded in scripts.