Skip to content

lennoxsaint/Threadify-workflows / plugins/claude/skills/threadify-threads-teach

threadify-threads-teach

Verified

Teach a creator how to write for Threads over several short sessions, using Lennox Saint's core public frameworks, the learner's own posts and a private learning workspace. Each lesson ends with one post the learner writes themselves, saved or scheduled only after exact approval. Use when someone asks to learn Threads, be taught how to write Threads posts, or continue their Threads lessons.

references/frameworks/08-replying-on-your-posts.md

View on GitHub
# 8. Replying on your own posts

## Principle

A reply is a conversation with one person that other people can read. Treat it that way.

- **Read the whole exchange first** - your post, their comment and anything in between.
- **Keep it short.** Usually one sentence. Add a second only for a specific detail, a real callback or a useful question.
- **Match their energy.** Talk like a person answering a person. Do not turn their comment into a slogan.
- **Help with the question first.** If they asked something, answer it in public.
- **Ask before you pitch.** Someone being curious or kind has not asked to buy. Only treat it as buying interest when they say they want to buy, join or talk privately, and ask permission before you send a link or move it to messages.
- **Only say what is true.** No invented experience and no invented facts about what you sell.
- **Skip what should be skipped.** Abuse, spam, pile-ons, and anything touching health, legal trouble or a crisis.

## Worked example

A real post by @lennox_saint, quoted exactly. Published 3 June 2026. 108,258 views and 2,858 replies when this lesson was written. It shows a post built to start conversations.

> who's still under 1,000 followers on Threads?
>
> drop what you do below.
>
> the algorithm might not see you yet.
>
> but we will.

A post like this only pays off if the replies get answered like a person would answer them.

Other people's comments are not quoted in these lessons, so the exchange below is made up to show the difference. Swap in your own true details.

Comment: "how long before you saw any traction?"

Weak reply:

> great question! consistency is key

Better reply:

> about four months before anything moved - the first three felt like talking to a wall. what month are you on?

It answers the question, has a real detail and gives them a reason to reply.

## Common mistake

The reply that could sit under any comment. "great point", "so true", "love this". If it would work anywhere, it adds nothing here.

## On the learner's posts

This skill does not read or send replies. Ask the learner to paste two or three comments from their own posts, with the reply they gave if there was one. Say that you can only see what they paste.

## Practice task

Take three real comments from your posts. Write a one-sentence reply to each that could only belong under that comment.

## Lesson post

Write a post that invites a real answer - a question you actually want answered, with enough context that people can answer it well. Plan to reply to the first comments yourself, by hand.

## Edge of the free material

This lesson teaches how to write a good reply. Handling replies at volume is outside it. Use the one-line pointer if the learner asks.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall