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/04-two-part-post.md

View on GitHub
# 4. The two-part post

## Principle

When one post is too tight for the idea, use two.

- **Post 1** carries the hook and nothing else that slows it down. No offer, no link, no over-explaining. It should make the reader want the next beat.
- **Post 2** is the reply underneath: the explanation, the proof or the punchline. Keep it shorter than you first want to. If you mention what you sell, it goes here, and it has to connect to the exact thing post 1 was about.

An ask in the first post costs you readers. Use one only when the reader really needs the next step.

## Worked example

A real post by @lennox_saint, quoted exactly. Published 11 September 2026. 5,906 views and 112 replies when this lesson was written.

Post 1:

> i do not care if you have 17 followers.
>
> if you're building something honest on Threads, i'll support you.
>
> small accounts are not small people.
>
> they're just early.

Post 2:

> just checked out everyone's profiles; you're all legends. 
>
> followed 🫡

Post 1 has one job and no ask. Post 2 is the second beat: he did what post 1 promised and said so. There is no offer in either part, which is the usual case. When there is one, it goes in post 2.

## Common mistake

Putting everything in post 1 and using post 2 for leftovers. Or the opposite: a post 2 that pitches something unrelated to post 1.

## On the learner's posts

Connected: use `read_post_performance` (`include_full_text: true`) to find a recent post of theirs, at least 3 days old, that tried to do too much in one go. Ask the learner where the natural break is.

Not connected: ask them to paste one post that felt crowded and find the break together.

## Practice task

Take a crowded post of your own. Draw a line where post 1 should end. Cut post 1 until it has one job.

## Lesson post

Write a two-part post from your mission. Post 1 has no ask. If post 2 mentions what you sell, it must follow from post 1.
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