Agent skill

Palantir Local Dev Loop

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds.

MITAuto-check passedTesting & QA

Install Palantir Local Dev Loop

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill palantir-local-dev-loop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace palantir-local-dev-loop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/palantir-local-dev-loop .claude/skills/palantir-local-dev-loop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
palantir-local-dev-loop
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
616 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds.

  • Works in 5 steps: Separate pure transformation or… → Write deterministic unit tests using… → Synchronize the sandbox branch, run… → …
  • Iterating on transforms
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Palantir Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds. Use when iterating on transforms or OSDK code. Trigger with "Foundry local development".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change

It sits in Testing & QA, covering Unit testing. It works with Visual Studio Code. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Iterating on transforms
  • With Foundry local development

Example prompts

  • “Foundry local development”
  • “/palantir-local-dev-loop”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Separate pure transformation or application logic from Foundry adapters and generated SDK code.
  2. Write deterministic unit tests using synthetic fixtures and run them before any platform request.
  3. Synchronize the sandbox branch, run Foundry checks, and preview representative inputs with protected-data rules intact.
  4. Use the Foundry debugger for Python transform behavior when needed; treat observed values as diagnostic only.
  5. Push the exact branch, run the full Foundry build or bounded OSDK smoke test, inspect results, and open a reviewed pull request.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change

    From compatibility in the SKILL.md frontmatter.

Context cost

Palantir Local Dev Loop loads about 1.3k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 65 tokens; SKILL.md has 616 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 616 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/palantir-local-dev-loop/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
palantir-local-dev-loop
description
Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds. Use when iterating on transforms or OSDK code. Trigger with "Foundry local development".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change
version
2.0.0
argument-hint
[code-repository-or-application]
model
inherit
effort
high
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, palantir, foundry, local-development, testing

Palantir Local and In-Platform Development Loop

Overview

Keep pure logic fast and local while treating Foundry preview, checks, and builds as separate evidence. A local mock can verify application logic, but it cannot prove Foundry permissions, lineage, transactions, or full-data behavior.

Prerequisites

  • Identify the Code Repository or Developer Console application, language, branch, data sensitivity, and target environment.
  • Install the supported Palantir VS Code extension or use an in-platform workspace as appropriate.
  • Read references/official-docs.md and the repository's generated in-platform documentation.
  • Prepare lightweight unit fixtures without production data and a sandbox branch.

Current Contract

  • Foundry Code Repositories support sandbox branches, automatic checks, unit tests, previews, pull requests, and full builds.
  • Preview can use sample or subset data; a full build runs on platform data and commits pipeline output.
  • The VS Code extension can preview, debug, synchronize, and initiate Foundry builds from a local workspace.
  • Local tests should isolate business logic and avoid relying on live external resources.

Authentication

Use the approved Palantir VS Code or Developer Console sign-in for the intended environment. Keep generated OAuth settings and any test credentials in approved local secret storage, and never place tokens or production object data in fixtures, logs, or repository files.

Instructions

  1. Separate pure transformation or application logic from Foundry adapters and generated SDK code.

  2. Write deterministic unit tests using synthetic fixtures and run them before any platform request.

  3. Synchronize the sandbox branch, run Foundry checks, and preview representative inputs with protected-data rules intact.

  4. Use the Foundry debugger for Python transform behavior when needed; treat observed values as diagnostic only.

  5. Push the exact branch, run the full Foundry build or bounded OSDK smoke test, inspect results, and open a reviewed pull request.

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.
Show full SKILL.md (254 more words)Show less

Approval Boundaries

Local iteration does not authorize production data access, writeback, full builds, or merges. Obtain data-owner approval for representative protected inputs and repository-owner approval for merge or production build.

Output

A reproducible development command map, synthetic fixtures, unit-test evidence, branch/commit, preview/debug findings, Foundry check/build results, and known differences between local, preview, and full execution.

Error Handling

ConditionResponse
Local tests pass but Foundry checks failUse the repository check details and compare dependency/build environments.
Preview passes but full build failsInspect full-data edge cases, resources, and input transactions; preview is not production proof.
Generated OSDK mocks driftRegenerate from Developer Console and update contract tests against the pinned package.
Debugger output differs from committed dataTreat debugger state as non-authoritative and verify the actual output transaction.

Examples

Example 1

Refactor a transform so its row-level normalization is a pure function covered by synthetic unit tests, then run Foundry preview and a branch build to verify dataset integration.

Example 2

Mock a generated OSDK client for application unit tests, then run a bounded non-production smoke test to prove OAuth restrictions, object selection, and pagination.

Validation

  • Unit fixtures contain no protected production data.
  • The sandbox branch and local workspace are synchronized at one exact commit.
  • Foundry checks and the relevant full build or smoke test pass.
  • Preview limitations and environment differences are documented.
  • The pull request receives the required independent review.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/palantir-local-dev-loop of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Palantir Local Dev Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Palantir Local Dev Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Palantir Local Dev Loop this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
MCP Testingadeze/raindrop-mcp188—~1.6kAutomated safety check: PassMIT
Debug Surefireeclipse-rdf4j/rdf4j420—~2.4kAutomated safety check: PassBSD-3-Clause
Code Completionfacioquo/stock-indicators-dotnet1.2k—~1.2kAutomated safety check: PassApache-2.0
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0

Similar skills

  • MCP Testing

    adeze/raindrop-mcp

    MCP Testing Strategies with Vitest, Inspector, and Integration Tests

    188 GitHub stars~1.6k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Debug Surefire

    eclipse-rdf4j/rdf4j

    Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…

    420 GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Code Completion

    facioquo/stock-indicators-dotnet

    Quality gates for finishing work in this repository — dead-code cleanup, Roslynator and dotnet format fixes, markdownlint, build, unit tests, documentation, and Obsolete migration shims — with the…

    1.2k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed
  • Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes
  • Test Writing Workflow

    iOfficeAI/AionUi

    Sets the test-writing workflow for the repository: risk-first scenario lists, behavior-focused Vitest tests, a full run before each commit and a coverage target.

    33k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Palantir Local Dev Loop

What does Palantir Local Dev Loop do?

Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds. Palantir Local Dev Loop is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run a safe Foundry development loop using the Palantir VS Code extension, unit tests, preview/debug, repository synchronization, and remote builds.

When should I use Palantir Local Dev Loop?

Palantir Local Dev Loop fits situations like: iterating on transforms; with Foundry local development.

How do I install Palantir Local Dev Loop in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill palantir-local-dev-loop -a claude-code`. Or copy the skill folder (skills/.curated/palantir-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/palantir-local-dev-loop in your project. Claude Code loads it when a task matches its description.

How do I install Palantir Local Dev Loop in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill palantir-local-dev-loop -a codex`. Or copy the skill folder (skills/.curated/palantir-local-dev-loop in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/palantir-local-dev-loop in your project. Codex loads it when a task matches its description.

Can I use Palantir Local Dev Loop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill palantir-local-dev-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/palantir-local-dev-loop, .gemini/skills/palantir-local-dev-loop, .github/skills/palantir-local-dev-loop and .opencode/skills/palantir-local-dev-loop in your project.

What does Palantir Local Dev Loop need to run?

SKILL.md names no scripts, command-line tools or credentials: Palantir Local Dev Loop is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Requires current Palantir Foundry documentation and approved access for any live resource, permission, data, build, application, or deployment change.

Does Palantir Local Dev Loop access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Palantir Local Dev Loop safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Palantir Local Dev Loop use?

Palantir Local Dev Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Palantir Local Dev Loop use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 270 tokens, read only when the agent opens those files.

What are the alternatives to Palantir Local Dev Loop?

Skills that share tags, products or a category with Palantir Local Dev Loop: MCP Testing (adeze/raindrop-mcp, 188 stars), Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars), Code Completion (facioquo/stock-indicators-dotnet, 1.2k stars) and Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Palantir Local Dev Loop?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.