Individual skill
palantir-observability
Design Foundry observability using build metrics, execution history, governed logs, audit exports, and monitoring subscriptions. Use when defining dashboards, alerts, or operational evidence. Trigger with "Foundry observability" or "Palantir monitoring".
plugins/saas-packs/palantir-pack/skills/palantir-observability/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,917
- 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
- observability Declared skill tag
- monitoring Declared skill tag
- design 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,263 bytesSKILL.mdcore · 5,263 bytesreferences/official-docs.mddoc · 988 bytes
Read excerpt
# Palantir Foundry Observability Design
## Overview
Use Foundry-native telemetry for Foundry workloads and export only when there is a governed consumer. Distinguish operational metrics, service/trace logs, execution history, monitoring notifications, and audit logs because they have different access and retention semantics.
## Prerequisites
- Identify the resource, owner, service objectives, failure modes, audiences, data classification, and incident process.
- Inventory available build metrics, resource metrics, execution history, logs, monitoring views, audit exports, and external notification targets.
- Read `references/official-docs.md` and confirm current log-access and marking policy.
- Define the minimum telemetry needed to detect user-visible or data-quality failures.
## Current Contract