creating-transaction-lists
Execution skill. Use when creating a transaction list, and whenever you aggregate rows from a transaction list into a metric — including a list that already exists in the application.
Install
With your agent
Install OMGSkills skill "gopigment/ai-plugins:skills/creating-transaction-lists" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gopigment/ai-plugins /tmp/ai-plugins && ln -s /tmp/ai-plugins/skills/creating-transaction-lists ~/.claude/skills/creating-transaction-listsFrom README
Creating Transaction Lists Recognize What a Transaction List Is A transaction list stores high-volume, row-based event data. Each row is one transaction or event. Items do not need to be unique (many rows can share the same product or date). Pigment auto-generates unique row IDs — source data does not need one. Represents granular events: orders, GL entries, bookings, movements, invoices. Cannot be used in a metric's structure — only referenced in formulas. Transaction lists hold transactional data; dimension lists hold metadata (products, accounts, employees). For deciding whether data belongs in a metric or a transaction list, see skill:creating-metrics-and-tables. Aggregate Transaction Lists into Metrics Transaction list data reaches metrics through aggregation: Date properties must map to calendar dimensions through a stored property, never through an inline conversion.