The BskySuite Team

Who we are

BskySuite is made by three people. We are not a content agency or a venture-backed company, and nothing here is outsourced or syndicated. We use Bluesky daily, we build the tools ourselves, and we write the guides ourselves. Guides are published under the BskySuite Team byline, and below is exactly who does what, because it affects how you should read any given article.

Responsibility for everything published under this domain rests with the founder. If something here is wrong, you can reach us directly at hello@bskysuite.com.

Why we built BskySuite

BskySuite started from a practical annoyance. Bluesky has no way to save a video or an image from a post, no view of your own engagement patterns, and no quick way to check whether a handle is free. These are small gaps, but they come up constantly if you use the platform daily. Rather than wait for someone else to solve them, we built the tools we wanted and made them free to use without an account.

The guides came later, for a similar reason. A lot of what is written about Bluesky is either outdated or copied from other articles. Because we work directly against the AT Protocol API when building these tools, we usually end up learning how a feature actually behaves rather than how it is described. Writing that down felt more useful than keeping it to ourselves.

What we work on

• Video & Image Downloader, saves the original media file from any public post.
• Post Screenshot Generator, renders clean, shareable post cards.
• Profile Analytics, surfaces engagement patterns from public data.
• Handle Checker, checks username availability against the live identity API.
• Trending Topics, collects trending hashtags, topics, feeds, and active accounts.
• Bluesky Media Downloader, a free Chrome extension on the Chrome Web Store.

How we work with the AT Protocol

Everything on this site reads public data through Bluesky's public API, the same endpoints the official app uses. No tool here asks for your password, uses a login, or stores what you paste. That constraint is deliberate: it keeps the tools simple, it means we hold no user data worth breaching, and it makes clear that nothing here bypasses anyone's privacy settings. Where that design limits what a tool can do, we say so on the tool's own page rather than overstating what is possible.

How the guides are produced

We test steps against the live platform before publishing them, cite primary sources such as Bluesky's own announcements where a claim depends on them, and state plainly when something cannot be measured. Bluesky's public API does not expose impressions or reach, for example, so we do not publish estimates dressed up as data. Anything touching the protocol, the API, or how our tools behave is reviewed by the founder before it goes out. The full standards are on the editorial policy page, and the data sources behind the tools are documented in the methodology.

Corrections

If you find an error in a guide or a bug in a tool, please tell us. We correct mistakes rather than quietly leaving them up, and revised articles carry an updated date. Email hello@bskysuite.com or use the contact form.

Independent and unaffiliated

BskySuite is an independent project. It is not affiliated with, endorsed by, or sponsored by Bluesky Social PBC. It uses the AT Protocol public API under its open access terms.