Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit results; reviewing service boundaries that return. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit
SkillScore82Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 18 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill82%
Checks it passed that the model alone missed
returns Result<T>.Fail with a Problem object
uses FailNotFound when the order is not found
uses ConfigureCommunication on builder.Services
and 14 more in the full report
11 fixed7 passed either way4 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+1%
Agent turns
0%
Response time
-43%
Model gemini-3.6-flashMeasured 8/19/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
In Program.cs of an ASP.NET Core API application, what method must be called on `builder.Services` to ensure JSON converters and logging for communication results are registered properly?
What was checked, without and with the skill
Checked
Without skill
With skill
calls builder.Services.ConfigureCommunication()
Missed
Passed
case-16 · 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.md131 linessingle file
ManagedCode.Communication
Trigger On
integrating ManagedCode.Communication into services or APIs
replacing exception-driven result handling with explicit results
reviewing service boundaries that return success or failure payloads
documenting result-pattern usage across ASP.NET Core or application services
mapping application errors to RFC 7807 problem details, Minimal API results, SignalR filters, or Orleans call filters
Install
Use the package that matches the boundary. Current upstream release reviewed: v10.0.4.
Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics. USE FOR: ManagedCode.Orleans.Graph integration; allowed grain transitions; Orleans call filters; live policy graphs; reviewing Orleans call-cycle risk. DO NOT USE FOR: generic graph data modeling or traversal unrelated to Orleans calls. INVOKES: inspect the repository context, edit targeted files, and run relevant bu