bluesky

1# Bluesky
2 
3## Purpose
4Read and write the user's Bluesky account through the AT Protocol (XRPC): view profiles and the home timeline, search posts, create posts, follow accounts, and list notifications. Use when the user mentions Bluesky or atproto.
5 
6## Tooling
7All commands go through `bin/bluesky.py`. Every command takes a required `--handle` (the account handle, e.g. `me.bsky.social`):
8 
9```bash
10bin/bluesky.py auth --handle me.bsky.social                  # verify the session
11bin/bluesky.py profile --handle me.bsky.social               # view a profile (add --target to view someone else)
12bin/bluesky.py timeline --handle me.bsky.social              # home timeline
13bin/bluesky.py search --handle me.bsky.social --query "agents"  # search posts
14bin/bluesky.py post --handle me.bsky.social --text "hello world"  # publish a post (confirm first)
15bin/bluesky.py follow --handle me.bsky.social --target them.bsky.social  # follow an account (confirm first)
16bin/bluesky.py notifications --handle me.bsky.social         # list notifications
17```
18 
19The CLI resolves the account's PDS automatically (via `resolveHandle` + the DID document), caches the session at `.bluesky-session.json` next to the skill, and refreshes tokens transparently on 401.
20 
21## Auth
22- Provider id: `bluesky` (credential is collected as `custom.bluesky`)
23…