Article to social posts

Turns one article into a LinkedIn post, an X thread and a newsletter blurb.

Marketing · produces a Social · built in, ready to run

What you give it

Something like this:

Article: "Why your order desk is your real bottleneck"

Distributors obsess over delivery time while orders sit in WhatsApp for hours. We measured 14 mid-size distributors: median 4.2 hours between a store sending an order and it existing in any system. Delivery itself took 19 hours. So 18% of total order-to-door time is a person reading a phone. The fix is not faster trucks. Three of the 14 moved ordering to a portal; their median dropped to 11 minutes, and their order-entry error rate fell from 6% to under 1%. The lesson: measure the part of the process nobody owns.

What you get back

This is a real run of the skill on the input above, not a mock-up:

Here are your three pieces:

---

## **LinkedIn Post**
We've been optimizing the wrong part of the supply chain. Our study of 14 mid-size distributors revealed the median order sits in WhatsApp for 4.2 hours before entering any system—while delivery itself takes 19 hours. That's 18% of total order-to-door time lost to manual entry. When three distributors moved to an ordering portal, their median time dropped to 11 minutes and error rates fell from 6% to under 1%. The bottleneck isn't speed—it's visibility. What process in your business is nobody explicitly responsible for measuring?

---

## **X/Twitter Thread**

1. Distributors obsess over delivery times. But here's what we found measuring 14 mid-size companies: orders sit in WhatsApp for a median 4.2 hours before reaching any system. Delivery takes 19 hours. 18% of total time = someone reading a phone.

2. The instinct is to fix logistics. Faster trucks, better routing, optimized warehouses. But our data said otherwise: the real bottleneck was sitting at the order desk the whole time.

3. Three of those 14 distributors moved from WhatsApp to an ordering portal. What changed? Median entry time: 4.2 hours → 11 minutes. Error rate: 6% → under 1%.

4. Not a technology story. Not a delivery story. A visibility story. The part of your process nobody explicitly owns is probably costing you more than you think.

5. Lesson: measure the unsexy middle. Fastest trucks in the world won't help if orders take hours to enter the system.

---

## **Newsletter Blurb**
We measured 14 mid-size distributors and found their real bottleneck: orders languishing in WhatsApp for a median 4.2 hours, consuming 18% of total order-to-door time. Delivery, by contrast, took 19 hours. When three distributors switched to an ordering portal, entry time dropped to 11 minutes and errors fell from 6% to under 1%—proving the fix isn't faster trucks. The hidden cost always lives in the part of the process nobody owns.

---

All three are ready to use and match the article's direct, data-driven tone without padding.

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

From the article below, write three things:

1. A LinkedIn post — 5 to 7 lines, one idea, ends with a question
2. An X/Twitter thread — 5 tweets, each under 280 characters, numbered
3. A newsletter blurb — 3 sentences

Match the tone of the original. Do not invent claims the article does not make. If the article is thin on a point, leave it out rather than padding it.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.