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/02-openers.md

View on GitHub
# 2. Openers

## Principle

A good first line makes the reader feel the post is already about them. The most reliable way to do that is to name what is happening, before you say how to fix it.

Three moves:

1. Name the thing people do or feel and do not say out loud.
2. Add one specific detail that makes it real.
3. Leave something unresolved, so the next line is needed.

Four kinds of opener to start with:

- **Receipt** - something true that happened to you. "i did this, here is what happened."
- **Mirror** - a specific person doing a specific private thing, so the right reader recognises themselves.
- **Correction** - common advice, and the part of it that is wrong or incomplete. It has to be useful, not just spicy.
- **Confession** - something you got wrong. It lowers the guard before the point lands.

## Worked example

A real post by @lennox_saint, quoted exactly. Published 26 January 2026. 716,983 views when this lesson was written. This is the first post of a longer thread.

> i handed in my resignation.
>
> my managers called me into a meeting.
>
> i didn't know it then, but that meeting would ruin 5 months of my life.

It is a receipt: something that happened to him. It names a moment you can picture, adds one specific detail (5 months), and leaves the question open - what happened in that meeting? It does not explain or teach anything yet.

Compare it with an opener like `how to deal with a difficult employer`. Same subject, no reason to keep reading.

## Common mistake

Clearing your throat. The real opener is often the second or third sentence, sitting under a warm-up line like "i've been thinking a lot about this lately".

## Fixing a weak opener

- Delete the first sentence and see if the post is better.
- Swap a big abstract word for something a person visibly does.
- Swap advice for an observation.
- If the opener claims proof, make sure the proof is real, or drop the claim.
- Keep the offer and the link out of the first line.
- Read it out loud. If it sounds like a work memo, start again.

## On the learner's posts

Connected: pull their best posts with `greatest_hits` (`metric: "views"`) and their recent ones with `read_post_performance` (`include_full_text: true`). Follow the post-picking rules in the skill: best posts by views with the age and view floors, full text for recent posts, and the contrast-post rule. Put the first lines side by side and ask which kind each one is, and which kind their strongest posts lean on.

Not connected: same exercise on pasted posts, called a sample.

## Practice task

Take one idea from your mission and write four first lines for it, one of each kind. Pick the one you would actually say.

## Lesson post

Write a short post under the opener you picked. Use hook, hold, help from lesson 1.

## Edge of the free material

This lesson teaches four kinds of opener and how to fix a weak one. It does not include ready-made hook lists. Use the one-line pointer if the learner asks for more.
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