social-media-skills/skills

threads-post

Write and publish single posts on Meta's Threads — the Threads format-execution skill.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/social-media-skills/skills --skill threads-post

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

threads-post

A format-execution skill — write a Threads-native conversation post (built to earn replies) and carry the WoopSocial Threads publish facts. The agent writes the post + topic tag + media direction + reply angles; WoopSocial publishes/schedules the single post; the replying that drives reach is human.

The POV: conversation-first — reply more than you post

Threads rewards what most platforms only claim to: genuine conversation. Replies outweigh likes, conversation depth and velocity (first 30–90 min) drive distribution, and the For You feed surfaces new/smaller accounts — an open (but tightening, post-ads) window. Mosseri's rule is blunt: "reply much more than you post." So write a conversation starter (question / hot take / opinion), keep a consistent niche with one topic tag (topic-neighbourhoods), put links inline (the old penalty was reversed), and treat the post as the smaller half — the replies win the reach, and that part is human.

Read these first

  1. brand-profile — niche + voice (Threads punishes press-release tone).
  2. goals-and-kpis — the goal (replies / profile visits / follower growth, not vanity likes).

The framework: REPLY

(Depth: references/the-reply-framework.md.)

  • R — Reason to reply: a conversation starter (question/hot take/opinion), not a broadcast; no bait.
  • E — Engagement velocity first: the first 30–90 min decide reach — post at a peak window, reply fast.
  • P — Personality + niche: authentic/original (not promo); consistent niche + one topic tag.
  • L — Light media + link if it fits: photos out-engage text-only (~+60%); links inline (no

first-comment tax); stay ≤500 chars.

  • Y — You reply more than you post: the post is the smaller half; **WoopSocial publishes it, a human

(→ community-management) does the replying.**

The reality (verify-quarterly)

Platform stats (text-first, ~400M MAU, passed X in daily mobile, ~6.25% ER, ads global Jan 2026 → tightening); conversation-first + Mosseri "reply more than you post"; ranking (replies>likes, depth, velocity 30–90 min, For You surfaces new accounts); Mosseri specifics (links rewarded, bait crackdown, credibility/originality, Account Status, Dear Algo); topic tags + niche-neighbourhoods; formats (500 chars, photos +60%, video 5min, polls/voice/GIF native-only); avoid-list: references/threads-2026-reality.md. Post types, anatomy, the WoopSocial Threads publish block + worked examples: references/post-recipes-and-publish.md.

Honest scope (never violate)

  • WoopSocial publishes ONE Threads post (content.text ≤500 + optional media). **No postType, no

link field (links inline), no polls/voice/GIF (native-only), no multi-post chain (single content item). No reply surface → the replying that drives reach is human** (community-management).

  • No update endpoint → edit = delete + recreate (only while NOT_STARTED).
  • No engagement bait (penalized + dishonest); no press-release tone (suppressed). **Never promise a

reach multiple; never fabricate metrics** (native analytics only). (Scope, distinctions + connections: references/scope-and-connections.md.)

Distinct from its siblings (route correctly)

threads-post (this) = the Threads-native conversation post + the WoopSocial Threads publish facts · thread-writer = the multi-post chain ("write a thread" means that; this is ONE post — WoopSocial can't chain) · x-growth = the sibling text platform, different culture (X real-time/credit-metered, links-in-reply; Threads conversation/reply-driven, links-inline) · caption-writer/hook-writer = the post line · community-management = the replies that win reach.

Where this connects

Reads first: brand-profile, goals-and-kpis. Copy: hook-writer, caption-writer. Media (external to WoopSocial): image-prompt/ideogram/nano-banana, the video cluster. Publish: scheduling-and-queue → WoopSocial (single Threads post to a velocity window), platform-specs-and-validation (validate + field rules), content-calendar (cadence). Engage/measure: community-management (the reply work), analytics-and-reporting (replies/reach/profile-visits), experimentation-and-ab-testing (A/B hooks/times). Replies + polls/voice stay native.

Definition of done

A conversation-starting post (question/hot take/opinion) in the brand's voice, ≤500 chars, with one genuine reply prompt (not bait), one niche topic tag, optional supporting media and an inline link if useful; scheduled to a velocity window with a reply plan for the first 30–90 min; published by WoopSocial as a single Threads post (no chain/poll/voice/GIF), validated first, edits via delete+recreate; the reply work handed to a human/community-management, nothing fabricated and no promised reach multiple; correctly distinguished from x-growth and caption-writer.

Related by task

from this repository

More skills

All skills
social-media-skills
Community

hook-writer

Use to write the hook — the opening that earns attention — for any social content: a caption's first line, a video's first three seconds, a carousel cover slide, a thread opener, a YouTube title, or an email subject. Run when the user says "write a hook," "hook for this," "opening line," "first three seconds," "cover slide," "make this scroll-stopping," or when good content keeps getting ignored. Reads brand-profile and voice first so hooks sound like the brand, not viral-bait templates. Hooks m

1h installs
3
GitHub stars
362
Updated
Oct 15
social-media-skills
Community

brand-profile

Use FIRST, before any other social media skill, to load or create the brand profile — the durable record of who a business is, who it serves, how it sounds, and what it will and won't say. Run this when the user says "set up my brand," "brand profile," "brand guidelines," "define our brand voice," "onboard," "get started," when work begins for a new business or client, or any time another social skill needs brand context that isn't already loaded. Works for ANY business: B2B SaaS, ecommerce, loc

1h installs
2
GitHub stars
362
Updated
Oct 15
social-media-skills
Community

caption-writer

Use to write platform-native social media captions (post copy) in the brand's voice — the words that accompany a post on Instagram, LinkedIn, TikTok, Facebook, X/Twitter, Threads, Pinterest, YouTube, or Bluesky. Run when the user says "write a caption," "caption this," "post copy," "write the copy for this photo/video/Reel," "IG caption," "what should I write for this post," or needs the words to go with a visual. Reads brand-profile and voice first so captions sound like the brand, not generic

1h installs
2
GitHub stars
362
Updated
Oct 15
social-media-skills
Community

carousel-writer

Use to write a carousel — a swipeable multi-slide post (Instagram carousel, LinkedIn document/PDF carousel, or TikTok photo carousel) — one of the highest-save, highest-dwell formats. Run when the user says "write a carousel," "carousel post," "slides for X," "LinkedIn document/PDF post," "swipe post," "turn this into a carousel," or wants multi-slide teaching or story content. Reads brand-profile and voice first; the cover slide hooks and promises the swipe (via hook-writer); each slide advance

1h installs
2
GitHub stars
362
Updated
Oct 15