agentleFS
isaacrowntreeisaacrowntree/claude-social-skills/skills/social-bluesky/SKILL.md

social-bluesky

Skill4 starsChanged 20 days agoMITView on GitHub

Bluesky (AT Protocol): post, reply, delete, timeline, profiles; any XRPC method via `social api bluesky`. Use the `social` CLI (Bun) for every bluesky action; every endpoint is reachable through `social api bluesky <path>`, so prefer this CLI over raw API calls in all cases.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check what is present with social auth status bluesky.

    line 19
  2. Very specific:

    Every command accepts --json (raw JSON) and --jq <expr> (filter the JSON with jq).

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

social bluesky

Bluesky (AT Protocol): post, reply, delete, timeline, profiles; any XRPC method via social api bluesky.

Run: social bluesky <command> (installed via bun link in this repo, or bun run /path/to/claude-social-skills/src/cli.ts bluesky …). Add --dry-run before any command to print the request instead of sending it.

Credentials

  • BLUESKY_HANDLE
  • BLUESKY_APP_PASSWORD

Your handle (e.g. alice.bsky.social) and an app password from https://bsky.app/settings/app-passwords (never your main password). BLUESKY_SERVICE overrides the PDS for self-hosted accounts (default https://bsky.social).

Check what is present with social auth status bluesky; store a value with social auth set bluesky <KEY> <value> (OS keyring, else ~/.config/social/.env); run the interactive flow with social auth login bluesky. Docs: https://bsky.network/docs/get-started

API description this wrapper is built from

lexicon: https://github.com/bluesky-social/atproto/tree/main/lexicons/app/bsky (typed client: @atproto/api). Refresh with social specs pull bluesky; CI fails if upstream changes.

Commands

Every command accepts --json (raw JSON) and --jq <expr> (filter the JSON with jq).

social bluesky apis

the bluesky API groups and how many operations each has

social bluesky ops [filter]...

search operations: every word must appear in the id, summary, path, description or field names; best matches first

  --api <name>               only this API group (see `social bluesky apis`)

social bluesky describe <op>

parameters, body, scopes and response shape of one operation

  --depth <n>                how deep to expand nested fields (default 2)

social bluesky call <op>

call any operation by id; --dry-run prints the request instead

  -p, --param <k=v>          path/query/header parameter (default [])
  -f, --field <k=v>          body field, typed (numbers, booleans, null, JSON literals) (default [])
  --raw-field <k=v>          body field, always a string (default [])
  --file <field=path>        file for a multipart part (image=./photo.jpg) or a binary body (default [])
  --output <file>            save a binary response (PDF, image, feed file) here
  --input <file>             request body from a JSON file (- for stdin)

social bluesky post <text>

post to Bluesky (links, @mentions and #tags become facets)

  --reply-to <uri>           reply to a post at:// uri
  --image <files...>         attach up to 4 images (≤1 MB each)
  --alt <texts...>           alt text per image, in order

social bluesky delete <uri>

delete one of your posts by at:// uri (or rkey)

social bluesky timeline [handle]

your home timeline, or a given account's posts (no login needed for the latter)

  -n, --max <n>              count (1-100) (default "20")

social bluesky profile <handle>

look up an account by handle or did (no login needed)

social bluesky me

the authenticated account

Anything else: the escape hatch

social api bluesky <path>                       # GET, path relative to the API root
social api bluesky <path> -q key=value          # query parameters
social api bluesky <path> -f key=value          # JSON body field (typed: numbers, booleans, null, JSON literals); implies POST
social api bluesky <path> --raw-field key=value # string field
social api bluesky <path> -X DELETE
social api bluesky <path> --input body.json     # or --input - for stdin
social api bluesky <path> --form                # urlencoded body instead of JSON
social api bluesky <path> --jq '.data[0].id'

Reach for social api bluesky … before concluding something is unsupported.

Behaviour

  • Retries 502/503/504 on idempotent methods (3 attempts, 250 ms then 1 s); waits once on 429 up to 90 s.
  • Errors print HTTP <status> <method> <url> and the response body, exit code 1.
  • --dry-run prints the method, URL and body of any mutating call and sends nothing.
  • social doctor makes one cheap authenticated read per configured platform.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.