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 fil
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill95%
Checks it passed that the model alone missed
The response requires documenting how Orleans state changes or events map into SignalR push messages.
The response states that developers should identify which grain events or workflows need to be broadcast to connected clients.
The response recommends confirming that the application genuinely requires both Orleans state orchestration and SignalR transport in the same flow.
3 fixed18 passed either way0 still failing1 broke
Pass-rate lift
+9 pp
Tokens
-14%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/19/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Before wiring up real-time handlers, what step should be taken regarding grain domain events?
What was checked, without and with the skill
Checked
Without skill
With skill
The response states that developers should identify which grain events or workflows need to be broadcast to connected clients.
Missed
Passed
case-19 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md35 linessingle file
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
Confirm the application genuinely needs both Orleans and SignalR in the same flow.
Identify which grain events or workflows should publish to connected clients.
Keep Orleans domain logic in grains and SignalR transport concerns in the integration boundary.
Document how user, group, or connection targeting is resolved.
Validate end-to-end message delivery from grain event to connected client.
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