atproto

Coordinate AT Protocol authentication, lexicons, and record handling for Bluesky integrations.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill atproto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atproto
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/atproto
Command: npx skills add https://github.com/dotBeeps/pantry --skill atproto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes clear rules and best practices for integrating the AT Protocol with Bluesky, covering client authentication, lexicons, and record handling to reduce misconfigurations and security risks.

Core Features & Use Cases

  • Client & Auth guidance for proper OAuth with DPoP and avoiding legacy app passwords.
  • Data modeling rules for lexicon IDs, DIDs, AT-URIs, and strong references to ensure consistent references across systems.
  • Firehose, indexing, and repository backfill guidance to maintain data integrity across updates.

Quick Start

Configure your client with the recommended AT Protocol authentication flow, including OAuth with DPoP, DID discovery, and lexicon usage to begin Bluesky integration.

Frequently Asked Questions about atproto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate with Bluesky using AT Protocol OAuth?

AT Protocol authentication uses OAuth with DPoP for secure login. You must implement proper nonce rotation and DID discovery to avoid legacy app passwords and ensure safe client access.

What is the best way to handle lexicons and AT-URIs for Bluesky data modeling?

Lexicons and AT-URIs require strict data modeling rules to ensure consistent references across systems. Properly formatted lexicon IDs, DIDs, and strong references maintain data integrity across PDS-based networks.

Can I use this for indexing and backfilling Bluesky repositories from the firehose?

Yes, this provides firehose, indexing, and repository backfill guidance. It enforces robust error handling to maintain data integrity and reliability across network updates and record synchronization.

Does AT Protocol integration require resolving DIDs before making API calls?

DID discovery is required before establishing secure connections. Resolving DIDs ensures proper identity verification across PDS-based networks and enables safe reference management for client-side apps.

Why should I avoid legacy app passwords when building Bluesky apps?

Legacy app passwords lack the security of OAuth with DPoP. Proper AT Protocol authentication flows enforce nonce rotation and DID discovery to reduce misconfigurations and security risks.

What limitations exist when handling AT-URI references across PDS networks?

AT-URI handling requires careful reference management to maintain consistency. Without proper error handling and strong references, data integrity can break during repository updates and firehose indexing.