choosing-formula-patterns
Skill from gopigment/ai-plugins
Install
npx skills add gopigment/ai-plugins --skill choosing-formula-patterns
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install pigment@pigment
This skill is part of the plugin “pigment”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the choosing-formula-patterns skill do?
Description from the SKILL.md in the source repository.
Questions about choosing-formula-patterns
What does the choosing-formula-patterns skill do?
Planning skill. Use before writing formulas to decide which patterns and modifiers are needed for the use case. Maps business requirements to formula pattern combinations.
How do I install choosing-formula-patterns?
In a terminal: npx skills add gopigment/ai-plugins --skill choosing-formula-patterns. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use choosing-formula-patterns?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is choosing-formula-patterns safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from gopigment/ai-plugins
Execution skill. Use when configuring an application calendar — choosing calendar type, fiscal year, date range, and time dimensions.
Planning skill. Supply chain use cases: demand planning, inventory management, procurement planning, S&OP alignment. Each use case has inline guidance.
Planning skill. Sales performance use cases: quota planning, commission calculations, territory assignment, attainment tracking, pipeline coverage. Each use case has inline guidance.
Planning skill. FP&A use cases: budget/expense planning, revenue forecasting, P&L reporting, multi-currency, financial consolidation. Each use case has inline guidance; load sub-files only for advanced patterns.
Execution skill. Use when sharing metrics or lists between Pigment Applications via Libraries and cross-Application formula references.
Execution skill. Use when investigating slow inputs, slow calculations, or timeouts with the Performance Insights tools (performance_profile_change, performance_profile_change_scope_details, performance_slowest_changes, performance_changes_statistics, get_top_blocks_by_performance). Covers which tool to call, the includeAllExecutions default, reading change profiles (X/Y scope, contention, impacted viewed data), drilling into the scoped dimensions of some executions, locating the bottleneck, and comparing timings before/after a fix. Always profile before formula changes; never optimize from assumptions.
Execution skill. Use when writing PREVIOUS, PREVIOUSOF, or PREVIOUSBASE formulas, configuring iterative calculation cycles, or debugging circular dependency errors.
Execution skill. Use when naming or organizing Pigment Applications, folders, and blocks so models stay navigable, formula-safe, and consistent across teams.
Related skills in Writing & Marketing
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
Writing, exploit: shape raw material into an article, paragraph by paragraph.
Writing, explore: mine raw fragments, no structure yet.
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment