Budget optimizer skill

Use when the user asks to "allocate my influencer budget", "optimize spend across tiers", or "compare budget scenarios".

by aaron-he-zhu·Apache-2.0 license·★ 2,858 Stars on the repo·GitHub ↗

Use now

Files of Budget optimizer

aaron-he-zhu/main1 file shown
SKILL.md
Show the full text129 lines

Budget Optimizer

This skill helps you allocate and optimize your influencer marketing budget to maximize return on investment. It considers platform costs, influencer tier economics, and campaign objectives to recommend optimal budget distribution.

Quick Start

Shortest invocation:

Help me allocate a $30,000 budget for an influencer campaign on Instagram and TikTok

Common scenario:

Optimize my influencer budget across micro and macro influencers for a Gen Z product launch — compare a $50K and a $100K scenario

Output: a tier/platform/content allocation table, projected reach + CPM/CPE, 2-3 budget scenarios, and a recommended split.

Skill Contract

  • Reads: total budget, fixed vs influencer-available split, campaign goal, target platforms, tier constraints (max per influencer, minimum count), industry, and — for mid-campaign work — spend-to-date and per-influencer results. Connector data via ~~influencer database / ~~social platform analytics when available.
  • Writes: return the budget allocation recommendation and handoff inline by default; save to memory/influencer/budget-optimizer/YYYY-MM-DD-<topic>.md (or the declared paid path) only with exact WARM-save authorization.
  • Promotes: only with separate exact authorization, promote the approved total budget, chosen scenario, locked tier mix, and spend constraints to memory/hot-cache.md.
  • Done when:
    1. Allocation sums to 100% of the stated budget; any contingency amount follows a user rule or a source-dated planning anchor rather than a repository default.
    2. Every projected metric includes its formula, input refs, evidence window, and Measured / User-provided / Estimated label.
    3. One recommended scenario is named with its rationale, or the numerical scenario remains NEEDS_INPUT with an exact evidence-request plan.
  • Primary next skill: use the readiness-gated Next Best Skill block below; a budget handoff never authorizes outreach or a send.
Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Cross-discipline: ad spend allocation

This skill also allocates paid-ads spend — the tier/platform tables map to channels/campaigns; use the ROAS profile (direct-response|prospecting|incremental-profit) as the scenario axis and read its declared CPA/payback/contribution constraint instead of substituting CPM/CPE. Scope: this computes the spend-reallocation plan only. It does not read in-flight pacing or issue scale-up/down moves — the live pacing read (pacing vs plan, learning-phase respect) belongs to budget-pacing-monitor, and bid-strategy choice belongs to bid-strategy-planner. paid-measurement-loop reads one shipped change back against a control, and premature scaling is an S guardrail flag in ad-account-auditor, not a separate skill or a veto. Save paid runs under memory/ad/budget-optimizer/.

Data Sources

This family has no required live integration, but numerical rate, multiplier, reach, engagement, revenue, and return projections require a compatible anchor: a user-provided quote or assumption, source-dated market evidence, or comparable first-party history. With only a total budget, platforms, and goal, return an allocation skeleton plus the exact rate-card/forecast queries needed and status NEEDS_INPUT; do not invent a repository rate table or multiplier.

Optional connectors that sharpen the estimates when present:

  • ~~influencer database — real rate cards instead of benchmark ranges.
  • ~~social platform analytics — actual reach, CPM, and engagement to replace estimated projections.
  • ~~CRM — past campaign spend and conversion data for ROI calibration.

Classify evidence field by field, not by connector provenance. Mark a connector value Measured only when it is an observed result for that exact metric, entity, and campaign window (record the source and as-of/window); mark numbers the user states User-provided; and mark benchmarks, forecasts, inferred values, and modeled downstream projections Estimated. A connector-backed input never upgrades an entire row or a projection derived from assumptions to Measured. See CONNECTORS.md for the keyless data recipes.

Instructions

When a user requests budget optimization, work these steps. Each step's fill-in template and scenario block lives in references/templates.md — copy the matching section and populate it.

  1. Gather budget parameters — campaign goal, audience, timeline, total budget, fixed vs influencer-available split, platform priorities, and constraints (max per influencer, min count). Intake template: §Step 1.
  2. Qualify cost evidence — inventory source-dated, market/platform/tier/deliverable/rights-compatible quotes or first-party history. A rate or multiplier without a compatible source and date stays NEEDS_INPUT; never supply a built-in default. Template: §Step 2.
  3. Create the allocation — split across tier, platform, content type, and other items (gifting, amplification, tools, contingency); sum to 100%. Use a contingency only when the user or a dated planning source supplied the rule. Template: §Step 3.
  4. Project returns — record each formula and input ref. Keep EMV as a separate media-equivalency scenario; never add it to attributed revenue or count it as cash return. Report ROAS = attributed revenue / spend as x:1; report arithmetic ROI as (attributed revenue - spend) / spend × 100%; do not claim profitability or incrementality without the required evidence. Template: §Step 4.
  5. Model scenarios — compare only scenarios supported by declared inputs; otherwise return named scenario shells and the missing-input plan. Template: §Step 5.
  6. Optimization strategies — label savings, concentration, and amplification thresholds as user rules or source-dated assumptions. Do not present unsourced percentages as standard. Detail: §Step 6.
  7. Mid-campaign reallocation — require comparable observed results plus a preregistered readback window and decision rule. Recommend KEEP_TESTING or NEEDS_INPUT when those are absent; a recommendation requires separate action authorization before spend changes. Persist and hand off creators only as creator_ref. Template: §Step 7.

Return the run inline. Offer memory/influencer/budget-optimizer/YYYY-MM-DD-<topic>.md (or memory/ad/budget-optimizer/ for paid-ads runs) for exact WARM-save authorization, and request a separate authorization before promoting the approved total, chosen scenario, or locked tier mix to memory/hot-cache.md.

Example

User: "Optimize a $30,000 budget for a skincare product launch on Instagram and TikTok targeting Gen Z"

Output:

## Budget Allocation: $30,000 Skincare Launch

**Status**: NEEDS_INPUT

The budget, platforms, audience, and goal are User-provided. No compatible creator quotes, deliverable/rights scope, contingency rule, reach/engagement history, conversion rate, AOV, or attribution basis was supplied, so no creator count, platform split, CPM, revenue, ROAS, ROI, or EMV is fabricated.

### Evidence request

| Needed input | Exact request |
|--------------|---------------|
| Cost basis | Dated creator quotes or first-party rates for the target market, platform, tier, deliverable, usage-rights term, exclusivity, and currency |
| Forecast basis | Comparable reach/engagement observations with source refs and windows |
| Return basis | Approved conversion rate, AOV, attribution window/method, and whether revenue is gross or net |
| Planning rules | User-approved platform/tier constraints, amplification amount, and contingency rule |

Until these arrive, provide only a 100%-summing allocation worksheet with `TBD` cells and no recommended numerical scenario.

Reference Materials

Next Best Skill

Primary: campaign-planner — when no approved execution-ready campaign plan exists, lock objectives, deliverables, rights, measurement, and decision rules before execution.

Alternates (same influencer family):

  • influencer-discovery — when the approved plan exists but a sourced shortlist does not; continue through discovery's documented typed-Fit handoff before treating any creator as selected.
  • outreach-manager — only when the campaign plan is approved, creators are selected after Fit, and contact/consent/channel readiness is documented. The handoff prepares outreach; it does not authorize a send.

Termination: keep a visited-set. If the recommended next skill was already invoked in this session's chain, stop and report chain-complete instead of re-invoking. Default max-depth: 3. When routing is ambiguous, present the options and stop rather than auto-following.

1---
2name: budget-optimizer
3slug: budget-optimizer
4displayName: "Budget Optimizer · 预算优化"
5summary: "跨创作者与层级的预算分配:目标导向的花费拆分与情景对比"
6description: 'Use when the user asks to "allocate my influencer budget", "optimize spend across tiers", or "compare budget scenarios"; produces a tier/platform/content allocation table, ROI and CPM/CPE projections, scenario comparisons, and mid-campaign reallocation moves. Not for building the full campaign plan — use campaign-planner. 达人预算分配/投放预算优化'
7version: "20.1.0"
8license: Apache-2.0
9compatibility: "Claude Code and compatible agent-skill hosts"
10homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
11when_to_use: "Use when planning budget allocation for a new influencer campaign, splitting spend across nano/micro/macro tiers or platforms, estimating influencer costs and projecting ROI, modeling conservative vs aggressive scenarios, justifying a budget request, or reallocating budget mid-campaign based on performance."
12argument-hint: "<total budget> [platforms] [campaign goal]"
13metadata: {"author": "aaron-he-zhu", "version": "20.1.0", "discipline": "influencer", "phase": "target", "geo-relevance": "low", "hermes": {"tags": ["marketing", "influencer", "target"], "category": "influencer"}, "openclaw": {"emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
14---
15 
16# Budget Optimizer
17 
18This skill helps you allocate and optimize your influencer marketing budget to maximize return on investment. It considers platform costs, influencer tier economics, and campaign objectives to recommend optimal budget distribution.
19 
20## Quick Start
21 
22Shortest invocation:
23 
24```
25Help me allocate a $30,000 budget for an influencer campaign on Instagram and TikTok
26```
27 
28Common scenario:
29 
30```
31Optimize my influencer budget across micro and macro influencers for a Gen Z product launch — compare a $50K and a $100K scenario
32```
33 
34Output: a tier/platform/content allocation table, projected reach + CPM/CPE, 2-3 budget scenarios, and a recommended split.
35 
36## Skill Contract
37 
38- **Reads**: total budget, fixed vs influencer-available split, campaign goal, target platforms, tier constraints (max per influencer, minimum count), industry, and — for mid-campaign work — spend-to-date and per-influencer results. Connector data via `~~influencer database` / `~~social platform analytics` when available.
39- **Writes**: return the budget allocation recommendation and handoff inline by default; save to `memory/influencer/budget-optimizer/YYYY-MM-DD-<topic>.md` (or the declared paid path) only with exact WARM-save authorization.
40- **Promotes**: only with separate exact authorization, promote the approved total budget, chosen scenario, locked tier mix, and spend constraints to `memory/hot-cache.md`.
41- **Done when**:
42 1. Allocation sums to 100% of the stated budget; any contingency amount follows a user rule or a source-dated planning anchor rather than a repository default.
43 2. Every projected metric includes its formula, input refs, evidence window, and Measured / User-provided / Estimated label.
44 3. One recommended scenario is named with its rationale, or the numerical scenario remains `NEEDS_INPUT` with an exact evidence-request plan.
45- **Primary next skill**: use the readiness-gated `Next Best Skill` block below; a budget handoff never authorizes outreach or a send.
46 
47### Handoff Summary
48 
49> Emit the standard shape from [skill-contract.md §Handoff Summary Format](../../../references/skill-contract.md).
50 
51## Cross-discipline: ad spend allocation
52 
53This skill also allocates **paid-ads** spend — the tier/platform tables map to channels/campaigns; use the ROAS profile (`direct-response|prospecting|incremental-profit`) as the scenario axis and read its declared CPA/payback/contribution constraint instead of substituting CPM/CPE. Scope: this computes the spend-reallocation **plan** only. It does **not** read in-flight pacing or issue scale-up/down moves — the live pacing read (pacing vs plan, learning-phase respect) belongs to [budget-pacing-monitor](../../../ad/scale/budget-pacing-monitor/SKILL.md), and bid-strategy choice belongs to [bid-strategy-planner](../../../ad/orchestrate/bid-strategy-planner/SKILL.md). [paid-measurement-loop](../../../ad/scale/paid-measurement-loop/SKILL.md) reads one shipped change back against a control, and premature scaling is an **S guardrail flag** in [ad-account-auditor](../../../ad/activate/ad-account-auditor/SKILL.md), not a separate skill or a veto. Save paid runs under `memory/ad/budget-optimizer/`.
54 
55## Data Sources
56 
57This family has no required live integration, but numerical rate, multiplier, reach, engagement, revenue, and return projections require a compatible anchor: a user-provided quote or assumption, source-dated market evidence, or comparable first-party history. With only a total budget, platforms, and goal, return an allocation skeleton plus the exact rate-card/forecast queries needed and status `NEEDS_INPUT`; do not invent a repository rate table or multiplier.
58 
59Optional connectors that sharpen the estimates when present:
60 
61- `~~influencer database` — real rate cards instead of benchmark ranges.
62- `~~social platform analytics` — actual reach, CPM, and engagement to replace estimated projections.
63- `~~CRM` — past campaign spend and conversion data for ROI calibration.
64 
65Classify evidence **field by field**, not by connector provenance. Mark a connector value **Measured** only when it is an observed result for that exact metric, entity, and campaign window (record the source and as-of/window); mark numbers the user states **User-provided**; and mark benchmarks, forecasts, inferred values, and modeled downstream projections **Estimated**. A connector-backed input never upgrades an entire row or a projection derived from assumptions to Measured. See [CONNECTORS.md](../../../CONNECTORS.md) for the keyless data recipes.
66 
67## Instructions
68 
69When a user requests budget optimization, work these steps. Each step's fill-in template and scenario block lives in [references/templates.md](references/templates.md) — copy the matching section and populate it.
70 
711. **Gather budget parameters** — campaign goal, audience, timeline, total budget, fixed vs influencer-available split, platform priorities, and constraints (max per influencer, min count). Intake template: [§Step 1](references/templates.md#step-1--budget-parameters-intake-template).
722. **Qualify cost evidence** — inventory source-dated, market/platform/tier/deliverable/rights-compatible quotes or first-party history. A rate or multiplier without a compatible source and date stays `NEEDS_INPUT`; never supply a built-in default. Template: [§Step 2](references/templates.md#step-2--cost-evidence).
733. **Create the allocation** — split across tier, platform, content type, and other items (gifting, amplification, tools, contingency); sum to 100%. Use a contingency only when the user or a dated planning source supplied the rule. Template: [§Step 3](references/templates.md#step-3--budget-allocation-recommendation).
744. **Project returns** — record each formula and input ref. Keep EMV as a separate media-equivalency scenario; never add it to attributed revenue or count it as cash return. Report `ROAS = attributed revenue / spend` as `x:1`; report arithmetic ROI as `(attributed revenue - spend) / spend × 100%`; do not claim profitability or incrementality without the required evidence. Template: [§Step 4](references/templates.md#step-4--return-projections).
755. **Model scenarios** — compare only scenarios supported by declared inputs; otherwise return named scenario shells and the missing-input plan. Template: [§Step 5](references/templates.md#step-5--budget-scenarios).
766. **Optimization strategies** — label savings, concentration, and amplification thresholds as user rules or source-dated assumptions. Do not present unsourced percentages as standard. Detail: [§Step 6](references/templates.md#step-6--optimization-strategies).
777. **Mid-campaign reallocation** — require comparable observed results plus a preregistered readback window and decision rule. Recommend `KEEP_TESTING` or `NEEDS_INPUT` when those are absent; a recommendation requires separate action authorization before spend changes. Persist and hand off creators only as `creator_ref`. Template: [§Step 7](references/templates.md#step-7--mid-campaign-reallocation).
78 
79Return the run inline. Offer `memory/influencer/budget-optimizer/YYYY-MM-DD-<topic>.md` (or `memory/ad/budget-optimizer/` for paid-ads runs) for exact WARM-save authorization, and request a separate authorization before promoting the approved total, chosen scenario, or locked tier mix to `memory/hot-cache.md`.
80 
81## Example
82 
83**User**: "Optimize a $30,000 budget for a skincare product launch on Instagram and TikTok targeting Gen Z"
84 
85**Output**:
86 
87```markdown
88## Budget Allocation: $30,000 Skincare Launch
89 
90**Status**: NEEDS_INPUT
91 
92The budget, platforms, audience, and goal are User-provided. No compatible creator quotes, deliverable/rights scope, contingency rule, reach/engagement history, conversion rate, AOV, or attribution basis was supplied, so no creator count, platform split, CPM, revenue, ROAS, ROI, or EMV is fabricated.
93 
94### Evidence request
95 
96| Needed input | Exact request |
97|--------------|---------------|
98| Cost basis | Dated creator quotes or first-party rates for the target market, platform, tier, deliverable, usage-rights term, exclusivity, and currency |
99| Forecast basis | Comparable reach/engagement observations with source refs and windows |
100| Return basis | Approved conversion rate, AOV, attribution window/method, and whether revenue is gross or net |
101| Planning rules | User-approved platform/tier constraints, amplification amount, and contingency rule |
102 
103Until these arrive, provide only a 100%-summing allocation worksheet with `TBD` cells and no recommended numerical scenario.
104```
105 
106## Reference Materials
107 
108- Templates, cost benchmarks, scenario A/B/C blocks, optimization tips & second example: [references/templates.md](references/templates.md)
109- Shared contract: [skill-contract.md](../../../references/skill-contract.md)
110- Shared state model: [state-model.md](../../../references/state-model.md)
111- Connector recipes: [CONNECTORS.md](../../../CONNECTORS.md)
112- Sibling skills:
113 - [campaign-planner](../campaign-planner/SKILL.md) — the campaign plan this budget funds
114 - [influencer-discovery](../../scout/influencer-discovery/SKILL.md) — find influencers in budget range
115 - [outreach-manager](../../activate/outreach-manager/SKILL.md) — turn the allocation into outreach
116 - [roi-calculator](../../report/roi-calculator/SKILL.md) — calculate actual ROI post-campaign
117 - [performance-analyzer](../../report/performance-analyzer/SKILL.md) — inform reallocation decisions
118 
119## Next Best Skill
120 
121**Primary**: [campaign-planner](../campaign-planner/SKILL.md) — when no approved execution-ready campaign plan exists, lock objectives, deliverables, rights, measurement, and decision rules before execution.
122 
123**Alternates** (same influencer family):
124 
125- [influencer-discovery](../../scout/influencer-discovery/SKILL.md) — when the approved plan exists but a sourced shortlist does not; continue through discovery's documented typed-Fit handoff before treating any creator as selected.
126- [outreach-manager](../../activate/outreach-manager/SKILL.md) — only when the campaign plan is approved, creators are selected after Fit, and contact/consent/channel readiness is documented. The handoff prepares outreach; it does not authorize a send.
127 
128**Termination**: keep a visited-set. If the recommended next skill was already invoked in this session's chain, stop and report chain-complete instead of re-invoking. Default `max-depth: 3`. When routing is ambiguous, present the options and stop rather than auto-following.
129 

Discussion

Alternatives

Ad campaign analyzerAnalyze ad campaign performance data (Google, Meta, LinkedIn) to identify what's working, what's wasting budget, and specific cut/scale/test recommendations. Runs statistical analysis, funnel diagnostics, and multi-channel budget reallocation with specific dollar-amount shift recommendations and scenario modeling.Business & ops · MITStartup financial modelingBuild comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups. Use this skill when creating financial projections, calculating burn rate or runway, modeling fundraising scenarios, or preparing investor-ready financials for a seed or Series A raise.Business & ops · MITProject managerUse this agent when you need to establish project plans, track execution progress, manage risks, control budget/schedule, and coordinate stakeholders across complex initiatives. Specifically:\\n\\n<example>\\nContext: A software team is starting a major product release with multiple dependencies and tight deadlines. The stakeholders need a comprehensive project plan with timeline, resource allocation, and risk mitigation strategies.\\nuser: "We're launching a new payment processing platform in Q2. Can you help us plan the project, identify risks, and set up tracking?"\\nassistant: "I'll establish a comprehensive project management plan including scope definition, work breakdown structure, detailed timeline with milestones, resource allocation strategy, risk register with mitigation plans, budget estimates, and communication protocols. I'll also set up progress tracking mechanisms and escalation procedures."\\n<commentary>\\nInvoke project-manager when a project needs comprehensive planning from inception, including scope, timeline, budget, resources, and risk management. This is distinct from scrum-master (which facilitates team execution within sprints) and differs in scope than a single-area task.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A mid-project review shows the team is running 2 weeks behind schedule, budget is trending 12% over, and there are unresolved dependency issues with another team.\\nuser: "Our project is sliding. We're behind schedule, over budget, and stuck waiting on another team. I need to understand what's happening and how to fix it."\\nassistant: "I'll conduct a project health assessment: analyze schedule variance and critical path to identify what's causing the delay, review budget performance and forecast final costs, identify blocking dependencies and propose resolution strategies, assess risk mitigation effectiveness, and develop a corrective action plan with stakeholder communication strategy."\\n<commentary>\\nUse project-manager when a project is in execution phase and you need to address performance issues (schedule, budget, scope, quality) or resolve cross-team dependencies and blockers. Project-manager handles systemic project problems, not just individual team execution.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A project is nearing completion with deliverables ready for handoff. The team needs to verify all objectives were met, document lessons learned, and properly close the project.\\nuser: "We're wrapping up the mobile app redesign. Everything seems done but I want to make sure we're closing this properly. Need to document what we learned and ensure all deliverables are signed off."\\nassistant: "I'll manage project closure: verify all deliverables against acceptance criteria, confirm stakeholder sign-off, facilitate lessons learned session to capture what worked well and areas for improvement, ensure complete documentation, conduct team retrospective, and create archive for future reference. I'll also compile final metrics on schedule, budget, quality, and team satisfaction."\\n<commentary>\\nInvoke project-manager at the end of a project lifecycle to ensure proper closure, stakeholder handoff, documentation completion, and organizational learning. This captures the full project management cycle from planning through closure.\\n</commentary>\\n</example>Business & ops · MIT/cs:cfo-review — CFO Forcing Questions/cs:cfo-review <plan> — Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation. Use when a plan commits meaningful spend — e.g. a hiring wave, a fundraise decision, or a new channel budget. · MIT