format-telegram-ads-report

Format Telegram Ads Report

Standardised output format for any Telegram Ads report delivered to the operator. This is a presentation-layer skill: it does not call tools, it tells the agent how to shape the result. Use it for snapshot, inspect_ad, account_diagnosis, review-campaign-results, custom analyses, and ad-hoc summaries.

The goal: any Telegram Ads report reads the same way. the operator can scan it, locate the numbers, and trust them.

Pointer to support files

• references/pipe-title-rendering.md — session-specific condensed reference for the markdown rendering rules around pipe (|) characters in account / ad / campaign titles. Captures the demonstrated failure mode (5-column shift bug) and the deterministic safe render templates (code block with fixed keys, bullet list). Read this when producing a cabinet-level or per-ad report whose title may contain |.

When to Use

• The output of any Telegram Ads tool or workflow is being delivered to the operator.
• A custom analysis (CTR trend, CPA breakdown, budget pacing, audience comparison) is being composed from raw tool output.

When NOT to Use

• The output is a structured approval request (use create-telegram-ads-campaign-workflow §"Approval Request Format" instead).
• The output is a structured error envelope (use the raw {"ok": false, "error": "…"} form, do not wrap it).
• The output is for another agent (DeepSeek review) — they get raw data, not the human-facing report.

Required Sections (in order)

For standard reports (snapshot, inspect_ad, account_diagnosis, custom summary):

## Summary
## Cabinet
## Campaigns
## Performance
## Anomalies / Data Quality
## Risks
## Recommendations (if any)
## Next actions
## Approval required (if any)

For ad-hoc question ("how is ad #142 doing?"):

## Answer
## Facts
## Anomalies / Data Quality
## Risks (if any)
## Next actions (if any)

For rejection diagnosis (delegated to handle-telegram-ads-review-and-declines):