Official skill · Marketing
Social posts from an article
Turns one article into a LinkedIn post, an X thread, and a short post, each hooked on the article's most specific point. Use it when an article, guide, or report just went live and needs promotion.
AI skill
Have your AI turn one article into social posts
14 days free · No card needed
Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.
When to use it
- An article, guide, or report just went live and needs promotion
- Someone wants to post about the company's article in their own name
What you give it
- The article text or URL
- Who posts it (company or a person)
- Audience (optional)
What you get
A LinkedIn post, an X thread, a short post, and 2 alternative hooks to test.
How it works
- Find the 3 most specific points
- Write the hook from the top point
- LinkedIn post: 120 to 220 words (our default; LinkedIn allows up to 3,000 characters)
- X thread: 4 to 7 posts
- Short post: under 200 characters
- Tags and mentions
- Check every claim against the article
Example
What you give it
Article "What we learned from 400 support tickets" by Mira Okafor, head of support at Brightlane (invoicing app). Mira read all 400 tickets one by one. Key finding: 38% of tickets came from one settings page, invoice settings. The feature wasn't the problem, the words were: "Apply" saved for one invoice, "Save" saved for all of them, and most people guessed wrong. Renaming the 2 buttons to "Save for this invoice" and "Save for all invoices" cut tickets from that page by 60% the next month; nothing else on the page changed. The article also says most "bugs" were wording and the angriest tickets came after a silent failure, not an error message, and it ends with the tagging sheet the team used. Poster: Mira.
What you get back (the start of it)
Posts for: What we learned from 400 support tickets
Top point used as hook: Renaming 2 buttons cut tickets from one page by 60% the next month. Poster: Mira Okafor
We renamed 2 buttons and tickets from one page fell 60%.
I read all 400 of our support tickets, one by one.
38% came from a single page: invoice settings.
People weren't confused by the feature. They were confused by the words. "Apply" saved for one invoice. "Save" saved for all of them. Most people guessed wrong.
We changed the buttons to "Save for this invoice" and "Save for all invoices". Tickets from that page dropped 60% the next month. Nothing else on the page changed.
What else the 400 tickets showed:
- Most "bugs" were wording.
- The angriest tickets came after a silent failure, not an error message.
The full breakdown is in the article. It ends with the tagging sheet our team used: [link]
The rest of this output, the full steps and the checks the AI runs before it answers are in your pod once you add the skill.
Use this skill in your AIShare it with your team
Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team
Changelog
- v1.0.1 · · Example: the input now carries every fact the posts use (the invoice settings page, the Apply/Save labels, the other findings, the tagging sheet), the hook is under 12 words, and the LinkedIn post is within 120 to 220 words.
- v1.0.0 · · First release.
Sources
- Counting Characters (read 2026-11-04)
- Post and share updates | LinkedIn Help (read 2026-11-04)
- Inverted Pyramid: Writing for Comprehension (read 2026-11-04)