Skip to content
Back to skills

Managedcode Orleans Signalr

ASecurity

Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating SignalR delivery from Orleans grains; reviewing grain-to-hub push flows. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted ...

  • 485 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
development

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add managedcode/dotnet-skills --skill managedcode-orleans-signalr --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Managedcode Orleans Signalr?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Managedcode Orleans Signalr
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/managedcode-managedcode-orleans-signalr/badge)](https://www.skillsdirectory.com/skills/managedcode-managedcode-orleans-signalr)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: managedcode-orleans-signalr
description: "Use ManagedCode.Orleans.SignalR when a distributed .NET application needs Orleans-based coordination of SignalR real-time messaging, hub delivery, and grain-driven push flows. USE FOR: integrating ManagedCode.Orleans.SignalR into a real-time distributed application; coordinating SignalR delivery from Orleans grains; reviewing grain-to-hub push flows. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
compatibility: "Requires a .NET application that combines Orleans and SignalR through ManagedCode.Orleans.SignalR."
---

# ManagedCode.Orleans.SignalR

## Trigger On

- integrating `ManagedCode.Orleans.SignalR` into a real-time distributed application
- coordinating SignalR delivery from Orleans grains
- reviewing grain-to-hub push flows and connection routing
- documenting how Orleans state or events become SignalR messages

## Workflow

1. Confirm the application genuinely needs both Orleans and SignalR in the same flow.
2. Identify which grain events or workflows should publish to connected clients.
3. Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
4. Document how user, group, or connection targeting is resolved.
5. Validate end-to-end message delivery from grain event to connected client.

```mermaid
flowchart LR
  A["Orleans grain event"] --> B["ManagedCode.Orleans.SignalR integration"]
  B --> C["SignalR hub delivery"]
  C --> D["Connected client or group"]
```

## Deliver

- guidance on where the Orleans-to-SignalR bridge belongs
- separation between grain logic and transport concerns
- validation expectations for real-time distributed delivery

## Validate

- the integration is justified instead of mixing Orleans and SignalR casually
- grain logic stays focused on domain or orchestration concerns
- real-time delivery is verified end to end, not only through registration code

Files in this skill

  • SKILL.md2 KB
  • manifest.json158 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…