bluesky-post
Post to Bluesky with rich text facets, images, videos, and alt text support via Publora MCP
53
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/bluesky-post/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is specific about capabilities and clearly targets a distinct niche (Bluesky posting via Publora MCP), making it easy to distinguish from other skills. However, it lacks an explicit 'Use when...' clause, which is important for Claude to know when to select this skill, and could benefit from more natural user-facing trigger terms beyond the technical tool name.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to post or publish content to Bluesky, share images/videos on Bluesky, or create social media posts for the AT Protocol network.'
Include additional natural trigger terms users might say, such as 'social media post', 'share on Bluesky', 'publish to Bluesky', or 'Bluesky social'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: posting to Bluesky with rich text facets, images, videos, and alt text support. These are distinct, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (post to Bluesky with rich text, images, videos, alt text) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Bluesky', 'images', 'videos', 'alt text', and 'post', but misses common variations users might say like 'social media', 'share', 'publish', 'tweet-like', or 'AT Protocol'. 'Publora MCP' is technical jargon most users wouldn't use. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Bluesky posting via Publora MCP is highly specific and unlikely to conflict with other skills. The platform name and tool name create a clear, unique identity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill covers Bluesky posting comprehensively with good reference tables and troubleshooting, but suffers from verbosity (social media tips, pricing details) and incomplete actionability for multi-step workflows like image/video uploads. The examples show user prompts rather than actual tool call sequences, which means Claude must infer the correct implementation chain.
Suggestions
Add an explicit step-by-step workflow for image posts showing the full chain: create_post → get_upload_url → PUT to presigned URL, with expected responses at each step
Remove the Best Practices timing/engagement sections and plan pricing table - these are social media advice Claude doesn't need for the technical task of posting
Replace the natural language examples with actual tool call sequences showing parameters and expected responses
Consider splitting REST API fallback and troubleshooting into separate referenced files to reduce the main skill's token footprint
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful information but is verbose in several areas. The plan pricing table, engagement best practices ('Bluesky favors authentic conversation', 'Reply to comments'), and timing tips ('Growing platform', 'Tech-savvy audience') are filler that Claude doesn't need. The REST API fallback section adds significant length. However, the core technical content (limits, tools, examples) is reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete API examples and tool parameter descriptions, but the workflow for actually creating a post with images/video is incomplete - there's no step-by-step showing how to chain create_post → get_upload_url → upload to presigned URL. The 'Examples' section shows natural language prompts rather than executable tool call sequences, leaving Claude to infer the actual implementation. | 2 / 3 |
Workflow Clarity | The getting started steps are clearly sequenced, but the core posting workflows lack explicit step sequences. For image/video posts (multi-step: create post → get upload URL → upload media), there's no clear numbered workflow with validation checkpoints. The troubleshooting table partially compensates but doesn't constitute inline validation steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's a long monolithic file (~180 lines) that could benefit from splitting. The REST API fallback, video size tiers, and detailed troubleshooting could be in separate referenced files. The link to docs.publora.com is good but the inline content is heavy. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- publora/skills
- Commit
8e5bffe
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.