How do I install the Server Foundation skill?

Run npx skillmds@latest add ryan-brosas/server-foundation 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 Server Foundation 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 Server Foundation?

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 Server Foundation free to use?

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

Who published Server Foundation?

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

Server Foundation by ryan-brosas — Agent Skill

Name: Server Foundation
Author: ryan-brosas

Server Foundation

Use when porting multi-engine push/notification fan-out, Azure Notification Hubs registration pools, tag-based targeting/exclusion grammars, installation-relay protocols for self-hosted instances, feature-flagged per-user vault-sync fan-out, or the real-time consumer side: SignalR hub group grammars and connect lifecycles, queue-consumer poll/poison loops, internal send ingress, wire-format contract tables across rolling deploys, and pre-auth token-as-group waiting rooms. Source code and direct tests are ground truth; references carry decisive excerpts and graph retrieval.

ryan-brosas 533847c 13 files · 54.3 KB Updated Sep 17, 2026

File contents

Bitwarden server: push-notification platform foundation

Foundation contract

This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.

Provenance and revision

Source record: server; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.
Recorded revision: main@ac309aa19ed351406a56032d5f26a7a9a99f4abd.
Full provenance, coverage caveats, boundaries, and preserved evidence: references/index.md.

Topic map

Representative topics: Fan-out kernel; Hub pool; Tag grammar; Relay guards; Registration; Cipher sync; Hub groups; Queue consumer.
Scope and retrieval questions: references/index.md#use-this-for.
Complete capsule chooser: references/index.md#load-the-matching-source-dump.
Detailed grouped map: references/index.md#capsule-map.
Source limitations and portability boundaries: references/index.md#boundaries.

Retrieval

Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.

---name: server-foundationdescription: Use when porting multi-engine push/notification fan-out, Azure Notification Hubs registration pools, tag-based targeting/exclusion grammars, installation-relay protocols for self-hosted instances, feature-flagged per-user vault-sync fan-out, or the real-time consumer side: SignalR hub group grammars and connect lifecycles, queue-consumer poll/poison loops, internal send ingress, wire-format contract tables across rolling deploys, and pre-auth token-as-group waiting rooms. Source code and direct tests are ground truth; references carry decisive excerpts and graph retrieval.---# Bitwarden server: push-notification platform foundation## Foundation contractThis is a cold, source-specific foundation, not an operational procedure. It ishistorical, revision-pinned evidence rather than timeless guidance. Currentproject source, tests, requirements, and runtime behavior outrank thisprojection and decide what ships.## Provenance and revision- Source record: `server`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.- Recorded revision: `main@ac309aa19ed351406a56032d5f26a7a9a99f4abd`.- Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`.## Topic map- Representative topics: Fan-out kernel; Hub pool; Tag grammar; Relay guards; Registration; Cipher sync; Hub groups; Queue consumer.- Scope and retrieval questions: `references/index.md#use-this-for`.- Complete capsule chooser: `references/index.md#load-the-matching-source-dump`.- Detailed grouped map: `references/index.md#capsule-map`.- Source limitations and portability boundaries: `references/index.md#boundaries`.## RetrievalOpen the index, choose one capsule matching the active question, and load onlythat capsule. Revalidate its cited source and revision before relying on it. Donot bulk-load the inventory, treat historical claims as current truth, or applythis foundation as a procedure.

Frequently asked questions