← Marketing CompassCONTENT HISTORY

Update to Marketing Compass

Snapshot Sep 30, 2026 · 23:14 UTC · version 1.1.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Audit marketing proposals, analyses, reports, dashboards, case studies, and frameworks for causal validity, evidence quality, reproducibility, context transfer, information freshness, ethical risk, and real-world implementability. Use when evaluating whether correlation supports causation, whether a successful case generalizes, whether metrics or models justify a decision, why a theoretically sound proposal may fail in practice, or how to rewrite a marketing claim into a falsifiable and operational form. Route measurement-system design and metric calculations primarily to design-marketing-measurement; route broad growth diagnosis primarily to diagnose-marketing-structure.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 502
    },
    {
      "relative_path": "assets/icon.svg",
      "size_in_bytes": 524
    },
    {
      "relative_path": "references/implementation-and-freshness.md",
      "size_in_bytes": 2621
    },
    {
      "relative_path": "references/output-contract.md",
      "size_in_bytes": 1735
    },
    {
      "relative_path": "references/reasoning-audit.md",
      "size_in_bytes": 3225
    }
  ],
  "name": "audit-marketing-reasoning",
  "skill_md_contents": "---\nname: audit-marketing-reasoning\ndescription: Audit marketing proposals, analyses, reports, dashboards, case studies, and frameworks for causal validity, evidence quality, reproducibility, context transfer, information freshness, ethical risk, and real-world implementability. Use when evaluating whether correlation supports causation, whether a successful case generalizes, whether metrics or models justify a decision, why a theoretically sound proposal may fail in practice, or how to rewrite a marketing claim into a falsifiable and operational form. Route measurement-system design and metric calculations primarily to design-marketing-measurement; route broad growth diagnosis primarily to diagnose-marketing-structure.\n---\n\n# Marketing Reasoning Audit\n\nAudit consequential claims without turning the review into fault-finding. Preserve the useful core, expose uncertainty, and convert criticism into a safer decision or a small validation step.\n\n## Operating principles\n\n- Treat frameworks as subordinate to observed reality.\n- Separate business outcomes from the proposed marketing mechanism.\n- Distinguish fact, interpretation, hypothesis, unknown, and recommendation.\n- Do not convert correlation, model output, or a successful case into causation by wording alone.\n- Treat missing information as a reason to condition a decision, not automatically to stop it.\n- Describe incentive, political, or operational risks as hypotheses unless directly evidenced.\n- Protect customer trust; weak signals do not create strong permission to sell.\n- Date unstable assumptions and verify current facts when the decision depends on them.\n\n## Workflow\n\n### 1. Define the audit object\n\nIdentify:\n\n- the decision the material is meant to support;\n- the material claims that could change that decision;\n- the population, market, channel, product, period, and organization in scope;\n- the cost of being wrong and the reversibility of the action.\n\nIf scope is unclear, state a provisional scope and ask only for information that could materially change the verdict.\n\n### 2. Build a claim map\n\nFor each material claim, trace:\n\n`evidence -> inference -> conclusion -> proposed action`\n\nLabel every element as fact, interpretation, hypothesis, unknown, or recommendation. Flag any skipped link, undefined term, proxy presented as an outcome, or meaning formula presented as a calculation formula.\n\nRead [reasoning-audit.md](references/reasoning-audit.md) when auditing a report, case study, model, or causal claim in detail.\n\n### 3. Audit evidence and causality\n\nCheck at minimum:\n\n- denominator, distribution, comparison group, and time window;\n- time order and a credible counterfactual;\n- common causes, reverse causality, selection bias, and survivorship bias;\n- measurement error, aggregation, collinearity, seasonality, and repeated testing;\n- whether the evidence measures behavior, attitude, recall, revenue, or only a proxy;\n- whether alternative explanations remain plausible.\n\nUse four evidence levels:\n\n- **A — causal:** credible experiment or strong quasi-experimental design.\n- **B — triangulated:** multiple independent methods support the same direction.\n- **C — observational:** association or model estimate with unresolved alternatives.\n- **D — hypothesis:** expert judgment, anecdote, analogy, or untested mechanism.\n\nDo not treat MMM as automatic causal proof. Use it primarily for hypotheses, anomaly detection, model and data audit, broad ranges, and directional risk. Pair it with experiments, Geo tests, surveys, or other evidence when the decision needs incrementality.\n\n### 4. Audit transfer and reproducibility\n\nTest whether the reasoning survives changes in:\n\n- customer and buying situation;\n- product category and price;\n- competitive structure and distribution;\n- channel, creative, and timing;\n- operating capacity, incentives, and approval process.\n\nLook for failed, neutral, and excluded cases—not only winners. A single high-CTR campaign, viral post, or successful company is evidence of possibility, not a universal rule.\n\n### 5. Audit freshness and implementation\n\nRead [implementation-and-freshness.md](references/implementation-and-freshness.md) when the claim depends on changing platforms, AI, tactics, internal politics, incentives, or operational capacity.\n\nCheck:\n\n- when the source, data, and premise were last valid;\n- whether the mechanism has changed since then;\n- who must act, what process changes, and what capacity is required;\n- local KPI conflicts, workarounds, vested interests, and approval incentives;\n- whether the proposal is reversible, stageable, and observable after launch.\n\nDo not call a plan implementable merely because its logic is sound. Equally, do not use organizational friction as an excuse to abandon a valuable hypothesis; propose staged adoption and explicit conditions.\n\n### 6. Issue a decision and repair the claim\n\nChoose one verdict:\n\n- **Support:** evidence and implementation conditions justify the stated action.\n- **Conditional support:** useful direction, but scope or conditions must be explicit.\n- **Hold:** material unknowns make the current action premature; define the smallest test.\n- **Refute:** evidence contradicts the claim or the inference is structurally invalid.\n\nFor every important weakness, provide:\n\n1. the original risk;\n2. a corrected, falsifiable wording;\n3. the smallest useful validation;\n4. implementation and withdrawal conditions.\n\nUse [output-contract.md](references/output-contract.md) for the final structure.\n\n## Routing boundaries\n\n- Use `design-marketing-measurement` first for KPI architecture, experimental design, MMM specification, or metric calculation. Apply this skill as a second-line reasoning audit.\n- Use `diagnose-marketing-structure` first when the primary question is why revenue or growth is weak and the bottleneck is unknown.\n- Use `evaluate-ad-investment` first for budget, media, brand-versus-performance, or investment classification decisions.\n- Use `assess-ma-crm-ltv` first for MA, CRM, retention, lifecycle, or LTV suitability.\n- Use this skill first when the artifact's logic, evidence, generalizability, freshness, or implementation assumptions are themselves under review.\n\n## Guardrails\n\n- Do not diagnose a person's motives, competence, or psychology from a proposal.\n- Do not hide behind “it depends”; name the variables on which it depends.\n- Do not block reversible learning because perfect information is unavailable.\n- Do not present proprietary terminology as an established industry standard.\n- Do not optimize a KPI in a way that predictably damages trust or long-term choice.\n- Do not erase rejected, non-buying, or churned people from stakeholder analysis.\n- Do not confuse a polished audit with truth; disclose residual uncertainty.\n"
}

SHA-256 of public snapshot: 1789480ed522431471f5214bc0c1b5340b68240eb79120f2c59d507d6df53fde