AI Services Market
AI Services Market › Fabbrica delle skill › Presentazioni › Slate Social Report Deck
$4.99 · Nessun login necessariov1.0.0– visualizzazioni

Slate Social Report Deck

Un report mensile che i clienti leggono davvero

Crea una presentazione di report mensile sui social media in un tranquillo stile grigio ardesia che mostra cosa è cresciuto, cosa ha funzionato e cosa fare dopo — con una storia, un tabellone e niente scarichi di screenshot.

Anteprima di Slate Social Report Deck
Ideale per
Social media manager e agenzie che riferiscono ai clienti
Tempo necessario
~30 min
Livello
Adatto ai principianti

Installala in 3 passaggi

Nessuna registrazione. Nessuno strumento da riga di comando. Scegli la tua AI, copia una riga e incollala.

Pro — tutte le 511 skill

Preferisci fare da te? Acquista la skill ($4.99), scarica lo ZIP dalla conferma d'acquisto, decomprimilo nella cartella mostrata sopra e riavvia la sessione della tua AI — stesso risultato. L'hai già acquistata? Il tuo assistente AI può scaricarla per te.

Cosa contiene

Un file SKILL.md (la guida operativa) + un modello di partenza. Un'anteprima:

Slate Social Report Deck

When to use

  • You manage social accounts for a client and the monthly report is due — and last month's was a 40-slide screenshot dump
  • Your agency needs one report format every account manager can fill in the same way
  • A client keeps asking "so what did we actually get for the money?" and your report doesn't answer it
  • You want to show a month of social performance to a non-technical stakeholder in under 10 minutes
  • You're turning a one-off report into a repeatable monthly template

Workflow

  1. Gather the month (input: platform analytics exports → output: raw numbers table)
    Pull the same set of numbers from every platform you report on: followers, reach, impressions, engagement (likes + comments + shares + saves), clicks, and conversions if tracked. Record this month and last month side by side, plus the goal if one was set. One table, one source of truth — no number appears in the deck unless it's in this table. If a platform changed its metric definitions, note it here so the deck doesn't compare apples to oranges.
  2. Find the story (input: raw numbers table → output: 3-bullet story)
    Before designing anything, answer three questions in plain sentences: What grew? (one line with the number) What worked? (the 1–3 posts or formats that drove the result, with why) What should change? (one concrete next step, not "post more"). If the month was flat or down, say so honestly and name the cause you can evidence — a dead format, a posting gap, a platform shift — not a vague "algorithm changes". The story decides which charts earn a slide; everything else stays in the appendix.
  3. Build the deck (input: 3-bullet story → output: 8–10 slide deck)
    Fixed structure, every month: ① Cover — client, month, one-line headline of the month ("Reach up 38%, driven by Reels") ② Scoreboard — 5–6 headline metrics with month-over-month change, big numbers, no chart junk ③ What grew — the single most important trend, one chart, one sentence ④ What worked — top 3 posts with thumbnails and the numbers that made them top ⑤ Platform breakdown — one row per platform, same metrics, so comparisons are honest ⑥ Audience — one slide: who engaged, any notable shift ⑦ Next month — 2–3 concrete actions with owners and dates ⑧ Appendix — the full numbers table for anyone who wants to audit. Ten slides max before the appendix; if it doesn't fit, it wasn't the story.
  4. Design in slate (input: deck structure → output: styled slides)
    The slate system: light slate-gray background (#f1f5f9 range), near-black slate text, white cards for numbers and charts, one accent color per platform (kept consistent month to month) plus one neutral accent for highlights. One chart per slide, one message per chart — title the chart with its conclusion ("Reels drove 61% of reach"), never with its metric name ("Reach by format"). Numbers at 48px+ on the scoreboard; body text never below 16px. Every slide carries the client name, month, and page number in the footer so a forwarded screenshot stays attributable.
  5. Review and send (input: styled deck → output: client-ready report)
    Check every number against the raw table — one wrong figure costs more trust than a late deck. Read the deck as the client would: does the cover headline match the scoreboard? Does "what worked" name real posts? Does "next month" contain actions someone could actually do? Export as PDF (fonts embedded, under 10MB) and send with a 3-line email summary: the headline, the one thing that worked, the one thing changing. Keep the editable source — next month is a refill, not a rebuild.

Anteprima del modello

Slate Social Report Deck — Template

One deck per client per month. Fill the numbers table first; the story comes from it; the slides follow.

Client: {name} · Month: {Month Year} · Prepared by: {name}

Raw numbers table (source of truth — every deck figure must match this)

Metric-definition changes this month: {none / platform X renamed Y — noted for comparability}

The story (write before designing)

What grew: {one line with the number} What worked: {1–3 posts/formats + why, with numbers} What changes: {one concrete next step}

Deck outline (8–10 slides + appendix)

  1. Cover — headline: "{Month} — {one-line result}"

Il pacchetto della skill (SKILL.md + modello) è scritto in inglese.

Pro — tutte le 511 skill

Potrebbe piacerti anche