bluesky-post-writer
Skill1 starsChanged 47 days agoMITView on GitHub
Write Bluesky posts within 300 characters, with links, #hashtags and @mentions that become clickable, and up to 4 images or 1 video, ready to publish with the PostOnce Bluesky MCP. Use when the user asks to write a Bluesky post, a skeet, or to turn an update, article, video or tweet into a Bluesky post.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Write one Bluesky post that fits in 300 characters and reads like a person wrote it, then hand it to the postonce skill if the user wants …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bluesky post writer
Write one Bluesky post that fits in 300 characters and reads like a person wrote it, then hand it to the postonce skill if the user wants it published or scheduled.
Before writing
Get or infer: the account and its voice, who they want to reach, the one idea, and any fact, link or example that proves it. From a long source, pick one idea. Never invent numbers, results, customers or quotes. If the user hands you a tweet, rewrite it for Bluesky rather than pasting it.
The limit
300 characters. Text over it is cut off at publish, not rejected, so the ending disappears. Count links at full length and count each emoji as 2 or more (some emoji are several characters). Aim for 150–280 so there's room.
What works on Bluesky
- Conversational and direct. Bluesky readers respond to people talking, not brand announcements.
- Line 1 says the point. No slow wind-up.
- Specifics: a number, a screenshot, a real example, a named thing.
- One idea per post. If it needs more, write standalone posts (see below).
- Community-minded tone: credit people with @mentions when you're building on their work.
- Custom feeds pick up posts by keyword and hashtag, so use the words the audience actually searches for.
Rich text
Links, #hashtags and @mentions are turned into clickable rich text when the post publishes.
- @mentions need the full handle (
@name.bsky.socialor a custom domain handle like@name.com). - Hashtags: 0–2, specific ones people follow (
#buildinpublic,#rstats), at the end or inline. - Links are clickable but no link preview card is attached. If the link needs a visual, add an image.
Media
Up to 4 images (JPEG, PNG, WEBP or GIF; large images are resized to fit Bluesky's 2 MB limit), or 1 video (up to 3 minutes and 100 MB). Don't mix images and video. Alt text isn't sent through this server, so put anything essential about the image in the post text, or post from the Bluesky app if alt text matters for that post.
What this server can't do
No threads or replies, no quote posts, no link cards, no editing after it's published. For a longer idea, offer either standalone posts that each make sense alone (schedule them apart), or publishing the first post and giving the user the rest to add as replies in the Bluesky app.
Anti-patterns
- Cross-posted tweets with X-only references ("RT", "quote tweet",
@handlesthat don't exist on Bluesky). - Hashtag walls, engagement bait, "🧵" on a single post.
- "Game-changer", "unlock", "let's dive in".
Output
Give 2 versions, each with its character count, and mark the one you'd post. Note any image to attach. Offer to publish or schedule it with the postonce skill; confirm the Bluesky account and the time (with timezone) before calling create_post.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

