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. 达人预算分配/投放预算优化
71
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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.
Shortest invocation:
Help me allocate a $30,000 budget for an influencer campaign on Instagram and TikTokCommon scenario:
Optimize my influencer budget across micro and macro influencers for a Gen Z product launch — compare a $50K and a $100K scenarioOutput: a tier/platform/content allocation table, projected reach + CPM/CPE, 2-3 budget scenarios, and a recommended split.
~~influencer database / ~~social platform analytics when available.memory/influencer/budget-optimizer/YYYY-MM-DD-<topic>.md (or the declared paid path) only with exact WARM-save authorization.memory/hot-cache.md.NEEDS_INPUT with an exact evidence-request plan.Next Best Skill block below; a budget handoff never authorizes outreach or a send.Emit the standard shape from skill-contract.md §Handoff Summary Format.
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/.
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.
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.
NEEDS_INPUT; never supply a built-in default. Template: §Step 2.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.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.
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.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):
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.
64562bc
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.