bsky
Use this when working with BlueSky - fetching threads, reading posts, creating content. Shows you how to use pdsx MCP tools for the task.
When & Why to Use This Skill
This Claude skill enables seamless interaction with the BlueSky social network using pdsx MCP tools. It allows users to programmatically fetch threads, read specific posts, manage profiles, and create new content. By leveraging the AT Protocol and supporting advanced JMESPath filtering, it simplifies complex social media tasks such as conversation tracking and automated engagement, making it a powerful asset for developers and social media managers.
Use Cases
- Social Media Monitoring: Automatically track mentions, specific keywords, or industry trends across BlueSky threads to stay informed on relevant discussions.
- Automated Content Management: Create and publish posts or replies programmatically to maintain a consistent brand presence and engage with the community.
- Thread Analysis and Summarization: Fetch entire conversation trees to extract key insights, participant perspectives, and summarize long-form discussions.
- Data Extraction and Research: Use advanced filtering to retrieve specific data points like links, user DIDs, or engagement metrics from the BlueSky ecosystem.
- Profile and Network Management: Programmatically retrieve profile details, manage follows, and interact with likes or reposts to streamline account administration.
| name | bsky |
|---|---|
| description | Use this when working with BlueSky - fetching threads, reading posts, creating content. Shows you how to use pdsx MCP tools for the task. |
BlueSky with pdsx
Use the pdsx MCP tools (list_records, get_record, create_record, etc.) for BlueSky tasks.
Quick Reference
| Task | Tool | Example |
|---|---|---|
| get a post | get_record |
get_record(uri="at://did:plc:xxx/app.bsky.feed.post/abc123") |
| list someone's posts | list_records |
list_records("app.bsky.feed.post", repo="handle.bsky.social") |
| get a profile | get_record |
get_record(uri="app.bsky.actor.profile/self", repo="handle.bsky.social") |
| create a post | create_record |
create_record("app.bsky.feed.post", {"text": "hello"}) |
Following Threads
Threads span multiple users. Pattern:
Get the root post to see its content and who posted it:
get_record(uri="at://did:plc:xxx/app.bsky.feed.post/abc123")List the OP's posts and filter for replies to extract participant DIDs:
list_records("app.bsky.feed.post", repo="did:plc:xxx", _filter="[?reply].reply.parent.uri")Extract DIDs from the URIs (format:
at://DID/collection/rkey)Query each participant's posts for their contributions to the thread:
list_records("app.bsky.feed.post", repo="did:plc:other", _filter="[?reply.root.uri=='at://did:plc:xxx/app.bsky.feed.post/abc123']")
Collections
| Collection | Purpose |
|---|---|
app.bsky.feed.post |
posts |
app.bsky.actor.profile |
profile (rkey is always self) |
app.bsky.feed.like |
likes |
app.bsky.feed.repost |
reposts |
app.bsky.graph.follow |
follows |
Post Structure
Posts reference other posts via reply:
{
"text": "reply text",
"reply": {
"root": {"uri": "at://did/collection/rkey", "cid": "bafyrei..."},
"parent": {"uri": "at://did/collection/rkey", "cid": "bafyrei..."}
}
}
reply.root- thread's original postreply.parent- immediate parent being replied to
Creating Posts
Simple:
create_record("app.bsky.feed.post", {"text": "hello world"})
Reply (requires both uri AND cid from the parent/root posts):
create_record("app.bsky.feed.post", {
"text": "my reply",
"reply": {
"root": {"uri": "at://...", "cid": "..."},
"parent": {"uri": "at://...", "cid": "..."}
}
})
Filtering with _filter
The _filter parameter uses JMESPath:
# just the text from posts
list_records(..., _filter="[*].text")
# reply URIs only
list_records(..., _filter="[?reply].reply.parent.uri")
# posts with specific text
list_records(..., _filter="[?contains(text, 'keyword')]")
Gotchas
- strongRef needs uri AND cid - when creating replies, you need both from the parent post
- profile rkey is always
self- useapp.bsky.actor.profile/self - byte indices for facets - links/mentions use UTF-8 byte positions, not character positions