ClaudeSuperPower
SubmitLog in

solving-specific-use-cases

Skill

Always use this skill when building or extending models for specific planning domains — FP&A, Workforce Planning, Sales Performance Management, Supply Chain Planning, or Financial Consolidation. Covers proven modeling patterns and domain-specific best practices. This skill includes supporting files

0Finance

Install

git clone https://github.com/gopigment/ai-plugins.git ~/.claude/skills/solving-specific-use-cases

What is solving-specific-use-cases?

Always use this skill when building or extending models for specific planning domains — FP&A, Workforce Planning, Sales Performance Management, Supply Chain Planning, or Financial Consolidation. Covers proven modeling patterns and domain-specific best practices. This skill includes supporting files in this directory - explore as needed.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~85 tokens of context used while enabled, before you invoke anything

Documentation

README · ~4 min read

Pigment Use Cases — Introduction

Pigment is a business planning platform used across multiple domains. Each domain has its own modeling patterns, dimensions, and reporting needs, but they all share Pigment's core building blocks: lists, metrics, formulas, tables, and boards.

This skill introduces the five primary use cases and explains what each one typically involves so the agent can orient itself when helping users build or extend a model. The list of patterns is not complete.

When to Use This Skill

Read this skill when:

  • You are deciding which patterns, dimensions, and structures are appropriate for a specific use case
  • You want to understand how different planning domains connect within a single Pigment organization
  • You are designing or integrating FX currency conversion (Hub app, rates by version, entity mapping, AVG/END, reporting currency)

Planning-cycle topics (Version Dimension, Budget vs Actual, Forecast, Reforecast, switchover, Actual/Plan layering, scenarios, snapshots) are NOT covered here. They are owned by skill:planning-cycles-pigment-applications. Most patterns below (Centralized Reporting Metric, OPEX, Workforce, FX) assume a Version Dimension already exists; consult that skill before building the planning-cycle layer of the model.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.