Individual skill
palantir-cost-tuning
Reduce Foundry compute usage through measured engine, resource, incremental, schedule, and Compute Module decisions. Use when build or application usage is high or unpredictable. Trigger with "Foundry cost tuning" or "Palantir compute usage".
plugins/saas-packs/palantir-pack/skills/palantir-cost-tuning/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- palantir Declared skill tag
- foundry Declared skill tag
- cost Declared skill tag
- compute Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,063 bytesSKILL.mdcore · 5,063 bytesreferences/official-docs.mddoc · 1,021 bytes
Read excerpt
# Palantir Compute and Usage Optimization
## Overview
Optimize from measured Foundry usage and telemetry, not invented data-volume bands. Separate transform-build consumption from interactive Compute Module replica consumption because they have different controls and failure modes.
## Prerequisites
- Identify the pipeline, build jobs, Compute Modules, schedules, owners, service objectives, and current usage window.
- Capture build duration, requested and observed CPU/memory, queue time, input change rate, output volume, and module replica activity.
- Read `references/official-docs.md` and confirm contract-specific pricing or usage questions with the account owner or Palantir representative.
- Define correctness and latency constraints that cannot be traded away.
## Current Contract
