Threads Post

Organization

social-media-skills

threads-post

Write and publish single posts on Meta's Threads — the Threads format-execution skill. Use when someone wants a "Threads post," to "post to Threads," grow on Meta's Threads, or publish a Threads post via WoopSocial. Writes a Threads-native conversation post (text <=500 + optional media) built to earn replies — Threads is conversation-first: replies outweigh likes and engagement velocity drives distribution. Uses the REPLY framework. Reads brand-profile + goals-and-kpis first. WoopSocial publishes ONE Threads post (no native multi-post chain, no polls/voice/GIF, no reply surface); the replying that drives reach is a human/community-management job; metrics never fabricated; no engagement bait. Distinct from thread-writer (a user saying "write a thread" wants that multi-post X chain, not this), x-growth (sibling text platform, different culture) and caption-writer (text only).

Overview

Publisher	social-media-skills
Repository	`skills`
Skill name	`threads-post`
Stars	215
Forks	44
Bundled files	5
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
5 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by social-media-skills on GitHub. Read the source before you install it.

Installation

Install the Threads Post AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/social-media-skills/skills/tree/main/skills/threads-post
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/social-media-skills/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/threads-post .claude/skills/threads-post

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Threads Post in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Threads Post on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Threads Post is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

brand-profile — niche + voice (Threads punishes press-release tone).
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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Threads Post AI skill do?

Why use Threads Post on TypingMind?

Because you install it once and use it with any model. Threads Post is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Threads Post in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/social-media-skills/skills/tree/main/skills/threads-post. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Threads Post?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Threads Post?

As many as you like. As long as a model supports skills, you can use Threads Post with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Threads Post AI skill free?

Yes. It is published on GitHub by social-media-skills under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Caveman Stats

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

threads-post

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

Read these first

The framework: REPLY

The reality (verify-quarterly)

Honest scope (never violate)

Distinct from its siblings (route correctly)

Where this connects

Definition of done

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now