AI agent skills related to using social media
Draft an ATproto skill
+60
+60
atproto/SKILL.md
+60
atproto/SKILL.md
···
1
+
---
2
+
name: atproto
3
+
description: "Use this skill whenever interacting with the AT Protocol ecosystem, including Bluesky, Tangled, wisp.place, BookHive, and other related platforms built on AT Protocol. Triggers include: any mention of 'AT Protocol', 'Bluesky', 'Tangled', or related terms. Also use when working with AT Protocol APIs, Bluesky clients, or any tools and libraries specific to the AT Protocol or Bluesky ecosystem."
4
+
---
5
+
6
+
# AT Protocol
7
+
8
+
## Overview
9
+
10
+
The AT Protocol (Authenticated Transfer Protocol, AKA "ATproto" or "atproto")
11
+
is a decentralized social networking protocol designed to enable
12
+
interoperability and user control across different platforms. It allows users
13
+
to create and manage their own social media presence while maintaining
14
+
ownership of their data. The AT Protocol is the foundation for platforms like
15
+
Bluesky, Tangled, wisp.place, BookHive, and other related ecosystems built on
16
+
top of it. Protocol docs are available at <https://atproto.com/docs>.
17
+
18
+
### DIDs
19
+
20
+
The AT Protocol uses DIDs (Decentralized Identifiers) to identify user
21
+
accounts. A DNS domain may be associated with a DID via an _atproto TXT record,
22
+
allowing for more human-readable identifiers, but the DID itself is the
23
+
authoritative identifier for the account. Every DID is associated with a DID
24
+
Document, which contains information about the account, including both
25
+
cryptoraphic keys used to certify changes to the DID document and a reference
26
+
to the user's Personal Data Server (PDS).
27
+
28
+
### Records
29
+
30
+
All user data in the AT Protocol is stored as records, which are structured
31
+
pieces of JSON data inside a PDS. Currently (February 2026), all records are
32
+
public and viewable by anyone without requiring a login. Every record is
33
+
associated with a DID, which identifies the account that created and owns the
34
+
record. AT protocol apps cannot create, modify, or delete records without
35
+
user permission, enforced by the user's PDS. Each record has a *lexicon*,
36
+
identified by a Namespaced Identifier (NSID), of the form `app.bsky.feed.post`,
37
+
`app.bsky.actor.profile`, and similar. Every record also has a *record key*, an
38
+
identifier that distinguishes different records of the same type created by the
39
+
same account.
40
+
41
+
### at:// URIs
42
+
43
+
The AT Protocol uses a custom URI scheme, `at://`, to identify records and
44
+
accounts. An `at://` URI of the form `at://<did>` or `at://<DNS domain>`
45
+
identifies a user account (the former by DID, the latter by the DID associated
46
+
with the DNS domain at time of resolution). An `at://` URI of the form
47
+
`at://<did or domain>/<lexicon nsid>` identifies a collection of records of
48
+
the given lexicon for the given account. An `at://` URI of the form
49
+
`at://<did or domain>/<lexicon nsid>/<record key>` identifies a specific
50
+
record.
51
+
52
+
## Using PDSls
53
+
54
+
You can use the https://pdsls.dev/ website to explore ATprotocol accounts
55
+
and records. Put any `at://` URI at the end of the URL to view the
56
+
corresponding ATproto resource, such as in the following:
57
+
58
+
```
59
+
https://pdsls.dev/at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.feed.post/3l6oveex3ii2l
60
+
```