atproto-publish-lexicon

Publish and resolve AT Protocol lexicons as com.atproto.lexicon.schema records.

46|3|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/ngerakines/atproto-skills --skill atproto-publish-lexicon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atproto-publish-lexicon
Source: https://github.com/ngerakines/atproto-skills/tree/main/skills/atproto-publish-lexicon
Command: npx skills add https://github.com/ngerakines/atproto-skills --skill atproto-publish-lexicon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Publishing AT Protocol lexicons as com.atproto.lexicon.schema records and resolving them back to lexicon documents is a coordinated workflow that requires aligning DNS authority, DID binding, and on-chain publication. This skill codifies the end-to-end process and provides guardrails for correctness.

Core Features & Use Cases

  • Publishes new lexicons and revisions to a DID-based repo, including authority checks, CID validation, and monotonic revision management.
  • Resolves NSIDs to published lexicon records, detailing authority binding, DNS TXT records, and DID-to-PDS resolution, to help debugging and integration.
  • Supports end-to-end publishing workflows and resolution traces across the lexicon lifecycle, from authoring to network publication.

Quick Start

Publish a lexicon by wrapping your lexicon document as a com.atproto.lexicon.schema record and publishing it to the publishing DID's repo with putRecord (validation enabled).

Frequently Asked Questions about atproto-publish-lexicon

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

FAQPage Schema
How do I publish an AT Protocol lexicon to a DID repository?

Publish an AT Protocol lexicon by wrapping your document as a com.atproto.lexicon.schema record and writing it to a DID-based repository using putRecord with validation enabled.

How does DNS authority binding work for AT Protocol lexicons?

DNS authority binding for AT Protocol lexicons uses _lexicon TXT records to verify that a publishing DID is authorized to claim a specific NSID, ensuring secure resolution.

What is the best way to resolve an NSID back to a published lexicon document?

Resolve an NSID to a published lexicon document by tracing authority bindings, checking DNS TXT records, and performing DID-to-PDS resolution to locate the repository containing the schema.

How do I manage lexicon revisions and ensure CID canonicalization?

Manage lexicon revisions by enforcing monotonic revision sequencing and applying CID canonicalization to maintain consistent record integrity across updates in the DID repository.

Can I use this to debug lexicon resolution failures across the network?

Debug lexicon resolution failures by generating end-to-end resolution traces that detail authority binding, DNS TXT record verification, and DID-to-PDS routing for the target NSID.

What limitations exist when publishing AT Protocol lexicons with DNS authority?

Limitations include strict enforcement of record shape, authority binding via DNS, and monotonic revision sequencing, meaning out-of-order updates or mismatched DNS TXT records will fail publication.