/threads-post-writer

name: threads-post-writer
description: "Draft a single Threads post or a multi-post thread using a 2026 Threads hook formula (warm contrarian, data-point, build-in-public, quote-post, mini-list, relatable, listicle, story, curiosity-gap, how-I teardown), picked by goal (replies, reposts, likes, quotes). Respects the 500-char limit and one-hashtag cap, runs the humanizer pass, and publishes via Publora, which auto-splits long content into a thread. Not for auditing a draft (use threads-humanizer) or hook teardown (use threads-hook-extractor)."

Threads Post Writer

Ship a single Threads post, or a multi-post thread, using hook shapes that travel on Threads in 2026. Single-post formulas land a complete punch in the first line, because the feed truncates long posts with a "more" cut. Threads posts run warmer and more conversational than X.

When to use

• User says "write me a Threads post about X"
• User has a topic or a rough one-liner and wants a sharper hook
• User wants to turn notes into a multi-post thread
• User wants a quick draft that auto-publishes on approval

Formulas this skill uses

Single-post shapes (T1-T6):

| Code | Formula | Primary goal | Best for | |---|---|---|---| | T1 | Warm Contrarian | reposts | a sharp, defensible take framed as an invite | | T2 | Data-Point Hook | reposts | one odd-precision number that reframes a thing | | T3 | Build-in-Public Confession | replies | a real metric from your own work, ugly ones included | | T4 | Quote-Post Add-Value | quotes | adding a layer to someone else's take (quote post) | | T5 | Mini-List Post | reposts | a scannable list that fits in one post | | T6 | Relatable Cold-Open | likes | a specific shared moment, no setup | | T11 | First-Person Status Flex | replies | a flat status or milestone, then a counterintuitive pivot | | T12 | Permission Reframe | quotes | "Most {group} DON'T NEED {thing}, they need {permission}" | | T13 | Copy-Swap Micro-Lesson | reposts | one before/after swap: weak version, then strong version |

Thread shapes (T7-T10):

| Code | Formula | Primary goal | Best for | |---|---|---|---| | T7 | Listicle-Thread Promise | reposts | numbered teaching thread, one item per post | | T8 | Story Thread | likes, quotes | a real narrative with a build and a turn | | T9 | Curiosity-Gap Opener | replies | a surprising result, mechanism withheld | | T10 | How-I Teardown | reposts | a repeatable process you ran yourself |

Full skeletons in `../../references/hook-formulas.md`. T11-T13 were added from a 318-post corpus pull (July 2026): the status flex, permission reframe, and copy swap topped the aspirational-warm Threads feed. They are strong hypotheses to test, anchored on small-account examples, not yet follower-normalized.

Pick by goal first

| Goal | Reach for | |---|---| | Replies | T3, T9, T1, T11 | | Reposts | T2, T5, T7, T10, T13 | | Likes | T6, T8 | | Quotes | T4, T8, T12 |

Pick the container first

| If the idea is... | Container | Formulas | |---|---|---| | One claim, one number, one moment | single post | T1, T2, T3, T6, T11, T12 | | A scannable list, one line per item | single post | T5 | | One before/after copy swap | single post | T13 | | A list where each item needs teaching | thread | T7 | | A narrative with a build and a turn | thread | T8 | | A surprising result with a mechanism | thread | T9 | | A repeatable process you ran yourself | thread | T10 |

A thread on a one-line idea reads as padding. A single post trying to teach five things should be a thread.

How Publora splits a thread

Pass the full thread as one `content` string. Publora auto-splits it:

• at paragraph breaks (`\n\n`) first,
• then at sentence endings,
• then at word boundaries as a fallback.

Unlike X, Threads does NOT add `(1/N)` markers by default. For full control of where each post breaks, hand-split with a `---` separator on its own line between posts. The skill defaults to hand-splitting with `---` so the user sees exactly how the thread will land before approving.

> If multi-post nesting is temporarily paused (Meta app reconnection), fall back > to posting the opener as a single post and adding the rest as replies by hand. > See `../../references/algorithm-heuristics.md`.

Steps

**Voice profile first (all drafts).** If `../../references/voice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA/link style throughout. If it is not filled, mention once that `threads-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules.

1. **Gather inputs.** Topic, angle, any rough draft, target audience (builders / founders / a niche), and the goal (replies / reposts / likes / quotes). 2. **Pick the container.** Use the container table. One claim or moment is a single post; a list that needs teaching or a story with a build is a thread. 3. **Pick the formula.** Use the goal table to shortlist, then suggest 2-3 that also fit the topic and let the user choose. 4. **Draft.** Fill the skeleton in the user's voice. Respect the 2026 Threads rules:

• First line carries the whole load (the feed truncates with "more").
• Under 500 chars per post (10,000 only if a text attachment is in play).
• One idea per post. Line breaks as beats.
• 0-1 hashtag at the end (Threads allows only one), 0-2 emoji, none on a

serious take.

• No external link in post 1 (offer to put it in a reply).
• Warm and conversational, not a transplanted X dunk.

5. **For a thread:** write post 1 first (the promise + open loop), front-load the strongest beat at position 1-2, target 4-7 posts for teaching/list threads, make each post stand alone, and close on the most quotable line plus one ask. 6. **Humanizer pass.** Scrub 2026 AI vocab by density, cap em dashes (at most one per post, never swap one for a period), break stacked triads, generic openers and reveal bridges. Leave the rhythm alone: uniform rhy