bluesky post

The problem

Managing a Bluesky presence via LLMs usually fails because the AT Protocol requires complex byte-offset calculations for rich text facets like URLs and hashtags. Manual posting through web interfaces breaks developer workflows and prevents automated scheduling.

What it does

• Automates Bluesky posts with auto-detected hashtags and clickable URLs.
• Handles image uploads (up to 4) with mandatory alt text support and automatic JPEG conversion.
• Supports video uploads up to 3 minutes with automated size tiering.
• Schedules posts using ISO 8601 timestamps via the Publora MCP server.
• Calculates precise byte offsets for emojis and multi-byte characters to ensure rich text rendering.

Frameworks & tools

Publora MCP server, Bluesky AT Protocol, Claude Desktop, and REST API fallback.

Why this beats prompting it yourself

Writing a prompt to "post to Bluesky" often results in broken links or plain text hashtags because the LLM cannot natively calculate the required byte-range facets. This skill offloads the protocol complexity to a dedicated MCP server, ensuring your links actually work.

Use cases

• Automate "build in public" updates with dashboard screenshots and alt text.
• Schedule product announcements with demo videos up to 100MB.
• Cross-post technical content with functional, clickable URLs and hashtags.
• Manage multiple Bluesky accounts via DID-based platform IDs.

Known limitations

Requires a Publora account and a Bluesky App Password. Posts are limited to 300 characters and images must be under 1MB.