Plan an A/B test by script: sample size per variant, days to run, stopping rules. "how many visitors per variant"
日本語の概要は準備中です。原文の説明を表示しています。
Run a quick what-if on 2-4 budget scenarios with revenue and ROI estimates. "compare two budget splits"
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Quick scenario comparison tool. Test 2-4 marketing scenarios against each other — different budget allocations, channel mixes, or strategic approaches — and see projected outcomes side-by-side. This is the lighter, faster alternative to full Monte Carlo simulation (/digital-marketing-pro:simulate). Where simulate runs thousands of iterations with full probability distributions, what-if uses point estimates with simple variance bands to give directional answers in minutes. Use it for rapid decision-making when you need a quick read on "should we do A or B?" without the statistical depth of a full simulation — team meetings, Slack discussions, quick planning calls, or narrowing down options before running a deeper analysis.
Simulated output — not a forecast. what-if projections are directional point-estimates produced by
revenue-simulator.pyfrom your stated assumptions and historical benchmarks, not measured predictions. Treat every scenario number as a planning aid: validate the ROI assumptions against your own data before committing budget. All example dollar figures in this skill are SYNTHETIC (illustrative only — never reuse these numbers).
The user must provide (or will be prompted for):
~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Pull historical channel performance, recent ROI data, and known benchmarks to calibrate scenario projections. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with industry defaults.revenue-simulator.py in what-if mode — a simplified projection that calculates expected revenue per scenario using point estimates with variance bands (not full Monte Carlo), applies basic diminishing returns for channels near saturation, and accounts for channel ramp time (SEO and content take months to deliver, paid is immediate). Faster execution, directional accuracy.A concise scenario comparison containing:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Plan an A/B test by script: sample size per variant, days to run, stopping rules. "how many visitors per variant"
日本語の概要は準備中です。原文の説明を表示しています。
Write ad copy variants to each platform's specs, policy-checked and in brand voice. "write ad copy for Meta"
日本語の概要は準備中です。原文の説明を表示しています。
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server"
日本語の概要は準備中です。原文の説明を表示しています。
Run a one-time AEO audit of six AI answer engines, scored per surface. "check our AI search visibility"
日本語の概要は準備中です。原文の説明を表示しています。
Plan AEO/GEO strategy to get cited by AI: content, entities, schema, 90-day plan. "how do we get cited by AI"
日本語の概要は準備中です。原文の説明を表示しています。
Build the agency dashboard across all client brands: health, pacing, risk. "how are all our clients doing"
日本語の概要は準備中です。原文の説明を表示しています。