[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7949QS5WM9XCAPEE7YAE89M":3,"skill-same:01M7949QS5WM9XCAPEE7YAE89M":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M7949QS5WM9XCAPEE7YAE89M","palantir-reference-architecture",null,"Implement Palantir Foundry reference architecture with best-practice project layout.\nUse when designing new Foundry integrations, planning data pipeline architecture,\nor establishing patterns for Ontology-driven applications.\nTrigger with phrases like \"palantir architecture\", \"foundry best practices\",\n\"foundry project structure\", \"how to organize palantir\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--palantir-pack--palantir-reference-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: palantir-reference-architecture\ndescription: |\n  Implement Palantir Foundry reference architecture with best-practice project layout.\n  Use when designing new Foundry integrations, planning data pipeline architecture,\n  or establishing patterns for Ontology-driven applications.\n  Trigger with phrases like \"palantir architecture\", \"foundry best practices\",\n  \"foundry project structure\", \"how to organize palantir\".\nallowed-tools: Read, Grep\nversion: 2.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, palantir, foundry, architecture, patterns]\ncompatible-with: claude-code, codex, openclaw\n---\n\n# Palantir Reference Architecture\n\n## Overview\nProduction-ready architecture for Foundry-integrated applications. Covers the standard data pipeline pattern (ingest > clean > model > serve), Ontology design, external API integration, and multi-repo project layout.\n\n## Prerequisites\n- Foundry enrollment with project access\n- Understanding of Ontology concepts (object types, link types, actions)\n- Familiarity with `palantir-core-workflow-a` (transforms) and `palantir-core-workflow-b` (Ontology)\n\n## Instructions\n\n### Step 1: Data Pipeline Architecture\n```\n┌─────────────┐     ┌──────────────┐     ┌─────────────┐     ┌───────────┐\n│  Raw Layer   │────>│  Clean Layer │────>│ Model Layer │────>│ Ontology  │\n│ (ingested)   │     │  (validated) │     │ (enriched)  │     │ (objects) │\n└─────────────┘     └──────────────┘     └─────────────┘     └───────────┘\n  ↑ Connectors        @transform_df       @transform_df       Object types\n  ↑ REST sync          null checks         joins, aggs         Link types\n  ↑ File upload        type casting        ML features         Actions\n```\n\n### Step 2: Project Layout (Foundry)\n```\nFoundry Project: \"Customer Analytics\"\n├── Datasets\u002F\n│   ├── raw\u002F                    # Ingested from sources\n│   │   ├── raw_orders          # REST connector → CRM\n│   │   ├── raw_customers       # JDBC connector → DB\n│   │   └── raw_products        # File upload (CSV\u002FParquet)\n│   ├── clean\u002F                  # Validated, typed\n│   │   ├── clean_orders        # Nulls removed, dates parsed\n│   │   ├── clean_customers     # Deduped, normalized\n│   │   └── clean_products      # Schema enforced\n│   └── model\u002F                  # Enriched, analytics-ready\n│       ├── order_enriched      # Joined with customer + product\n│       ├── customer_360        # Aggregated customer view\n│       └── daily_summary       # Time-series aggregation\n├── Code Repositories\u002F\n│   ├── pipeline-ingestion\u002F     # Connectors and raw → clean\n│   ├── pipeline-analytics\u002F     # Clean → model transforms\n│   └── ontology-actions\u002F       # Action implementations\n└── Ontology\u002F\n    ├── Object Types: Customer, Order, Product\n    ├── Link Types: Customer→Orders, Order→Products\n    └── Actions: createOrder, updateCustomerSegment\n```\n\n### Step 3: External API Integration Pattern\n```python\n# External app consuming Foundry Ontology via Platform SDK\nmy-external-app\u002F\n├── src\u002F\n│   ├── foundry\u002F\n│   │   ├── client.py           # Singleton FoundryClient\n│   │   ├── objects.py          # Object query helpers\n│   │   ├── actions.py          # Action wrappers\n│   │   └── cache.py            # TTL cache layer\n│   ├── api\u002F\n│   │   ├── routes.py           # REST endpoints\n│   │   └── webhooks.py         # Foundry event handlers\n│   └── main.py\n├── tests\u002F\n│   ├── conftest.py             # Mocked FoundryClient\n│   ├── test_objects.py\n│   └── test_actions.py\n├── .env                        # FOUNDRY_HOSTNAME, credentials\n└── requirements.txt\n```\n\n### Step 4: Ontology Design Patterns\n| Pattern | When to Use | Example |\n|---------|-------------|---------|\n| Hub-and-spoke | Central entity with many relationships | Customer → Orders, Tickets, Payments |\n| Event sourcing | Audit trail needed | OrderEvent (created, shipped, delivered) |\n| Computed properties | Derived values | `totalRevenue` on Customer (sum of orders) |\n| Composite actions | Multi-step mutations | `processReturn`: update order + create credit + notify |\n\n### Step 5: Security Layers\n```\n┌──────────────────────────────────────────┐\n│ Layer 1: Network (VPN\u002Fprivate link)       │\n├──────────────────────────────────────────┤\n│ Layer 2: OAuth2 (service user per app)    │\n├──────────────────────────────────────────┤\n│ Layer 3: Scopes (minimum per app)         │\n├──────────────────────────────────────────┤\n│ Layer 4: Project roles (Viewer\u002FEditor)    │\n├──────────────────────────────────────────┤\n│ Layer 5: Marking (data classification)    │\n└──────────────────────────────────────────┘\n```\n\n## Output\n- Standard 3-layer data pipeline (raw > clean > model)\n- Ontology design with typed objects, links, and actions\n- External app architecture with caching and webhooks\n- Security model with 5 defense layers\n\n## Error Handling\n| Architecture Issue | Symptom | Fix |\n|--------------------|---------|-----|\n| Circular dependencies | Builds fail | Restructure pipeline DAG |\n| Missing clean layer | Bad data in model | Always validate between raw and model |\n| Monolithic transforms | Slow builds | Split into focused transforms |\n| No caching | API rate limits | Add TTL cache layer |\n\n## Resources\n- [Foundry Documentation](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry)\n- [Ontology SDK Overview](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry\u002Fontology-sdk\u002Foverview)\n- [Transforms Guide](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry\u002Ftransforms-python\u002Ftransforms)\n\n## Next Steps\nFor data handling and compliance, see `palantir-data-handling`.\n","# Palantir Reference Architecture\n\n## Overview\nProduction-ready architecture for Foundry-integrated applications. Covers the standard data pipeline pattern (ingest > clean > model > serve), Ontology design, external API integration, and multi-repo project layout.\n\n## Prerequisites\n- Foundry enrollment with project access\n- Understanding of Ontology concepts (object types, link types, actions)\n- Familiarity with `palantir-core-workflow-a` (transforms) and `palantir-core-workflow-b` (Ontology)\n\n## Instructions\n\n### Step 1: Data Pipeline Architecture\n```\n┌─────────────┐     ┌──────────────┐     ┌─────────────┐     ┌───────────┐\n│  Raw Layer   │────>│  Clean Layer │────>│ Model Layer │────>│ Ontology  │\n│ (ingested)   │     │  (validated) │     │ (enriched)  │     │ (objects) │\n└─────────────┘     └──────────────┘     └─────────────┘     └───────────┘\n  ↑ Connectors        @transform_df       @transform_df       Object types\n  ↑ REST sync          null checks         joins, aggs         Link types\n  ↑ File upload        type casting        ML features         Actions\n```\n\n### Step 2: Project Layout (Foundry)\n```\nFoundry Project: \"Customer Analytics\"\n├── Datasets\u002F\n│   ├── raw\u002F                    # Ingested from sources\n│   │   ├── raw_orders          # REST connector → CRM\n│   │   ├── raw_customers       # JDBC connector → DB\n│   │   └── raw_products        # File upload (CSV\u002FParquet)\n│   ├── clean\u002F                  # Validated, typed\n│   │   ├── clean_orders        # Nulls removed, dates parsed\n│   │   ├── clean_customers     # Deduped, normalized\n│   │   └── clean_products      # Schema enforced\n│   └── model\u002F                  # Enriched, analytics-ready\n│       ├── order_enriched      # Joined with customer + product\n│       ├── customer_360        # Aggregated customer view\n│       └── daily_summary       # Time-series aggregation\n├── Code Repositories\u002F\n│   ├── pipeline-ingestion\u002F     # Connectors and raw → clean\n│   ├── pipeline-analytics\u002F     # Clean → model transforms\n│   └── ontology-actions\u002F       # Action implementations\n└── Ontology\u002F\n    ├── Object Types: Customer, Order, Product\n    ├── Link Types: Customer→Orders, Order→Products\n    └── Actions: createOrder, updateCustomerSegment\n```\n\n### Step 3: External API Integration Pattern\n```python\n# External app consuming Foundry Ontology via Platform SDK\nmy-external-app\u002F\n├── src\u002F\n│   ├── foundry\u002F\n│   │   ├── client.py           # Singleton FoundryClient\n│   │   ├── objects.py          # Object query helpers\n│   │   ├── actions.py          # Action wrappers\n│   │   └── cache.py            # TTL cache layer\n│   ├── api\u002F\n│   │   ├── routes.py           # REST endpoints\n│   │   └── webhooks.py         # Foundry event handlers\n│   └── main.py\n├── tests\u002F\n│   ├── conftest.py             # Mocked FoundryClient\n│   ├── test_objects.py\n│   └── test_actions.py\n├── .env                        # FOUNDRY_HOSTNAME, credentials\n└── requirements.txt\n```\n\n### Step 4: Ontology Design Patterns\n| Pattern | When to Use | Example |\n|---------|-------------|---------|\n| Hub-and-spoke | Central entity with many relationships | Customer → Orders, Tickets, Payments |\n| Event sourcing | Audit trail needed | OrderEvent (created, shipped, delivered) |\n| Computed properties | Derived values | `totalRevenue` on Customer (sum of orders) |\n| Composite actions | Multi-step mutations | `processReturn`: update order + create credit + notify |\n\n### Step 5: Security Layers\n```\n┌──────────────────────────────────────────┐\n│ Layer 1: Network (VPN\u002Fprivate link)       │\n├──────────────────────────────────────────┤\n│ Layer 2: OAuth2 (service user per app)    │\n├──────────────────────────────────────────┤\n│ Layer 3: Scopes (minimum per app)         │\n├──────────────────────────────────────────┤\n│ Layer 4: Project roles (Viewer\u002FEditor)    │\n├──────────────────────────────────────────┤\n│ Layer 5: Marking (data classification)    │\n└──────────────────────────────────────────┘\n```\n\n## Output\n- Standard 3-layer data pipeline (raw > clean > model)\n- Ontology design with typed objects, links, and actions\n- External app architecture with caching and webhooks\n- Security model with 5 defense layers\n\n## Error Handling\n| Architecture Issue | Symptom | Fix |\n|--------------------|---------|-----|\n| Circular dependencies | Builds fail | Restructure pipeline DAG |\n| Missing clean layer | Bad data in model | Always validate between raw and model |\n| Monolithic transforms | Slow builds | Split into focused transforms |\n| No caching | API rate limits | Add TTL cache layer |\n\n## Resources\n- [Foundry Documentation](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry)\n- [Ontology SDK Overview](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry\u002Fontology-sdk\u002Foverview)\n- [Transforms Guide](https:\u002F\u002Fwww.palantir.com\u002Fdocs\u002Ffoundry\u002Ftransforms-python\u002Ftransforms)\n\n## Next Steps\nFor data handling and compliance, see `palantir-data-handling`.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"description":32,"allowed-tools":33,"compatible-with":34},[25,26,27,28,29],"saas","palantir","foundry","architecture","patterns","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","2.0.0","Implement Palantir Foundry reference architecture with best-practice project layout.\nUse when designing new Foundry integrations, planning data pipeline architecture,\nor establishing patterns for Ontology-driven applications.\nTrigger with phrases like \"palantir architecture\", \"foundry best practices\",\n\"foundry project structure\", \"how to organize palantir\".\n","Read, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--palantir-pack--palantir-reference-architecture",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill palantir-reference-architecture",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill palantir-reference-architecture",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill palantir-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--palantir-pack--palantir-reference-architecture\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]