Agent skill

Managedcode Orleans Signalr

by managedcode in managedcode/dotnet-skills

Integrate ManagedCode.Orleans.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state.

MITAuto-check passed

Install Managedcode Orleans Signalr

skills CLI
$ npx skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills managedcode-orleans-signalr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Libraries/ManagedCode-Orleans-SignalR/skills/managedcode-orleans-signalr .claude/skills/managedcode-orleans-signalr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managedcode-orleans-signalr
GitHub stars
486
Token cost
~1.9k tokens
SKILL.md length
579 words
Files
2
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Integrate ManagedCode.Orleans.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state.

  • Works in 5 steps: Choose combined or separate… → Configure authenticated connection,… → Keep publishing at an explicit… → …
  • : Orleans backplane setup
  • SKILL.md covers Trigger On, Install, Configure the Backplane and Send and Receive Updates, plus 5 more sections
  • Calls dotnet

What it does

Managedcode Orleans Signalr is an agent skill from managedcode/dotnet-skills. Integrate ManagedCode.Orleans.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state. USE FOR: Orleans backplane setup, grain-to-hub publishing, reconnect, heartbeat, and client-invocation failures. DO NOT USE FOR: ordinary SignalR without Orleans or unrelated persistence. INVOKES: inspect configuration, implement the integration, and validate connected-client delivery.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `manifest.json`). Compatibility notes: Requires a .NET application with compatible Orleans and ASP.NET Core SignalR packages; use aligned ManagedCode.Orleans.SignalR Client and Server versions.

The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : Orleans backplane setup
  • Grain-to-hub publishing
  • Client-invocation failures
  • : ordinary SignalR without Orleans

Example prompts

  • “/managedcode-orleans-signalr”

Requirements

  • Compatibility (from SKILL.md): Requires a .NET application with compatible Orleans and ASP.NET Core SignalR packages; use aligned ManagedCode.Orleans.SignalR Client and Server versions.

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Choose combined or separate silo/endpoint hosts and align packages, clustering, partition options, and named storage.
  2. Configure authenticated connection, user, and group targeting.
  3. Keep publishing at an explicit domain-event boundary and decide whether bounded offline retention is sufficient.
  4. Exercise live delivery, reconnect replay, queue limits, heartbeat cleanup, and interrupted client invocations.
  5. Before upgrades, validate prior persisted payloads with the production serializer and choose an explicit compatibility or…

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires a .NET application with compatible Orleans and ASP.NET Core SignalR packages; use aligned ManagedCode.Orleans.SignalR Client and Server versions.

    From compatibility in the SKILL.md frontmatter.

Context cost

Managedcode Orleans Signalr loads about 1.9k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 579 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 579 words, ~1,887 tokens.

Download SKILL.mdSave it as .claude/skills/managedcode-orleans-signalr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
managedcode-orleans-signalr
description
Integrate ManagedCode.Orleans.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state. USE FOR: Orleans backplane setup, grain-to-hub publishing, reconnect, heartbeat, and client-invocation failures. DO NOT USE FOR: ordinary SignalR without Orleans or unrelated persistence. INVOKES: inspect configuration, implement the integration, and validate connected-client delivery.
compatibility
Requires a .NET application with compatible Orleans and ASP.NET Core SignalR packages; use aligned ManagedCode.Orleans.SignalR Client and Server versions.

ManagedCode.Orleans.SignalR

Trigger On

  • configuring an Orleans SignalR backplane or sending messages from grains
  • diagnosing connection, group, or user routing across hosts
  • upgrading offline delivery, heartbeat persistence, or client invocation handling

Install

For a host that runs both the silo and SignalR endpoint:

bash
dotnet add package ManagedCode.Orleans.SignalR.Server --version 10.3.0
dotnet add package ManagedCode.Orleans.SignalR.Client --version 10.3.0

For separate hosts, put Server on the silo and Client on the ASP.NET Core endpoint. Core supplies shared contracts transitively. Keep versions and partition options aligned across participants; preserve central package management when present.

Configure the Backplane

A combined local development host can use the memory provider:

csharp
using ManagedCode.Orleans.SignalR.Server.Extensions;
using Microsoft.AspNetCore.SignalR;

var builder = WebApplication.CreateBuilder(args);
builder.Host.UseOrleans(silo =>
{
    silo.UseLocalhostClustering();
    silo.ConfigureOrleansSignalR();
    silo.AddOrleansSignalRInMemoryStorage();
});
builder.Services.AddSignalR().AddOrleans(options =>
{
    options.ConnectionPartitionCount = 4;
    options.GroupPartitionCount = 4;
    options.KeepMessageInterval = TimeSpan.FromMinutes(5);
    options.MaxQueuedMessagesPerUser = 100;
});

var app = builder.Build();
app.MapHub<UpdatesHub>("/updates");
app.Run();

public sealed class UpdatesHub : Hub { }

Import only Server.Extensions for this combined host; a separate client-only endpoint uses Client.Extensions. Importing both makes AddOrleans ambiguous. Use authenticated hub endpoints and the application's existing cluster discovery in deployed environments. The memory provider does not survive silo restarts. When offline delivery must survive restarts, register a durable Orleans grain-storage provider under OrleansSignalROptions.OrleansSignalRStorage instead of the memory helper. Connection metadata, queued messages, heartbeat registrations, and invocation state use this named store.

Send and Receive Updates

Inject IHubContext<UpdatesHub> into the grain or application service that owns the event:

csharp
using Microsoft.AspNetCore.SignalR;

public sealed class UpdatePublisher(IHubContext<UpdatesHub> hub)
{
    public Task NotifyUserAsync(string userId, string eventId, string text) =>
        hub.Clients.User(userId).SendAsync("Updated", eventId, text);

    public Task NotifyGroupAsync(string group, string eventId, string text) =>
        hub.Clients.Group(group).SendAsync("Updated", eventId, text);
}

Register a receiver before starting the connection. This example uses the application's @microsoft/signalr client:

javascript
import { HubConnectionBuilder } from '@microsoft/signalr';

const connection = new HubConnectionBuilder()
  .withUrl('/updates')
  .withAutomaticReconnect()
  .build();

connection.on('Updated', (eventId, text) => {
  renderUpdate(eventId, text); // Application-owned rendering and deduplication.
});
await connection.start();

Derive userId and permitted group membership from authenticated application identity. Never treat a client-supplied user or group name as authorization. Keep domain state in the owning grain; the backplane transports notifications about that state.

Delivery and Upgrade Boundaries

  • 10.3.0 persists queued offline user messages with delivery IDs and expiry, removing them after acknowledgement. Successful dispatch or queue storage is not proof that the browser applied the update; use application event IDs and idempotent handlers when replay matters.
  • KeepMessageInterval bounds offline retention. MaxQueuedMessagesPerUser defaults to 100 and discards oldest entries when exceeded. Test expiry and overflow explicitly; offline queues are not an unlimited event log.
  • KeepEachConnectionAlive renews a bounded heartbeat lease. Disabling it relies on ordinary observer/activation lifecycle; it does not make disconnected observers immortal. Test clean disconnect and abrupt host loss independently.
  • Observer failure thresholds, grace-period buffering, and circuit-breaker options affect retries and cleanup. Set them from measured reconnect behavior and watch drop/failure metrics.
  • Internal persisted HubMessageState changed from a dictionary to a QueuedHubMessage list, and ISignalRInvocationGrain.WaitForCompletion now returns a cancellation-aware IAsyncEnumerable<CqrsStreamChunk<InvocationProgress, CompletionMessage>>. Applications using these lower-level contracts must validate serialization and mixed-version compatibility before rolling upgrades.
  • A storage write failure must remain observable. Test retry and reactivation with the actual configured serializer and storage provider; an in-memory-only test does not prove durable recovery.
mermaid
flowchart LR
  G[Grain or service] --> H[IHubContext]
  H --> R[Orleans connection, group, or user routing]
  R --> L[Live observer dispatch]
  R --> Q[Offline user queue in named grain storage]
  Q --> P[Reconnect and replay]
  P --> A[Acknowledge delivery ID]
  A --> D[Remove queued message]
  L --> C[SignalR client]
  P --> C
Show full SKILL.md (175 more words)Show less

Workflow

  1. Choose combined or separate silo/endpoint hosts and align packages, clustering, partition options, and named storage.
  2. Configure authenticated connection, user, and group targeting.
  3. Keep publishing at an explicit domain-event boundary and decide whether bounded offline retention is sufficient.
  4. Exercise live delivery, reconnect replay, queue limits, heartbeat cleanup, and interrupted client invocations.
  5. Before upgrades, validate prior persisted payloads with the production serializer and choose an explicit compatibility or maintenance-window strategy.

Deliver

  • configured backplane and named storage with a stated durability boundary
  • a working publisher and client receiver
  • evidence for the required live, offline, restart, and failure behavior

Validate

  • dotnet restore and dotnet build resolve the aligned package set
  • a real connected client receives a grain-originated message on another host
  • user/group isolation, reconnect, queue expiry/overflow, and heartbeat cleanup work
  • restart tests preserve queued messages only when durable storage is configured
  • cancellation and missing-client completion terminate predictably
  • tests keep unrelated cases parallel; isolate destructive restart tests by their owned cluster

Sources

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in catalog/Libraries/ManagedCode-Orleans-SignalR/skills/managedcode-orleans-signalr of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Managedcode Orleans Signalr next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managedcode Orleans Signalr compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managedcode Orleans Signalr this skillmanagedcode/dotnet-skills486—~1.9kAutomated safety check: PassMIT
ConnectComposioHQ/awesome-claude-skills77k3 repos~987Automated safety check: PassNone
Integration Connectivity Connected App Configureforcedotcom/sf-skills1.1k—~2.7kAutomated safety check: NotesApache-2.0
Integration Testingthedaviddias/Front-End-Checklist74k—~514Automated safety check: PassMIT
Integration Connectivity Generateforcedotcom/sf-skills1.1k—~2.2kAutomated safety check: PassApache-2.0
API Integrationsickn33/agentic-awesome-skills47k1 repos~1.3kAutomated safety check: PassMIT

Similar skills

  • Connect

    ComposioHQ/awesome-claude-skills

    Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~987 tokens
    Productivity & AutomationAuto-check passed
  • Salesforce Connected Apps and External Client Apps OAuth configuration with 120-point scoring.

    1.1k GitHub stars~2.7k tokensUpdated 4 days ago
    Backend & APIsAuto-check: notes
  • Integration Testing

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Write integration tests for key workflows.

    74k GitHub stars~514 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Salesforce integration architecture and runtime plumbing with 120-point scoring.

    1.1k GitHub stars~2.2k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • API Integration

    sickn33/agentic-awesome-skills

    Designs event-driven architectures, webhook systems, API chaining flows, ETL pipelines, and integration patterns between services.

    47k GitHub starsUsed in 1 repo~1.3k tokens
    Backend & APIsAuto-check passed
  • Integrations Lifecycle

    netdata/netdata

    Change or review the Netdata integrations pipeline, collector artifact consistency, metadata validation, generated docs/catalogs and source-versus-runtime delivery.

    81k GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo
  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Questions about Managedcode Orleans Signalr

What does Managedcode Orleans Signalr do?

Integrate ManagedCode.Orleans.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state. Managedcode Orleans Signalr is an agent skill from managedcode/dotnet-skills.SignalR for grain-driven SignalR delivery, connection and group routing, offline user queues, and restart-safe state.

When should I use Managedcode Orleans Signalr?

Managedcode Orleans Signalr fits situations like: : Orleans backplane setup; grain-to-hub publishing; client-invocation failures; : ordinary SignalR without Orleans.

How do I install Managedcode Orleans Signalr in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr -a claude-code`. Or copy the skill folder (catalog/Libraries/ManagedCode-Orleans-SignalR/skills/managedcode-orleans-signalr in managedcode/dotnet-skills) into .claude/skills/managedcode-orleans-signalr in your project. Claude Code loads it when a task matches its description.

How do I install Managedcode Orleans Signalr in Codex?

Run `npx skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr -a codex`. Or copy the skill folder (catalog/Libraries/ManagedCode-Orleans-SignalR/skills/managedcode-orleans-signalr in managedcode/dotnet-skills) into .agents/skills/managedcode-orleans-signalr in your project. Codex loads it when a task matches its description.

Can I use Managedcode Orleans Signalr in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managedcode-orleans-signalr, .gemini/skills/managedcode-orleans-signalr, .github/skills/managedcode-orleans-signalr and .opencode/skills/managedcode-orleans-signalr in your project.

What does Managedcode Orleans Signalr need to run?

Going by SKILL.md and its folder, Managedcode Orleans Signalr needs the command-line tools its instructions call (dotnet). Compatibility (from SKILL.md): Requires a .NET application with compatible Orleans and ASP.NET Core SignalR packages; use aligned ManagedCode.Orleans.SignalR Client and Server versions..

Does Managedcode Orleans Signalr access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Managedcode Orleans Signalr safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Managedcode Orleans Signalr use?

Managedcode Orleans Signalr is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managedcode Orleans Signalr use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Managedcode Orleans Signalr?

Skills that share tags, products or a category with Managedcode Orleans Signalr: Connect (ComposioHQ/awesome-claude-skills, 77k stars), Integration Connectivity Connected App Configure (forcedotcom/sf-skills, 1.1k stars), Integration Testing (thedaviddias/Front-End-Checklist, 74k stars) and Integration Connectivity Generate (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managedcode Orleans Signalr?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.