Agent skill

Managedcode Orleans Graph

by managedcode in managedcode/dotnet-skills

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics.

MITAuto-check passedDatabases

Install Managedcode Orleans Graph

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

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills managedcode-orleans-graph --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-Graph/skills/managedcode-orleans-graph .claude/skills/managedcode-orleans-graph && 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-graph
GitHub stars
486
Token cost
~1.6k tokens
SKILL.md length
463 words
Files
2
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics.

  • Works in 8 steps: Confirm the application needs grain-call… → Register Orleans.Graph filters in the… → Model the policy from source grain to… → …
  • : ManagedCode.Orleans.Graph integration
  • SKILL.md covers Trigger On, Install, Workflow and Practical Usage, plus 3 more sections
  • Calls dotnet

What it does

Managedcode Orleans Graph is an agent skill from managedcode/dotnet-skills. 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 build, test, lint…

Its SKILL.md is about 1.6k 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 .NET 10, Microsoft Orleans 10, and an Orleans silo or client that needs explicit grain-call policy enforcement or diagnostics.

It sits in Databases, covering Diagrams, Database schema design and Codebase knowledge for agents. It works with .NET and Mermaid. 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

  • : ManagedCode.Orleans.Graph integration
  • Allowed grain transitions
  • Orleans call filters
  • Live policy graphs

Example prompts

  • “/managedcode-orleans-graph”

Requirements

  • Compatibility (from SKILL.md): Requires .NET 10, Microsoft Orleans 10, and an Orleans silo or client that needs explicit grain-call policy enforcement or diagnostics.

Workflow steps

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

  1. Confirm the application needs grain-call policy enforcement or live-call diagnostics. If the task is generic graph data traversal, use…
  2. Register Orleans.Graph filters in the silo with AddOrleansGraph(...).
  3. Model the policy from source grain to target grain and method. Start with explicit allow rules for client entry points and grain-to-grain…
  4. Use AllowAll() observe mode only to discover traffic before enforcement. Keep a follow-up step to convert observed edges into reviewed…
  5. Register the client-side outgoing filter with clientBuilder.AddOrleansGraph() only when Orleans clients should participate in call-history…
  6. Use attributes when colocating policy with grain contracts is clearer than central fluent setup.
  7. Generate Mermaid diagrams and inspect policy edges for review artifacts.
  8. Validate with real Orleans runtime tests, including timer, reminder, hosted-service, and stateless-worker call origins when those are part…

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

    No URLs in SKILL.md.

    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 .NET 10, Microsoft Orleans 10, and an Orleans silo or client that needs explicit grain-call policy enforcement or diagnostics.

    From compatibility in the SKILL.md frontmatter.

Context cost

Managedcode Orleans Graph loads about 1.6k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 463 words of instructions outside code blocks.

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

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). 463 words, ~1,557 tokens.

Download SKILL.mdSave it as .claude/skills/managedcode-orleans-graph/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
managedcode-orleans-graph
description
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 build, test, lint, or validation commands when changes are made.
compatibility
Requires .NET 10, Microsoft Orleans 10, and an Orleans silo or client that needs explicit grain-call policy enforcement or diagnostics.

ManagedCode.Orleans.Graph

Trigger On

  • integrating ManagedCode.Orleans.Graph into an Orleans-based system
  • enforcing which grain interfaces may call other grain interfaces and methods
  • detecting unsafe runtime grain call cycles or intentional self-reentrancy
  • generating configured-policy or live-call Mermaid diagrams
  • running observe mode to discover real traffic before locking down a policy

Install

Current upstream release reviewed: v10.0.3.

bash
dotnet add package ManagedCode.Orleans.Graph

The upstream package targets the current .NET 10 / Orleans 10 stack. Do not add it to older Orleans applications without first checking target frameworks and Orleans package compatibility.

Workflow

  1. Confirm the application needs grain-call policy enforcement or live-call diagnostics. If the task is generic graph data traversal, use normal Orleans grain modeling instead.
  2. Register Orleans.Graph filters in the silo with AddOrleansGraph(...).
  3. Model the policy from source grain to target grain and method. Start with explicit allow rules for client entry points and grain-to-grain transitions.
  4. Use AllowAll() observe mode only to discover traffic before enforcement. Keep a follow-up step to convert observed edges into reviewed policy.
  5. Register the client-side outgoing filter with clientBuilder.AddOrleansGraph() only when Orleans clients should participate in call-history tracking.
  6. Use attributes when colocating policy with grain contracts is clearer than central fluent setup.
  7. Generate Mermaid diagrams and inspect policy edges for review artifacts.
  8. Validate with real Orleans runtime tests, including timer, reminder, hosted-service, and stateless-worker call origins when those are part of the topology.
mermaid
flowchart LR
  A["Orleans call"] --> B["Outgoing filter records source"]
  B --> C["Incoming filter checks transition policy"]
  C --> D{"Allowed?"}
  D -->|Yes| E["Target grain method runs"]
  D -->|No| F["Blocked before target code"]
  E --> G["Telemetry worker aggregates live edge"]
  G --> H["Telemetry grain / Mermaid graph"]

Practical Usage

Enforce a grain transition
csharp
using ManagedCode.Orleans.Graph.Extensions;

siloBuilder.AddOrleansGraph(graph =>
{
    graph.AllowClientCallGrain<IOrderGrain>();

    graph.AddGrainTransition<IOrderGrain, IPaymentGrain>()
        .Method(
            source => source.SubmitAsync(GraphParam.Any<Order>()),
            target => target.ChargeAsync(GraphParam.Any<Payment>()))
        .And();

    graph.AddGrain<IPaymentGrain>()
        .WithReentrancy();
});
Discover traffic before enforcement
csharp
siloBuilder.AddOrleansGraph(
    configureFilters: filters =>
    {
        filters.LiveGraphFlushPeriod = TimeSpan.FromSeconds(1);
    },
    configureGraph: graph =>
    {
        graph.AllowAll();
    });

clientBuilder.AddOrleansGraph();

After the app receives traffic, inspect the observed graph:

csharp
var telemetry = grainFactory.GetGrain<IOrleansGraphTelemetryGrain>(
    Constants.LiveGraphTelemetryGrainKey);

var observedGraph = await telemetry.GetObservedGraphAsync();
var mermaid = await telemetry.GenerateLiveMermaidDiagramAsync();
Use attributes on grain contracts
csharp
using ManagedCode.Orleans.Graph.Attributes;

[AllowClientCall]
[AllowGrainCall(
    typeof(IPaymentGrain),
    AllowAllMethods = false,
    SourceMethods = [nameof(IOrderGrain.SubmitAsync)],
    TargetMethods = [nameof(IPaymentGrain.ChargeAsync)])]
public interface IOrderGrain : IGrainWithStringKey
{
    Task SubmitAsync(Order order);
}

[AllowSelfReentrancy]
public interface IPaymentGrain : IGrainWithStringKey
{
    Task ChargeAsync(Payment payment);
}
Show full SKILL.md (212 more words)Show less

Options And Constraints

  • AllowAll() is an observe/discovery mode, not a finished production policy.
  • AllowClientCallGrain<T>() is required for client-originated entry points that should be allowed.
  • TrackOrleansGraphInternalCalls should stay off unless debugging Orleans.Graph itself.
  • RegisterGrainTimer callbacks use * as the source method because Orleans does not expose a grain interface method for that callback.
  • Reminder callbacks use the source grain identity and ReceiveReminder as the source method.
  • Runtime vertices use exact graph identities. The library records ORLEANS_GRAIN_CLIENT for client calls and UNKNOWN_CALLER when Orleans exposes no resolvable caller identity.
  • v10.0.3 includes fixes for reminders and timers; re-test those origins when upgrading.

Deliver

  • explicit Orleans.Graph registration for the silo and, when needed, clients
  • reviewed allow rules for client-to-grain and grain-to-grain transitions
  • observe-mode output or Mermaid diagrams when discovering real call paths
  • validation coverage for blocked transitions, allowed transitions, self-reentrancy, and runtime graph diagnostics

Validate

  • the app needs call policy enforcement, not generic graph traversal
  • every client entry point and grain transition required by the workflow is allowed intentionally
  • missing or unexpected transitions fail before target grain code runs
  • observe-mode findings are converted into reviewed policy before production enforcement
  • timer, reminder, hosted-service, stateless-worker, and client-originated calls are covered when they exist
  • Mermaid or edge snapshots are generated from runtime traffic or configured policy and reviewed for cycles

© 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-Graph/skills/managedcode-orleans-graph of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Managedcode Orleans Graph 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 Graph compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managedcode Orleans Graph this skillmanagedcode/dotnet-skills486—~1.6kAutomated safety check: PassMIT
Drizzle Erdhiroppy/mf-dashboard418—~627Automated safety check: PassMIT
Walkthroughalexanderop/walkthrough141—~3.4kAutomated safety check: NotesNone
Entity ModelAI-Unified-Process/marketplace140—~1.9kAutomated safety check: PassApache-2.0
Data Model CreationTencentCloudBase/CloudBase-AI-Toolkit1.1k1 repos~1.8kAutomated safety check: PassMIT
Data Model ExtractorEmeaAppGbb/spec2cloud100—~2.5kAutomated safety check: PassMIT

Similar skills

  • Drizzle Erd

    hiroppy/mf-dashboard

    A skill your agent uses when needing to visualize database schema, generate ERD diagrams from Drizzle ORM schemas, or understand table relationships

    418 GitHub stars~627 tokensUpdated today
    DatabasesAuto-check passed
  • Walkthrough

    alexanderop/walkthrough

    Generates a self-contained HTML file with an interactive, clickable Mermaid diagram (flowchart or ER diagram) that explains how a codebase feature, flow, architecture, or database schema works.

    141 GitHub stars~3.4k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes
  • Entity Model

    AI-Unified-Process/marketplace

    Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules.

    140 GitHub stars~1.9k tokensUpdated 2 days ago
    DatabasesAuto-check passed
  • Data Model Creation

    TencentCloudBase/CloudBase-AI-Toolkit

    [Deprecated] Optional advanced tool for complex data modeling.

    1.1k GitHub starsUsed in 1 repo~1.8k tokens
    DatabasesAuto-check passed
  • Data Model Extractor

    EmeaAppGbb/spec2cloud

    Extract database schemas, data models, and entity relationships from code.

    100 GitHub stars~2.5k tokensUpdated 5 mo ago
    DatabasesAuto-check passed
  • Dotnet Inspect Relationships

    richlander/dotnet-inspect

    Map how code connects — implementors and subclasses, extension methods, dependency graphs, reverse callers, and ecosystem integrations.

    151 GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-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

Works with

Questions about Managedcode Orleans Graph

What does Managedcode Orleans Graph do?

Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics. Managedcode Orleans Graph is an agent skill from managedcode/dotnet-skills.NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics.

When should I use Managedcode Orleans Graph?

Managedcode Orleans Graph fits situations like: : ManagedCode.Orleans.Graph integration; allowed grain transitions; orleans call filters; live policy graphs.

How do I install Managedcode Orleans Graph in Claude Code?

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

How do I install Managedcode Orleans Graph in Codex?

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

Can I use Managedcode Orleans Graph 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-graph -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-graph, .gemini/skills/managedcode-orleans-graph, .github/skills/managedcode-orleans-graph and .opencode/skills/managedcode-orleans-graph in your project.

What does Managedcode Orleans Graph need to run?

Going by SKILL.md and its folder, Managedcode Orleans Graph needs the command-line tools its instructions call (dotnet). Compatibility (from SKILL.md): Requires .NET 10, Microsoft Orleans 10, and an Orleans silo or client that needs explicit grain-call policy enforcement or diagnostics..

Does Managedcode Orleans Graph access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Managedcode Orleans Graph 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 Graph use?

Managedcode Orleans Graph 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 Graph use?

About 1.6k tokens (SKILL.md is roughly 6.2k 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 Graph?

Skills that share tags, products or a category with Managedcode Orleans Graph: Drizzle Erd (hiroppy/mf-dashboard, 418 stars), Walkthrough (alexanderop/walkthrough, 141 stars), Entity Model (AI-Unified-Process/marketplace, 140 stars) and Data Model Creation (TencentCloudBase/CloudBase-AI-Toolkit, 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 Graph?

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.