manage-scenarios

Snapshot fpa_yield_assumptions data into named budgeting scenarios per user and fiscal year.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/clenisa/optimal-cli --skill manage-scenarios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-scenarios
Source: https://github.com/clenisa/optimal-cli/tree/main/skills/manage-scenarios
Command: npx skills add https://github.com/clenisa/optimal-cli --skill manage-scenarios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages named budget scenarios for Wes projections by snapshotting fpa_yield_assumptions per user and fiscal year.

Core Features & Use Cases

  • Save a current set of fpa_yield_assumptions as a named scenario with metadata (name, created_at, user_id, row_count)
  • Load a named scenario to overwrite current data for a user and fiscal year, with a backup created beforehand
  • List all saved scenarios with name, created_at, fiscal_year, row_count, and owner
  • Compare two scenarios side-by-side to compute deltas in units, revenue projections, and program-level differences
  • Delete a named scenario (with optional confirmation)

Quick Start

Use optimal manage-scenarios to save a current set of assumptions as a named scenario.

Frequently Asked Questions about manage-scenarios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save and compare budget projections for what-if analysis?

You save budget projections by snapshotting fpa_yield_assumptions data per user and fiscal year into named scenarios. You can then compare two scenarios side-by-side to compute deltas in units, revenue projections, and program-level differences for what-if analysis.

Can I load a saved budget scenario without losing my current data?

Loading a named budget scenario overwrites current fpa_yield_assumptions data for a specific user and fiscal year, but the system automatically creates a backup beforehand to prevent data loss.

What metadata is tracked when saving budget scenarios?

Saved budget scenarios track metadata including the scenario name, creation timestamp, user ID, fiscal year, and row count. You can list all saved scenarios to view these details along with the owner information.

Do I need a Supabase environment to manage budget scenarios?

Yes, managing budget scenarios requires the environment variables RETURNPRO_SUPABASE_URL and RETURNPRO_SUPABASE_SERVICE_KEY to access the data store and persist fpa_yield_assumptions snapshots.

How do I delete a budget projection scenario safely?

You delete a named budget scenario using the delete operation, which supports optional confirmation to prevent accidental removal of saved fpa_yield_assumptions snapshots.