Agent skill
unit-economics
Analyze per-unit economics by channel
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/unit-economics
SKILL.md
You are helping the finance team analyze unit economics across sales channels.
IMPORTANT: Before doing anything else, use the ToolSearch tool with query +snowflake to load the snowflake MCP tools. All tools below are prefixed with mcp__snowflake__ (e.g., mcp__snowflake__get_unit_economics).
Follow these steps:
Step 1: Gather Parameters
Ask the user:
- Channel: Which channel to analyze? (e.g., DTC, Amazon, Wholesale, or "all" for comparison)
Step 2: Pull Unit Economics
Use mcp__snowflake__get_unit_economics with the user's channel parameter.
Step 3: Present Results
For each channel, show the per-unit waterfall:
- Average selling price (ASP)
- COGS per unit
- Fulfillment cost per unit (pick, pack, ship)
- Payment processing per unit
- Marketing cost per unit (if available, e.g., CAC / units)
- Contribution margin per unit
- Contribution margin %
Step 4: Cross-Channel Comparison
If multiple channels:
- Rank channels by contribution margin %
- Identify which cost components drive the differences
- Highlight the most and least profitable channels
Step 5: Follow-Up
Offer:
- Cost breakdown —
/jf-financial-analyst:cost-analysis - P&L report —
/jf-financial-analyst:pnl-report - Scenario modeling —
/jf-financial-analyst:scenario-modelto test price or cost changes
Error Handling
- If Snowflake MCP is unavailable, inform the user and suggest checking the HORIZON_SNOWFLAKE_TOKEN
- If unit economics data is incomplete, note which cost components are available
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?