agentleFS
bluesky-socialbluesky-social/atproto/.agents/skills/lex-setup/SKILL.md

lex-setup

Skill9.7k starsChanged 3 days agoLicence not identifiedView on GitHub

Wire up, maintain, or troubleshoot `@atproto/lex` code generation and the per-package `lexicons.json` manifest. Use when a package needs generated Lexicon schemas; when adding or editing a `lexicons.json`, its `resolvers` (`directory` / `http` / `repo`) or a `lexicons-overrides` directory; when migrating a package off compiling the repo-root `lexicons` directory; when adding a `codegen:lex` / `lex:install` / `prebuild` script; when `./src/lexicons/` or `./lexicons/` is missing, stale, or gitignored wrong; after editing anything under `lexicons/`; when adding an NSID; when `pnpm codegen`, `lex build`, or `lex install` fails; when `lex` resolves to the wrong binary; when a post-lexicon-edit build reports "type X is not assignable to Y"; or when ripping out legacy `@atproto/lex-cli` codegen. Reach for it before hand-editing anything under a `lexicons/`, `lexicons-overrides/`, or `src/lexicons/` directory, or any `lexicons.json`.

Trending

More talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 1 mentionFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the bluesky-social/atproto repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about bluesky-social/atproto

The biggest 5 of 104 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 104

Talked about on Bluesky, GitHub, Hacker News, YouTube, the web and Stack Overflow (104 times).

On Bluesky · 50

45 more on Bluesky

On GitHub · 41

36 more on GitHub

On Hacker News · 7

2 more on Hacker News

On YouTube · 3

On Stack Overflow · 1

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.