agentleFS
Sign inStart free
berntpoppberntpopp/genefoundry-router/.claude/skills/backend-registry-change/SKILL.md

backend-registry-change

Skill6 starsChanged 4 months agoMITView on GitHub

Use when adding, removing, enabling/disabling, or reconfiguring a backend in the router's servers.yaml registry (URLs, namespaces, entrypoints, server_name/transform overrides).

  • Reads credentials

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Follow AGENTS.md first. servers.yaml is the source of truth for the federated fleet.

    line 8
  2. Very specific:

    Never expose a backend directly — it stays behind the router / proxy.

    line 17

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

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

Backend Registry Change

Follow AGENTS.md first. servers.yaml is the source of truth for the federated fleet; URLs/secrets live in .env.

Workflow

  1. Edit the backend's entry in servers.yaml. Keys per server: name, repo, url_env (the .env var holding the URL), namespace, tags, entrypoints; enabled defaults true via the defaults block. Add the URL var to .env / .env.example.
  2. entrypoints seed the discovery catalog / golden tasks — set the common first-call tools for a new backend.
  3. Prefer namespacing over transforms. The current fleet has no transform blocks (all backends adopted Tool-Naming v1). Use server_name only to reconcile a backend whose ratified serverInfo.name differs from its registry alias (e.g. spliceai → spliceailookup-link). If you must add a transform, delete it once the backend fixes naming upstream.
  4. make validate (config schema) → make list-tools (namespaced, collision-free surface) → make fleet-probe (live reachability + non-zero tool harvest; fail loud on 0-tool backends).
  5. make snapshot-catalog to regenerate the discovery catalog; keep the guard test green.
  6. Never expose a backend directly — it stays behind the router / proxy. Run make ci-local.

Common mistakes

  • Using url instead of url_env, or forgetting to add the var to .env.
  • Adding a transform to patch a naming issue the backend should fix upstream.
  • Enabling a backend without fleet-probe — a 307 redirect or 0-tool backend passes CI but is dead in prod.

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.

Reviews can't be read right now.

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