---

name: atmosphere description: Route AT Protocol and Atmosphere work. Trigger for any at:// URI, Bluesky post, Bluesky post URL, or domain-style handle such as @example.domain.com, as well as PDS, DID, repository, record, lexicon, feed, and social-graph tasks. Use the aturi.to Atmosphere MCP for reads and the goat CLI for writes, with goat as the read fallback. #

Atmosphere #

Use this routing rule for all Atmosphere and AT Protocol operations.

Trigger the skill #

Always use this skill when a request contains or concerns any of these:

• An at:// URI.
• A Bluesky post, including a pasted post or a link to one.
• A domain-style handle prefixed with @, such as @example.domain.com.
• Any other AT Protocol or Atmosphere resource or operation.

Route operations #

• Send every read to the installed atmosphere MCP from https://aturi.to/api/mcp.
• Send every write through the goat CLI. This includes creates, updates, deletes, posts, reactions, follows, uploads, account changes, and PDS administration.
• If a request mixes reads and writes, use the MCP for the reads and goat for the writes.
• If the MCP has no tool for a read, use goat for that read.
• If the MCP is unavailable or its call fails because the server, transport, or tool is unavailable, retry the read with goat.
• Treat a successful empty result, not_found, unsupported identity type, validation error, or other meaningful domain response as the result. Do not retry it with goat merely to seek a different answer.
• Do not use a generic web request, browser, or direct AT Protocol HTTP call when the Atmosphere MCP or goat can perform the operation.

Use the MCP #

Choose the most specific mcp__atmosphere__* tool for the read. Follow cursors when the user's requested scope requires more than one page. Use the MCP's discovery and schema tools when the correct collection, lexicon, identity, or API method is not yet known.

The MCP is read-only. Do not use it for mutations even if a write-capable tool becomes available later.

Use goat #

Before running an unfamiliar command, inspect the relevant help, such as goat <command> --help, instead of guessing flags. Preserve the user's existing authentication and configuration. Never print credentials or session tokens.

Only perform a mutation when the user's request authorizes it. Report the affected AT URI, DID, record, or other concrete result when goat returns one. If goat cannot perform an MCP fallback operation, explain the unsupported operation and the command or capability that is missing.