Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides specialized guidance for .NET backend engineers implementing distributed systems with Akka.NET. It focuses on the structural requirements of actor system setup, supervision strategies, and entity patterns.
The material covers the transition from local development to production, detailing how to orchestrate clusters using .NET Aspire and manage service discovery through Akka.Management across Kubernetes and Azure environments.
WHO IT'S FOR
.NET Backend Engineers
implementing distributed actor systems with Akka.NET
Cloud Architects
orchestrating Akka.NET clusters in production environments
QA / Test Automation Engineers
testing asynchronous actor interactions and persistence
Platform / DevEx Teams
standardizing local development for distributed .NET apps
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Follow the documented setup, then try a first task.
I’m using
Claude Code plugin
Installs: Complete dotnet-skills plugin, including its registered skills and specialized agents. · Claude Code
Before you start
Claude Code CLI terminal application
Platform: Claude Code CLI terminal app; the documented procedure is not for the VSCode extension.
Inside the Claude Code CLI session, add the repository as a marketplace and then install the dotnet-skills plugin. These are agent-session commands, not ordinary terminal shell commands.
Installs: Complete dotnet-skills Codex plugin. Skills are discovered from the plugin's skills directory; Claude Code-specific specialized agents are excluded. · Codex
Before you start
Platform: Codex CLI or IDE extension; specialized agents are not included in this plugin.
In a terminal, add the dotnet-skills marketplace and then install its plugin.
Ordering, backpressure, and shared-state requirements
Use the csharp-concurrency-patterns skill to review the concurrency logic in [SOURCE_FILE_OR_COMPONENT]. Identify one concrete hotspot, explain whether async/await, a concurrent collection, Channel<T>, actor isolation, or a short critical section is the simplest appropriate abstraction, and propose one small improvement. Account for [I/O_OR_CPU_WORK], [ORDERING_REQUIREMENTS], and [BACKPRESSURE_OR_STATE_REQUIREMENTS]. Do not modify files yet.
Map one Aspire dependency to explicit configuration
Uses aspire-configuration
Path to AppHost Program.cs
Path to the application project or Program.cs
One database or external service to configure
Use the aspire-configuration skill to inspect [APPHOST_PROGRAM_PATH] and [APPLICATION_PROJECT_PATH]. For the single dependency [DATABASE_OR_EXTERNAL_SERVICE], propose a small mapping from its AppHost resource outputs to explicit environment-variable configuration keys and the corresponding IOptions<T> or Configuration binding in the application. Note any Aspire client or service-discovery dependency that should remain out of application code. Do not edit the project yet.
Relevant test-project path and existing fixture conventions
Use the testcontainers-integration-tests skill to draft one focused xUnit integration test for [COMPONENT_OR_OPERATION] using a real [DATABASE_CACHE_OR_QUEUE] container instead of a mock. Include the fixture lifecycle, isolation approach, automatic cleanup, and randomized connection-port handling. Keep the result limited to this one test and identify any project details still needed before implementation.
Claude
Codex
Copilot
OpenCode