using-mapped-dimensions
Execution skill. Use when modeling dynamic or time-dependent hierarchies, card metrics for flexible reporting (e.g. headcount by team/function via BY-arrow mappings), or any scenario where reporting breakdowns must differ from the structural dimensions on the metric.
Install
With your agent
Install OMGSkills skill "gopigment/ai-plugins:skills/using-mapped-dimensions" 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/using-mapped-dimensions ~/.claude/skills/using-mapped-dimensionsFrom README
Using Mapped Dimensions Mapped dimensions (time-dependent hierarchies, slowly changing dimensions) model parent-child relationships that change across periods. Past periods keep the old parent; future ones reflect the new assignment. Choose Between Static Properties and Mapped Dimensions | Criterion | Dimension-Type Property (static) | Mapped Dimension (dynamic) | | --- | --- | --- | | Relationship changes? | Rarely or never | Changes over time or by version | | History preservation | Updating the parent moves all history with the child | Each period retains its own parent assignment | | Where it works | Metric formulas, aggregation, views | Views only (Joined Pivot); core metrics stay lean | | Examples | Product to Category, Store to Region | Employee to Team (monthly), Cost Center to Department (re-org), Product to Promotion (seasonal) | Rule of thumb: if the parent-child mapping is the same for all periods, use a dimension-type property.