Agent skill · software engineering · jeremylongshore
palantir-debug-bundle
Collect a minimal, redacted Foundry diagnostic bundle for API, OSDK, transform, or Compute Module incidents. Use when support or engineering needs reproducible evidence without credentials or protected data. Trigger with "Palantir debug bundle".
Why this skill is useful
Adds an executable script for collecting and packaging diagnostic information specific to Palantir Foundry, which the AI wouldn't 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 Redacted Diagnostic Bundle Overview Collect identifiers and platform evidence that allow another operator to reproduce the failure while excluding bearer tokens, secrets, object values, dataset rows, and unnecessary logs. The bundle is an inventory and evidence manifest, not an indiscriminate archive. Prerequisites Identify the failure surface, time window, owner, support case, audience, and maximum allowed data classification. Obtain request IDs, build IDs, repository branch/commit, module version, SDK package versions, and non-secret environment metadata. Read references/official-docs.md and confirm whether log access is enabled and appropriately marked. Create the bundle in an access-controlled temporary location with an expiration owner. Current Contract Foundry build reports, debugger sessions, and metrics are distinct evidence surfaces. Service and trace logs can contain values from prompts, objects, or upstream systems; viewing them can require Edit permission, log access, and markings. A caller can record OAuth grant type and scope names without recording a bearer token or client secret. Python transform debugging is an interactive investigation tool; debugger values are not proof of committed output. Instructions 1. Write a manifest naming the incident, audience, time window, collection authority, and prohibited data. 2. Collect exact IDs, versions, branch/commit, timestamps, status or error names, sanitized request metadata, and relevant platform links. 3. Export only the smallest log excerpts authorized for the audience and replace tokens, secrets, personal data, and protected values with typed redaction markers. 4. Reproduce the issue with a safe request, preview, or sandbox build and record the result. 5. Review the bundle against the prohibition list, compute file hashes, set an expiration, and transfer through the approved channel. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-debug-bundle--dc3587