Help us improve
Share bugs, ideas, or general feedback.
From pigment
Imports CSV and Excel data into Pigment, mapping columns to properties and choosing between dimensions and transaction lists.
npx claudepluginhub gopigment/ai-plugins --plugin pigmentHow this skill is triggered — by the user, by Claude, or both
Slash command
/pigment:integrating-external-dataThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides guidance for importing external data into Pigment applications efficiently.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
This skill provides guidance for importing external data into Pigment applications efficiently.
There are three broad use-cases.
Use Decision Framework:
| Data Characteristic | Import To | Reason |
|---|---|---|
| Master data (customers, products, employees) | Dimension | Relatively static, used as dimension |
| Transactional data (orders, sales, movements) | Transaction List | High volume, time-stamped events |
| Static entities with properties | Dimension | Need to maintain properties/hierarchies |
| Granular event-based data | Transaction List | Aggregate to metrics using formulas |
From modeling-pigment-applications skill:
If unfamiliar → Use modeling-pigment-applications skill first
Read: ./data_import_csv.md
Quick Decision:
Excel imports are to be done according to the instructions in ./excel_import.md
Questions:
Read: ./integration_overview.md
Scenario: CSV columns don't exactly match property names
Examples:
Read: ./data_import_csv.md - "Semantic Column Matching" section
Key principle: Match by meaning, not exact name
Scenario: Importing customer, product, or employee master data
Steps:
Scenario: Importing orders, sales, or inventory movements
Steps:
Scenario: CSV columns don't exactly match property names
Approach:
| Use Dimension When | Use Transaction List When |
|---|---|
| Master data (customers, products, employees) | Transactional data (orders, sales, movements) |
| Relatively static data | High volume, time-stamped events |
| Used as dimension in metrics | Need to aggregate to metrics |
| Need to maintain properties/hierarchies | Granular event-based data |
| CSV Column | Matches Property | Type |
|---|---|---|
| "Pays" | "Country" | Translation (French) |
| "Emp" | "Employee" | Abbreviation |
| "Client" | "Customer" | Synonym |
| "email" | "Email" | Case variation |
| "PRODUCT_ID" | "Product ID" | Case + spacing |
Before Integration:
After Integration: