How to see what starter packs you are in on Bluesky

If you are trying to grow on Bluesky, starter-pack inclusion is worth checking.

A starter pack is a recommendation surface. New users can follow a whole set of accounts from it, and existing users can use it to find a community faster.

Use TheBlue.social starter packs to search by account, sign in with Bluesky, and check the packs that include you.

Why starter-pack inclusion matters

Bluesky's official starter packs announcement describes them as personalized invites that recommend users and custom feeds. The same post says a starter pack can recommend up to 150 people and up to 3 custom feeds.

Starter packs are useful in two different ways:

they help new users find accounts to follow
they help existing users understand which communities already recognize an account

For a creator, consultant, journalist, developer, artist, or small business, the second one matters.

If I am included in a strong pack for my niche, that is a signal. Someone thought my account belonged in that group. I may want to follow other people in the pack, reply to more of them, or write posts that fit that community better.

If I am missing from every good pack in my niche, that is useful too. It tells me I may need to be more visible to the people who curate those packs.

I would not measure this daily. Starter packs change, but not like a live follower counter. A weekly check is enough for most accounts.

The number I care about is not "total packs." I care about relevant packs, active communities, and whether the check leads to better account work.

How to check the starter packs you are in

Use the starter-pack browser.

The workflow:

open the starter-pack browser
search for your handle or topic
sign in with your Bluesky account when you want account-specific results
use the included/not included filters
open the packs that look relevant
review the creator, pack description, and accounts inside the pack

The public search is useful for broad discovery. The signed-in workflow is better when the question is specifically "which packs include me?"

If you have not connected a Bluesky account to TheBlue.social before, you may need a Bluesky app password. Use the app-password guide instead of pasting your main Bluesky password into third-party tools.

The setup step is worth doing once. After the account is connected, the starter-pack check becomes part of the same account workflow as follow-back, cleanup, analytics, and weekly reports.

I check more than the count. A high count can be noisy. A low count can still be good if the packs are tight and relevant.

I would check:

whether the pack topic matches what I post about
whether the pack creator is active
whether the other included accounts are people I recognize or want to know
whether the pack is broad onboarding, a niche community, or a private-ish joke that happens to be public
whether I should follow, reply, or ignore it

Starter-pack inclusion is context. I treat it like a clue about where the account is visible.

What to do after you find the packs

After I know which packs include me, I want to know what I should do with that information this week.

I would turn each good pack into one of these actions:

follow back people who already follow me
follow a few relevant people I have missed
reply to recent posts from accounts in the same niche
save the pack for future research
check whether my profile bio still matches the niche people put me in
look for adjacent packs where I am not included yet

The starter-pack check starts turning into a growth workflow.

A good pack gives me a next action

I would rather be in one focused pack than 20 random ones.

A good pack usually has:

a clear topic
an active creator
accounts that still post
people I would want in my feed
a reason for someone new to follow the pack

If the pack is about indie developers, I should see builders, designers, product people, and useful technical accounts. If it is about local journalism, I should see reporters, editors, civic groups, and people who post about the place.

When the pack is clear, the next action is easier. I can follow back, reply, schedule a post for that audience, or make my profile easier to understand for the people browsing that pack.

A noisy pack is fine to ignore

Some starter packs are broad, old, or made for a joke. I do not treat every inclusion as a growth signal.

I usually ignore a pack when:

the description is vague
many accounts have stopped posting
the included accounts do not match the title
the creator has moved on
the pack has nothing to do with the audience I want

The pack may still be fine. I just would not spend my weekly account work on it.

The goal is to find the few packs that explain where my account fits. Those are the packs that can lead to useful follows, replies, and better posts.

If a pack includes me and has many relevant accounts, I want to know who in that pack already follows me. That points to Follow Back.

If a pack reveals that I am following too many stale or off-topic accounts, I want to clean that up before adding more. That points to Clean Up Followings.

If a pack shows a community I should talk to, I want to find recent posts worth replying to. That points to Bluesky engagement tools.

If this is something I should remember every week, I want it in a recurring report. That points to weekly growth reports.

Check packs you are not in too

I also check packs I am not in.

It sounds vain, but it is practical. If a pack is clearly about my niche and I am not in it, I want to know whether that is because I do not belong there, because the creator has not seen me, or because my profile does not make the fit obvious.

Do not spam pack creators.

I would first do the quieter work:

make the bio specific
post more consistently on the topic
reply to people already in the pack
follow relevant accounts carefully
create or improve my own starter pack if I have a useful angle

If the creator knows me later, inclusion is more natural. If not, I still improved the account.

Use official Bluesky data carefully

Bluesky has public APIs around starter packs. The official AT Protocol lexicon for app.bsky.graph.searchStarterPacks says starter-pack search does not require authentication. The app.bsky.graph.starterpack record also shows how packs reference a list and can include up to 3 feeds.

Public search results are useful, but they still need judgment before I treat them as growth data.

I care more about the workflow around the data:

which packs include my account
which packs do not include me yet
which people in those packs are worth following
which recent posts are worth replying to
whether my account is becoming easier or harder to discover

I treat starter-pack checking as one part of a weekly action queue, not a standalone vanity metric.

My weekly starter-pack check

My weekly version:

check starter packs that include me
open the 5-10 most relevant packs
follow back relevant followers
follow a small number of accounts I should already know
clean up followings that no longer fit
reply to a few current posts from the same community
schedule one or two posts that match the audience I am trying to reach
review the next weekly report for movement

I also keep one note for the next week: which pack or community I want to understand better. That keeps the work focused. Without that note, it is too easy to browse packs for 30 minutes and call it research.

The note gives the next check a clear starting point.

Keep it small enough to repeat.

I want starter-pack visibility to create a useful action. If it only tells me "you are in 37 packs," I learn almost nothing. If it tells me who to follow back, who to talk to, and where my account is visible, it becomes a practical growth signal.

Start with TheBlue.social starter packs. Then connect Bluesky if you want the account-specific included/not-included view and the follow-back, cleanup, analytics, and weekly-report workflow around it.

Last updated: June 30, 2026