PrompTom
For Threads

Profile topics

FREE

The topics on your profile decide which strangers get shown your posts.

Works best in ChatGPT / Claudeprofiletopicsreach

The prompt

You do social strategy. Pick profile topics for Threads.

What you write about: {topics over the last month}
Who you write for: {audience}
What you sell or do: {if anything}
What the profile says now: {as it is}

Deliver:
1. Three to five topics you should be found under. Not what interests you, but what strangers will look for you under.
2. How each topic overlaps with what you actually post. A topic with no posts works against you: arrivals leave.
3. What to remove: the too broad ("marketing") and the too narrow that nobody searches.
4. How this fits the first line of the bio. Topic and bio must agree, or the profile reads as somebody else's.
5. Three opening posts per topic, so an arrival sees this place is about that.
6. When to check and what to look at: the share of non-followers in your reach.

Topics are not hashtags. They are a claim about which feed you belong in, and the claim is backed by posts, not words.

Anything in curly braces is yours to replace.

Example output

Topics: prompts for work, marketplaces, seller tools. Remove "AI" — too broad, you are two hundredth there. Bio first line: "I break down prompts that save sellers time." Matches the topics. Check in 3 weeks: share of impressions from non-followers. Was 40%, should rise.

Related prompts

The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.

ChatGPT / Claudehooksthreadsreach
Write 20 opening lines for Threads posts on the topic "{topic}".

Audience: {who}
My role: {who you are to them — practitioner, seller, observer}

Hard limits:
— No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land.
— No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past.
— No caps lock, no emoji chains.

Give 4 groups of 5:
1. Personal experience with a specific number or timeframe.
2. Disagreement with received wisdom in the niche.
3. An observation the reader recognises in themselves.
4. An open question they have something to answer from their own experience.

After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Show sample result

Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)

Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.

ChatGPT / Claudethreadsengagementrecommendations
Write a Threads post on the topic "{topic}" designed to pull replies.

What I know about it: {your experience, facts, numbers}
Audience: {who}
What I want to hear in the replies: {e.g. how other people solve this}

Rules:
— No longer than 500 characters, that is the platform limit. 300 is better.
— The first 90 characters must work as a standalone hook; the rest is what people unfold themselves.
— End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice.
— Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say.

Don't do this:
— "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to.
— Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow.

Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Show sample result

Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.

The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.

ChatGPT / Claudethreadsalgorithmfirst hour

This prompt is part of the PRO collection

Unlock access