report-generator Checked

zation, promote durable evidence-backed facts (verified final ROI/ROAS, measured performance baselines, and headline learnings) to memory/hot-cache.md. The Retro Card's qualitative renew | retest | retire | unknown decision, rationale, next hypothesis, and limitations remain WARM and are not creator-registry facts. This skill makes no creator-registry proposal: after a creator row is closed, only a separately authorized, evidence-backed **actual rate**, **signed rights window/expiry**, or **measured performance baseline** may be proposed by the owning workflow; creator-registry (../../../protocol/creator-registry/SKILL.md) alone decides whether it becomes canonical.

• **Done when**:

1. The report matches the requested audience template (executive, client, team, or board).

2. Every metric is paired with compatible source-dated context (target, benchmark, or prior period) or explicitly marked Unknown/NEEDS_INPUT; the report does not manufacture context or recompute missing performance/return metrics.

3. The report ends with concrete recommendations and, where relevant, action items.

4. When current tracker-state evidence proves measured or closed, the report package preserves the matching performance-analyzer Retro Card with exact campaign/creator/state/measurement/decision-rule refs; a missing or invalid card produces an unknown placeholder and NEEDS_INPUT, never a newly derived decision.

5. Saved/copyable output contains only opaque client/preparer/contact/owner/creator refs; any resolved labels/contact details exist only in a transient render for the declared audience, and external distribution is blocked without a fresh audience-scoped exact authorization.

• **Primary next skill**: content-quality-auditor (../../../seo-geo/tune/content-quality-auditor/SKILL.md)

### Handoff Summary

> Emit the standard shape from skill-contract.md §Handoff Summary Format (../../../references/skill-contract.md).

Data Sources

This family ships Tier 1: no live integration is required. Give it already-computed, provenance-labeled campaign metrics and it builds the report. If only raw observations are supplied, route metric analysis to performance-analyzer; if only spend/revenue/LTV inputs are supplied, route return math to roi-calculator before reporting.

Optional connectors that can pre-fill data where available:

• ~~social platform analytics — reach, impressions, engagement, video views per post
• ~~influencer database — creator handles, tiers, fees, audience demographics
• ~~analytics — link clicks, conversions, attributed revenue
• ~~CRM — new-customer counts and downstream revenue

Without any of these, the skill asks for the existing computed artifacts/metrics. It may return a partial report shell, but any missing dependent claim remains Unknown/NEEDS_INPUT; it does not calculate ROI/ROAS, rankings, attribution, or causal drivers here. See CONNECTORS.md (../../../CONNECTORS.md) for the free/keyless data recipe per category.

Instructions

When a user requests a report:

1. **Determine report parameters** — set report type (post-campaign/monthly/quarterly/annual), campaign(s), period, one explicit audience, opaque client_ref/preparer_ref/contact_ref/owner_ref values where applicable, and supplied tracker stage when present. Match depth to the audience: executive wants ROI and strategy at a high level; client wants results and value; team wants detailed learnings and optimization; board wants business impact. Keep any raw identity/contact locator transient. See the audience-needs matrix in report-templates.md (references/report-templates.md).

2. **Pick the audience template and fill it in** — full executive, client, and internal-team templates live in report-templates.md (references/report-templates.md). Pull performance metrics/deltas only from performance-analyzer output and financial ratios only from roi-calculator output. If the required computed artifact is absent, return a partial shell plus NEEDS_INPUT and the exact handoff; do not recompute from raw numbers. Pair every metric with compatible source-dated context or mark the comparison pending.

3. **Apply visualization and writing guidance** — choose the right chart per data point and per audience, and follow the lead-with-outcomes narrative arc. See the visualization recommendations and writing best practices in report-templates.md (references/report-templates.md).

4. **Close with recommendations and action items** — end every report with concrete next steps; add an opaque owner_ref/deadline action-items table for team and board audiences.

5. **Represent the measured cycle without re-deciding it** — only preserve an existing Campaign Retro Card from performance-analyzer when it explicitly binds the same campaign_id, opaque creator_ref, current non-forked measured/closed tracker-state ref, locked measurement contract, and precommitted decision-rule ref. Never derive or change the decision in this reporting skill. If the card is absent, mismatched, or stale, emit a bound decision: unknown placeholder plus NEEDS_INPUT for the performance-analyzer artifact. Keep the card outside a client/board-facing copy unless the user requests it.

6. **Return, then offer persistence or distribution** — return the ref-only repor