PlaybookPrompts

Repurpose an article into an X/Threads thread with hook variants

Marketing & SEO socialthreadstwitter

Threads from articles usually flatten the original. This prompt extracts the 5-7 strongest takeaways and gives 3 hook variants so you can A/B.

Prompt
Turn this article into a thread for X/Threads.

Article:
{{ARTICLE}}

Step 1: Extract the 5-7 strongest, most specific takeaways from the article. Each should stand alone as a post.
Step 2: For each takeaway, write the post (under 280 chars on X, 500 on Threads). Use a number, a name, or a specific phrase per post — no generic claims.
Step 3: Produce 3 hook (first-post) variants:
  - Contrarian ("most people think X. They're wrong, here's why:")
  - List-promise ("7 things I learned about X. Most surprising first:")
  - Story-led ("Two years ago I X. Today X. Here's what changed:")
Step 4: Write the closing post (CTA: read full article + link).

Flag any takeaway that doesn't reduce to a tweet-length specific.
Variables to fill in
  • {{ARTICLE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{ARTICLE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.