performance-analysis

Creative Performance Analysis

Analyze creative performance using the creative-strategist skill methodology — multi-metric landscape, demographic overlay, and creative taxonomy. Produce an actionable report of what's working, what's scaling, and what's dying.

---

Phase 0: Orient

Before pulling data:

1. Acknowledge: "I'll analyze your creative performance to find what's working, scaling, and dying."
2. Detect complexity: Is this a quick question ("how's ROAS?") or a full deep dive ("what's working?")? Quick questions get 1-2 tool calls and a direct answer. Full analysis gets the multi-metric sweep.
3. Ask if ambiguous: "Quick top-line or full deep dive? Any specific metric or time period you care about?"
4. Connected workflow: After analysis, you can create concepts (/create-concepts), find iterations (/find-iterations), or dive into a specific ad (/analyze-ad).

If the user provides clear, specific intent (e.g., "full performance analysis for last 30 days"), skip questions and deliver.

---

Phase 1: Setup

1a. Parse Arguments

• --datePreset: Time window for analysis. Default: LAST_30_DAYS. Options: TODAY, YESTERDAY, THIS_MONTH, LAST_MONTH, LAST_7_DAYS, LAST_14_DAYS, LAST_30_DAYS, LAST_90_DAYS.
• --limit: Max creatives per metric query. Default: 10.
• --metric: Optional focus metric (SPEND, SCALING, HOOK, CPC, CTR_ALL, PURCHASES, PURCHASE_VALUE, or the workspace's goalMetric). If provided, lead the analysis with this metric. If not, use the standard multi-metric approach.

1b. Load Settings & Auth

1. Read ${CLAUDE_PLUGIN_ROOT}/motion-creative.config.md for org-specific configuration. If the file does not exist, use these defaults and suggest the user run /customize:
   • primary_kpi: use goalMetric from first get_creative_insights response
   • default_date_preset: LAST_30_DAYS
   • default_creative_limit: 10
   • demographic_focus: both
   • primary_metrics / secondary_metrics / exclude_metrics: auto-detect
   • priority_glossary_categories: use all
   • Brand guidelines: pull from get_workspace_brand
2. Call get_auth_context() to resolve workspaceId (use settings workspace_id as fallback context).
3. If settings contain a primary_kpi and no --metric was specified, use the primary KPI to lead the analysis.
4. If settings contain target_demographics, weight demographic analysis toward those segments.
5. If settings contain primary_metrics, ensure those metrics lead the analysis. If secondary_metrics, include after primary. If exclude_metrics, omit those from all queries and output.
6. Use default_date_preset from settings as the datePreset for all calls unless the user provided a --datePreset argument. Use default_creative_limit from settings as the limit unless the user provided a --limit argument.