agentleFS
Sign inStart free
navidmoazzeznavidmoazzez/bluesky-mcp-cli/AGENTS.md

bluesky-mcp-cli

AGENTS.md0 starsChanged 39 days agoMITView on GitHub

For agents editing this repository. Users read the README. Driving the server is SKILL.md. This repo is the reference implementation for the house standard, so a shortcut taken here gets copied into every server built afterwards. Commit as n@navid.me. Never pass -c user.email=. The global config is correct and the override is the bug: the wrong address credits a blocked account and the Contributors panel reads 0. Writes are on by default. BLUESKY_READ_ONLY=1 is the opt-out and it works by…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. thenavidm/bluesky-mcp-cli★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit as n@navid.me: Never pass -c user.email=.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Working on bluesky-mcp

For agents editing this repository. Users read the README. Driving the server is SKILL.md.

This repo is the reference implementation for the house standard, so a shortcut taken here gets copied into every server built afterwards.

Layout

src/app.ts      the Slipway app: tools, settings, doctor. Slipway owns both surfaces, the guard and the audit log
src/guide.ts    server instructions, resources and prompts
src/api/        client, errors, identity resolution
src/content/    facets, media, mp4, text. The AT Protocol specifics
src/tools/      one module per group, registered in tools/index.ts

Non-negotiables

Commit as n@navid.me. Never pass -c user.email=. The global config is correct and the override is the bug: the wrong address credits a blocked account and the Contributors panel reads 0.

Writes are on by default. BLUESKY_READ_ONLY=1 is the opt-out and it works by not registering the write tools, not by refusing at call time. A model cannot call a tool it cannot see.

confirm: true on operations that reach other people only. Posting, threads, deleting, blocking. Not likes, reposts, follows or mutes. The test is not "does it write" but "can the person undo it in one action from their own client". Confirming everything is what makes the confirmation on a delete worthless.

Every anticipated failure is an AtpError subclass from api/errors.ts. Slipway maps its HTTP status to the exit code and keeps its message, so a plain Error reaches the model as an unexpected failure with your explanation lost.

Facets are computed, never accepted from the caller. content/facets.ts turns URLs, hashtags and mentions into real links. Byte offsets, not character offsets: the AT Protocol counts UTF-8 bytes, so an emoji shifts every facet after it if you count characters.

create_thread validates every part before posting any, so a thread cannot half-publish because part four was too long.

Never add anything that automates the follow graph. It is what gets accounts limited.

Before claiming it works

npm run build && npm test && npm run typecheck
npx @modelcontextprotocol/inspector node dist/index.js

A green suite is not a working server. Run the handshake.

Download now (ZIP)

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.

Check your setup, free