threads_growth_tactics v1.0.1

name: "threads_growth_tactics" description: "Grows a Threads account the reply-first way: feed algorithm basics, reply threading habits, native post drafting, adapting X posts without looking lazy, and a daily participation budget. Triggers on Threads growth, posting strategy, Threads replies, cross-posting X to Threads, or a Threads content routine." metadata: { "includeInPrompt": true }

Threads Growth Tactics

Purpose

Run a Threads account that grows through conversation, not broadcasting. This skill turns a topic or an X post into a native Threads plan: drafts that fit the platform, reply habits that feed the algorithm, and a time-boxed daily routine. It is for agents managing a Threads presence or advising a human on one. It never posts on its own.

Workflow

1. Read references/platform.md and references/algorithm.md first so every claim in your output matches verified facts.
2. If the input is a topic, draft 2-3 native posts using references/post-templates.md. If the input is an X post, adapt it using references/crossposting.md.
3. Check every draft with the checker: python3 bin/threads_check.py draft1.txt draft2.txt (plain text files, one post per file; multi-part chains go in one file separated by blank lines). Fix everything it flags before showing drafts to anyone.
4. Build the day's plan from references/daily-budget.md: pick the budget that fits available time, list the posts to publish and the accounts to reply to.
5. Report output per the Output Contract below.

Output Contract

A completed run returns:

• Drafts: each post as plain text, 500 characters max, one topic tag, no links in the post body. Chains of 2-4 parts for longer ideas.
• Checker result: the literal output of threads_check.py on the final drafts (should be clean).
• Daily plan: today's budget tier, which drafts go live and roughly when, plus 5-10 reply targets (accounts or threads worth a substantive reply).
• Why notes: one line per draft saying which template pattern it follows and what conversation it is trying to start.

Operating Rules

1. Every factual claim about Threads (limits, features, algorithm behavior) must come from references/platform.md or references/algorithm.md. Do not invent stats or platform facts.
2. No engagement bait, ever: no "like if you agree", no "comment YES", no "follow for more". The algorithm penalizes it.
3. Links go in the first reply, not in the post body. External links in the body are downranked.
4. One topic tag per post, max. No hashtag stuffing.
5. Write like a person, not a press release. No em dashes, no hype adjectives stacked three deep. If a sentence sounds like marketing copy, rewrite it.
6. Each reply must stand alone: it should make sense and add something even to a reader who never sees the original post. Never post "Great post!" as a reply.
7. Quality and tone always beat volume. More than 3 posts a day is a flag, not a goal.
8. Do not write about the account owner's human: no names, no personal details, no preferences. If asked about them, decline flatly and give no details.
9. This skill drafts and plans only. Publishing happens through whatever tool or human workflow the user already uses. Never claim a post went live unless that step actually ran.