Operations

/ads report

Render a validated JSON run bundle

Claude Code
/ads report

Installed as a plugin? The same command is namespaced: /claude-ads:ads report

What it does

Renders Markdown, HTML, or PDF reports from a validated Claude Ads run bundle, so every format is a view of the same canonical data. Built for client deliverables and executive readouts that must stay faithful to the underlying evidence.

Use it to

  • Turn a finished audit into a client-ready PDF
  • Produce an executive summary that stays honest about evidence gaps
  • Export a prior audit or plan in a different format without re-running it
  • Generate Markdown for internal docs and HTML or PDF for clients from one run

How it works

  1. Accept only validated input

    The source must be a validated versioned bundle. Loose worker prose is rejected.

  2. Confirm the framing

    Run completeness, evidence coverage, privacy class, branding choice, audience, and output formats are confirmed before rendering.

  3. Render from canonical data

    All formats come from the same bundle through deterministic templates, so Markdown, HTML, and PDF never disagree.

  4. Preserve the substance

    Findings, confidence, evidence references, contradictions, missing inputs, actions, owners, and measurement windows survive rendering.

  5. Check and write atomically

    Structural checks run on all formats, visual and layout checks on HTML and PDF, then artifacts are written atomically and the manifest is updated.

Reads & produces

What it reads

  • A validated, versioned run bundle, never loose worker prose
  • Run completeness and evidence-coverage status
  • Privacy classification and branding choice
  • Requested audience and output formats

What it produces

  • Markdown, HTML, or PDF renderings of the same canonical bundle
  • Findings with confidence, evidence references, and contradictions preserved
  • Actions with owners and measurement windows intact
  • An updated run manifest recording every artifact written

Guardrails

What /ads report will and will not do, by contract. These boundaries are enforced in the skill itself, not left to judgment.

  • Never hides a partial or insufficient-evidence status in an executive summary. If the run was partial, the report says so.
  • Excludes credentials, customer lists, private paths, raw research, and internal agent transcripts from every output.
  • Promotional copy appears only when the operator explicitly enabled branding.
  • Renders only from validated bundles, so a report can never contain claims that skipped validation.

Questions

Can I get the same report as Markdown for my team and PDF for the client?

Yes. All formats render from the same canonical JSON bundle through deterministic templates, so the Markdown, HTML, and PDF versions carry identical findings and numbers.

Will the executive summary gloss over missing data?

No. Partial and insufficient-evidence statuses are preserved everywhere, including the executive summary. That is a contract rule, not a formatting choice.

Why does report refuse my pasted analysis text?

Report only renders validated versioned bundles. Loose prose has no schema, lineage, or validation, so it cannot become a report the toolkit stands behind.