---
name: share-on-bluesky
description: Use when asked to write a Bluesky post (≤300 characters) announcing a personal project to busy professionals — generating interest, asking for help/advice, and inviting shares in a humble, personal voice — as distinct from [[share-on-facebook]], [[share-on-instagram]], [[share-on-linkedin]], [[share-on-mastodon]], and [[share-on-threads]] (same announcement, different platform conventions), or [[press-release]] and [[copywriting]] (formal/persuasive registers this deliberately avoids).
---

# Share on Bluesky

Bluesky's feed is close to reverse-chronological by default, and its
custom feeds (topic-based, user-built algorithms people opt into) are
the main way a post reaches anyone outside your existing followers.
The audience skews early-adopter, technical, academic, and
journalist-heavy, and it's a crowd that reads corporate-toned
self-promotion as a bad sign — a plain, first-person, slightly
unpolished post outperforms a marketing-voiced one.

## What works on Bluesky

- **Links aren't penalized.** Unlike platforms that historically
  throttled posts with outbound links, Bluesky renders a link preview
  card and doesn't visibly suppress reach for including one — so the
  link can sit directly in the post instead of "in bio" or "in
  comments."
- **Reposts and quote-posts are the real distribution mechanism.** A
  plain like barely moves a post beyond followers; a quote-post (or a
  repost into a well-followed custom feed) is what gets a post in
  front of a new audience.
- **Custom feeds are targeted discovery.** A post that fits a specific
  topic feed (e.g. a software or science feed) can reach people who
  never followed the author, but only if the post is legible out of
  context — assume the reader has no prior thread to lean on.
- **Replies build real conversation.** Because the timeline isn't
  optimized around maximizing time-on-app the way some larger
  platforms are, genuine back-and-forth in replies is common and
  welcomed, not just performative.
- **Alt text is expected.** The community is accessibility-conscious;
  an image post with no alt text reads as an oversight to a
  meaningfully sized part of the audience.
- **Hashtags do little.** They exist but carry far less discovery
  weight than on Instagram or Mastodon — don't spend characters on
  them.

## Hashtags

Bluesky has no meaningful hashtag-driven discovery layer comparable to
Mastodon or Instagram — search and custom feeds do the real work of
surfacing a post to strangers, not tags. Skip hashtags by default.
If a post genuinely fits an active community tag (e.g. one a specific
custom feed is built to surface), one or two placed inline — not
appended in a block at the end — can help, but treat that as an
exception, not a habit, and never spend scarce characters on tags
"just in case."

## Structure for a 300-character post

With 300 characters total, there's no real "above the fold" cutoff the
way longer platforms have — but the first line is still what decides
whether someone stops scrolling, since it's what shows in
notifications and quote-post previews. Spend it on the actual news,
not a run-up to it.

1. **First ~140 characters — the news itself, plainly stated.** What
   the project is and why it might matter to this reader, not a teaser
   for what's coming next in the post.
2. **One honest, personal line.** Why it exists, what it took, or what
   you're unsure about — the thing that makes it a person talking
   instead of a brand.
3. **One specific ask.** Feedback on a particular part, a use case you
   haven't thought of, or a straightforward "reply if you try it" —
   not a vague "thoughts welcome."
4. **The link.** Bare is fine; the preview card carries the visual
   weight.

## Key components

- **Humble framing over hype** — "I've been building this and I'm not
  sure I got X right" invites engagement in a way "Excited to
  announce..." doesn't on this platform.
- **A concrete ask, not a general one** — "does this hold up for your
  use case?" gets replies; "let me know what you think!" mostly
  doesn't.
- **An explicit, low-friction invitation to share** — "if this is
  useful to someone you know, a repost genuinely helps" reads as
  honest here, not as a growth-hack line, because it's said plainly.
- **Self-contained meaning** — since custom feeds can surface the post
  with zero surrounding context, it needs to make sense to a stranger
  on first read.

## Common pitfalls

- **Marketing voice** — adjective-heavy, achievement-announcement
  phrasing gets scrolled past or actively mocked by this audience.
- **Burying the news in a lead-up line**, using the scarce 300
  characters on throat-clearing instead of the actual thing being
  announced.
- **A vague ask** that gives a reader nothing concrete to do, so the
  post collects likes but no replies, feedback, or reposts.
- **Treating it like a thread when one post would do** — splitting a
  simple announcement across several posts dilutes it and makes
  quote-posting harder.
- **Skipping alt text** on any screenshot or image included.

## Learn more

- [[share-on-facebook]], [[share-on-instagram]], [[share-on-linkedin]],
  [[share-on-mastodon]], and [[share-on-threads]] for the same
  announcement adapted to each platform's own norms and character
  budget.
- [[copywriting]] for persuasive-copy technique this style
  deliberately underplays in favor of a plainer, personal voice.
- [[content-calendar]] for coordinating the announcement's timing
  across all four platforms.
- [[branding]] for keeping the personal voice here consistent with
  how the project is described elsewhere.