palantir-webhooks-events
Implement Palantir Foundry webhook handling for Ontology change events. Use when reacting to Ontology object changes, dataset updates, or build completion events from Foundry. Trigger with phrases like "palantir webhook", "foundry events", "palantir notifications", "ontology change events". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-webhooks-events --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Palantir Webhooks & Events ## Overview Handle Foundry webhook events for Ontology changes, dataset updates, and build completions. Covers webhook registration via the Foundry API, signature verification, event routing, and idempotent processing. ## Prerequisites - Foundry enrollment with webhook support enabled - HTTPS endpoint accessible from Foundry's network - `foundry-platform-sdk` installed
What does the palantir-webhooks-events skill do?
Implement Palantir Foundry webhook handling for Ontology change events. Use when reacting to Ontology object changes, dataset updates, or build completion events from Foundry. Trigger with phrases like "palantir webhook", "foundry events", "palantir notifications", "ontology change events". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill palantir-webhooks-events --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.