atprotoing

Solid

Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.

API & Backend 148 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# ATProtoing Reads the atmosphere from sources that stay up when Bluesky PLC's AppView does not. On 2026-08-16 the AppView timed out and Jetstream returned 503 while PDSes and Constellation served every request — this skill is built around that split. ## Invoke ```bash python3 <skill>/scripts/atproto.py <command> [--json] ``` Digest output is the default and is what belongs in a transcript. Reach for `--json` only when the result will be transformed programmatically; raw records are large and re-reading them into context defeats the purpose. | Command | Answers | |---|---| | `feed [actor] [--hours 3] [--html PATH]` | The Following timeline, threaded | | `status [--actor X]` | Which layer is broken right now | | `interactions <actor> [--hours 8] [--scan 100]` | Who liked/replied/reposted/quoted recent posts | | `thread <at-uri>` | Replies to a post | | `posts <actor> [--limit]` | An actor's posts, from their own PDS | | `records <actor> <collection>` | Any collection in any repo | | `resolve <actor>` | DID, handle, PDS host | | `backlinks <target> [--collection C --path P]` | What references a record or account, in ANY lexicon | | `identity <actor>` | Handle renames and PDS migrations, from the PLC audit log | | `lexicons [query] [--hours N] [--others] [--schema NSID]` | Which collections are active network-wide | ## Source model Each read targets the cheapest source that survives independently. Prefer the PDS for anything a repo owns �� it is authoritative and had no o...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category