How do I install the Update Chat Lexicons skill?

Run npx skillmds@latest add bluesky-social/update-chat-lexicons in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Chat Lexicons safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Chat Lexicons?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Chat Lexicons free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Chat Lexicons?

bluesky-social (@bluesky-social) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Chat Lexicons by bluesky-social

Name: Update Chat Lexicons
Author: bluesky-social

Update Chat Lexicons

Sync `chat.bsky.*` Lexicon JSON from the private `bluesky-social/chat` repo into this monorepo, regenerate the code derived from it, and add a changeset. Use whenever asked to update, sync, pull, refresh, or copy chat lexicons, to pick up new or changed chat convo, group, moderation, or notification definitions, or to reconcile `lexicons/chat/` with the chat service — including when the request is just "update chat lexicons".

File contents

Update chat lexicons

lexicons/chat/bsky/** is a mirror. The source of truth is the separate bluesky-social/chat repo, so an update is a copy plus codegen plus a changeset — the copy on its own leaves the generated clients stale.

1. Refresh the source checkout

This assumes a sibling clone at ../chat. Update it first: step 2 copies with --delete, so syncing from a checkout that is behind will delete lexicons that still exist upstream.

git -C ../chat pull --ff-only

If ../chat doesn't exist, bluesky-social/chat is private and not web-fetchable — clone it with gh repo clone bluesky-social/chat ../chat, or ask the user where their checkout lives and substitute that path below. Don't improvise a source from the destination; there would be nothing to sync.

2. Copy

rsync -a --delete ../chat/lexicons/chat/ ./lexicons/chat/

Only lexicons/chat/ is mirrored. The chat repo also carries app/, com/, and tools/ lexicons that diverge from this repo's — never sync those.

Check git status immediately. Unexpected deletions almost always mean the source checkout is behind, not that definitions were dropped upstream.

3. Regenerate

pnpm codegen

Run this from the repo root, and use pnpm codegen rather than pnpm build: packages/api and packages/ozone regenerate only when a lexicon file is newer than their generated index, and rsync -a preserves the source's mtimes — so a build can decide nothing changed and silently keep stale types. pnpm codegen invokes the generators unconditionally, building the codegen tooling itself first.

Both generated trees are gitignored, so the commit diff shows only JSON. The real blast radius stays invisible until you build.

4. Changeset

Add a file under .changeset/ with a three-word kebab-case name:

---
'@atproto/api': patch
---

update chat lexicons

A patch on @atproto/api alone is the established convention here (see git log --oneline -- lexicons/chat). @atproto/ozone also generates from these lexicons but picks up an automatic dependency bump, so don't list it by hand. Use minor instead if the sync removes or renames a definition — that breaks the published types.

5. Verify

(cd packages/api && pnpm build && pnpm test)
(cd packages/ozone && pnpm build)

Ozone's build typechecks its route handlers against the regenerated server types, which is where a removed or narrowed chat definition actually surfaces.

Then review the diff and commit. Before opening a PR, run the full checks from the root: pnpm build --force && pnpm verify.

---name: update-chat-lexiconsdescription: Sync `chat.bsky.*` Lexicon JSON from the private `bluesky-social/chat` repo into this monorepo, regenerate the code derived from it, and add a changeset. Use whenever asked to update, sync, pull, refresh, or copy chat lexicons, to pick up new or changed chat convo, group, moderation, or notification definitions, or to reconcile `lexicons/chat/` with the chat service — including when the request is just "update chat lexicons".---# Update chat lexicons`lexicons/chat/bsky/**` is a mirror. The source of truth is the separate`bluesky-social/chat` repo, so an update is a copy _plus_ codegen _plus_ achangeset — the copy on its own leaves the generated clients stale.## 1. Refresh the source checkoutThis assumes a sibling clone at `../chat`. Update it first: step 2 copies with`--delete`, so syncing from a checkout that is behind will delete lexicons thatstill exist upstream.```bashgit -C ../chat pull --ff-only```If `../chat` doesn't exist, `bluesky-social/chat` is private and notweb-fetchable — clone it with `gh repo clone bluesky-social/chat ../chat`, orask the user where their checkout lives and substitute that path below. Don'timprovise a source from the destination; there would be nothing to sync.## 2. Copy```bashrsync -a --delete ../chat/lexicons/chat/ ./lexicons/chat/```Only `lexicons/chat/` is mirrored. The chat repo also carries `app/`, `com/`,and `tools/` lexicons that diverge from this repo's — never sync those.Check `git status` immediately. Unexpected deletions almost always mean thesource checkout is behind, not that definitions were dropped upstream.## 3. Regenerate```bashpnpm codegen```Run this from the repo root, and use `pnpm codegen` rather than `pnpm build`:`packages/api` and `packages/ozone` regenerate only when a lexicon file is_newer_ than their generated index, and `rsync -a` preserves the source'smtimes — so a build can decide nothing changed and silently keep stale types.`pnpm codegen` invokes the generators unconditionally, building the codegentooling itself first.Both generated trees are gitignored, so the commit diff shows only JSON. Thereal blast radius stays invisible until you build.## 4. ChangesetAdd a file under `.changeset/` with a three-word kebab-case name:```markdown---'@atproto/api': patch---update chat lexicons```A patch on `@atproto/api` alone is the established convention here (see`git log --oneline -- lexicons/chat`). `@atproto/ozone` also generates fromthese lexicons but picks up an automatic dependency bump, so don't list it byhand. Use `minor` instead if the sync removes or renames a definition — thatbreaks the published types.## 5. Verify```bash(cd packages/api && pnpm build && pnpm test)(cd packages/ozone && pnpm build)```Ozone's build typechecks its route handlers against the regenerated servertypes, which is where a removed or narrowed chat definition actually surfaces.Then review the diff and commit. Before opening a PR, run the full checks fromthe root: `pnpm build --force && pnpm verify`.

Frequently asked questions