/report-to-post

---
name: report-to-post
description: >-
  Turn a long report, study, survey or white paper (WEF, OECD, a central
  bank, McKinsey, an academic paper, your own company's research) into a
  LinkedIn post or short carousel that a busy professional reads to the
  end: one striking finding up top, three supporting points, what it means
  for the reader's work, one action, and a clear credit line with the
  source and page. Use this skill whenever the user uploads or links a
  report and says "make a post from this", "LinkedIn post about this
  study", "carousel from this PDF", "summarise for my audience", or wants
  to share research without copying it. Do NOT use to repost someone
  else's content as your own, to quote more than a few words verbatim, or
  to claim findings the report does not make.
---

# Report to post

Every week a hundred-page report lands with one finding that would change
how your readers work, buried on page 47. Most people who share it post
the cover and the executive summary's first line, which everyone else also
posted. The value is in finding the one number that matters for YOUR
readers, checking it is really in the report, and explaining it in their
language.

This skill reads the report like an analyst and writes like a teacher:
one finding, the evidence, what it means on Monday morning, and full
credit to the people who did the work.

## Workflow

### 1. Know the reader

Ask once (or use what you know): who follows the user, and what do they
do all day? A finding about "AI adoption in firms" lands differently for
CFOs, for recruiters and for students.

### 2. Read for the finding, not the summary

- Read the executive summary, then the charts and tables, then the methods.
- List 5 candidate findings with page numbers.
- Pick the one that is surprising, specific and useful for THIS reader.
  A finding that contradicts a common belief usually wins.
- Check the scope: who was surveyed, where, when, how many. Write it down;
  it goes in the post.

### 3. Write the post

```
[Hook: the finding as a fact, with its number. Max 3 short lines.]

[Context: who found it and how, in one sentence. "The OECD surveyed
5,300 firms in 9 countries."]

[Three points, numbered, each one line with a number or example.]

[What it means for you: one or two sentences in the reader's job terms.]

[One action the reader can take this week.]

Source: [Report title], [organisation], [year], p. [X].
```

For a carousel: one finding per slide, the source on every slide, the
action on the last one.

### 4. Check before handing over

- Every number appears in the report on the page cited. Re-open it and look.
- Nothing says "proves" where the report says "suggests" or "is associated".
- Quotes, if any, are under 15 words and in quotation marks with credit.
- The post makes sense to someone who never opens the report.

## Rules

**The report is the hero, you are the guide.** Credit the organisation by
name in the text, not only in a link.

**One finding, done well.** A post that summarises everything teaches
nothing. Save the other findings for other posts.

**Translate, do not copy.** Paraphrase in your own words. Long verbatim
passages are the authors' work, not yours.

**Scope is part of the fact.** "Firms in 9 OECD countries" is not "all
companies". Keep the qualifier, even when it makes the line longer.

## Example

A 90-page central-bank report on household finances. The usual post shares
the headline inflation figure. This skill instead finds a table on page 34:
households under 35 hold a smaller share of savings in cash than five years
ago, and more in investment funds. For an audience of young professionals,
the post leads with that change, explains the method in one line, gives
three related numbers from the same table, and ends with an action: "Check
what share of your savings has been sitting in cash for over a year."
Source line with the page. (Figures in a real post come only from the
report itself.)