Agent skill · data analytics · jeremylongshore
palantir-data-handling
Design and verify Foundry data handling across projects, roles, mandatory controls, Ontology security, logs, exports, and retention. Use when processing sensitive or regulated data. Trigger with "Foundry data handling" or "Palantir markings".
Why this skill is useful
Adds specific Palantir Foundry scripts for PII protection and GDPR compliance that are not publicly documented.
What it needs
Requires palantir account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir Data Governance and Handling Overview Map the full data path before editing a permission or transform. Foundry discretionary roles, mandatory controls, Ontology row/property policies, and downstream exports protect different boundaries and must be reviewed separately. Prerequisites Identify data owner, purpose, classifications, source datasets, derived resources, Ontology objects and properties, logs, exports, and retention obligations. Record the projects, organizations, markings, CBAC policies, groups, and roles governing each stage. Read references/official-docs.md and involve the information-security or privacy owner for regulated data. Use synthetic data for policy tests unless a protected test environment is approved. Current Contract Projects and roles provide discretionary access, while organizations, markings, and CBAC remain mandatory and propagate according to their own rules. Ontology object and property policies can implement row- and column-level read controls; granular controls do not automatically protect downstream exports. Mandatory controls within security policies continue to protect derived data where the documented propagation rules apply. Logs and audit exports may contain sensitive or personal data and require explicit access, marking, retention, and audience decisions. Instructions 1. Draw the data-flow and authority map from ingestion through transforms, Ontology, applications, logs, and exports. 2. Classify each resource and define the minimum project roles, groups, mandatory controls, and application restrictions. 3. Configure Ontology object/property policies for read-time needs and pair them with mandatory controls when downstream propagation is required. 4. Define retention, deletion, export, and audit evidence procedures with accountable owners. 5. Test authorized, unauthorized, downstream-derived, log-viewing, and export cases before production. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-data-handling--2d5b9a