New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mcaf Dotnet Roslynator

by managedcode in managedcode/Storage

Use the open-source free Roslynator analyzer packages and optional CLI for .NET.

MITAuto-check passedAgent Workflows

Install Mcaf Dotnet Roslynator

skills CLI
$ npx skills add managedcode/Storage --skill mcaf-dotnet-roslynator -a claude-code

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

GitHub CLI
$ gh skill install managedcode/Storage mcaf-dotnet-roslynator --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/Storage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-roslynator .claude/skills/mcaf-dotnet-roslynator && 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
mcaf-dotnet-roslynator
GitHub stars
138
Token cost
~1.2k tokens
SKILL.md length
606 words
Files
2 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Use the open-source free Roslynator analyzer packages and optional CLI for .NET.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • A repo wants broad C static analysis
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls dotnet and rg

What it does

Mcaf Dotnet Roslynator is an agent skill from managedcode/Storage. Use the open-source free Roslynator analyzer packages and optional CLI for .NET. Use when a repo wants broad C static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/roslynator.md`). Compatibility notes: Requires a .NET SDK-based repository; respects the repo's AGENTS.md commands first.

It sits in Agent Workflows, covering Static analysis and SAST. It works with .NET and C#. The repository describes itself as: Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. The licence is MIT.

When your agent uses it

  • A repo wants broad C static analysis
  • Dead-code detection
  • Optional CLI checks
  • Extra rules beyond the SDK analyzers

Example prompts

  • “/mcaf-dotnet-roslynator”

Requirements

  • Compatibility (from SKILL.md): Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

Workflow steps

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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 5d32121. 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
    • rg

    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 a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

    From compatibility in the SKILL.md frontmatter.

Context cost

Mcaf Dotnet Roslynator loads about 1.2k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 606 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

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/Storage at commit 5d32121, republished under its MIT licence (© managedcode). 606 words, ~1,229 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-dotnet-roslynator/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
mcaf-dotnet-roslynator
description
Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.
compatibility
Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

MCAF: .NET Roslynator

Trigger On

  • the repo uses or wants Roslynator.Analyzers
  • the team wants Roslynator CLI or extra Roslyn-based rules
  • the user asks about C# linting, static analysis, code cleanup, or unused code

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • repos that already have overlapping analyzer packs with no consolidation plan
  • formatting-only work when the repo already standardized on dotnet format or CSharpier

Inputs

  • the nearest AGENTS.md
  • current analyzer packages
  • .editorconfig

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Prefer the NuGet analyzer packages for build-enforced checks.
  2. Use the CLI when the repo needs one of these flows explicitly:
    • analyze
    • fix
    • find-unused
    • format
  3. Build first when Roslynator needs compiled context.
  4. Configure rule severity and Roslynator behavior in .editorconfig.
  5. Avoid duplicating the same rules across multiple analyzer packs without a severity plan.
  6. Treat CLI auto-fix as a controlled change:
    • run it on a bounded target first
    • rebuild
    • rerun tests

Bootstrap When Missing

If Roslynator is not configured yet:

  1. Detect current state:
    • rg -n "Roslynator\\.Analyzers" -g '*.csproj' .
    • rg --files -g '.config/dotnet-tools.json'
    • dotnet tool list --local
    • dotnet tool list --global
    • command -v roslynator
  2. Choose the install path deliberately:
    • analyzer package: dotnet add PROJECT.csproj package Roslynator.Analyzers
    • optional CLI: dotnet new tool-manifest (if missing) and dotnet tool install roslynator.dotnet.cli
  3. Configure ownership in root .editorconfig so Roslynator does not fight SDK analyzers, StyleCop, or Meziantou.
  4. If the CLI is adopted, add exact commands in AGENTS.md and CI, such as:
    • dotnet tool run roslynator analyze SOLUTION_OR_PROJECT
    • dotnet tool run roslynator fix SOLUTION_OR_PROJECT
  5. Run dotnet build SOLUTION_OR_PROJECT and the selected Roslynator command, then return status: configured or status: improved.
  6. If the repo wants only the current analyzer baseline and no Roslynator-specific CLI workflow, return status: not_applicable.
Show full SKILL.md (254 more words)Show less

Deliver

  • Roslynator package or CLI setup that fits the repo
  • explicit ownership of rule severity
  • repeatable commands for analyze, fix, or unused-code workflows when the repo adopts them

Validate

  • Roslynator adds value beyond the current analyzer baseline
  • CI commands remain reviewable and reproducible
  • the repo is not confusing Roslynator CLI with the analyzer package itself

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • read references/roslynator.md first

Example Requests

  • "Add Roslynator analyzers."
  • "Use Roslynator CLI in CI."
  • "Find unused code with Roslynator."
  • "Auto-fix Roslynator issues in this solution."

© 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 (references) in .codex/skills/mcaf-dotnet-roslynator of managedcode/Storage.

  • SKILL.md
  • references/roslynator.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Dotnet Roslynator 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.

Mcaf Dotnet Roslynator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Dotnet Roslynator this skillmanagedcode/Storage138—~1.2kAutomated safety check: PassMIT
Roslynatormanagedcode/dotnet-skills486—~1.3kAutomated safety check: PassMIT
Find Untested Sourcesdotnet/skills5.6k1 repos~3.3kAutomated safety check: PassMIT
Init My ProjectMCSLTeam/MCServerLauncher-Future121—~2.1kAutomated safety check: PassGPL-3.0
MCP Csharpatherio-danp/cde-dotnetcc109—~1.2kAutomated safety check: NotesNone
Csharp MCP Server GeneratorILoveDotNet/ilovedotnet155—~560Automated safety check: PassCC0-1.0

Similar skills

  • Roslynator

    managedcode/dotnet-skills

    Use the open-source free Roslynator analyzer packages and optional CLI for .NET.

    486 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Find Untested Sources

    dotnet/skills

    Official

    Statically pairs source files with test files to list code that no test references, using Roslyn for C# or tree-sitter for many languages, with no build.

    5.6k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed

  • Init My Project

    MCSLTeam/MCServerLauncher-Future

    Bootstrap reusable project governance for a new or existing repo.

    121 GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • MCP Csharp

    atherio-danp/cde-dotnetcc

    Create, debug, test, and publish MCP (Model Context Protocol) servers in C using the official ModelContextProtocol SDK — tools/prompts/resources, stdio vs HTTP transport, MapMcp hosting.

    109 GitHub stars~1.2k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check: notes

  • Csharp MCP Server Generator

    ILoveDotNet/ilovedotnet

    Generate a complete MCP server project in C with tools, prompts, and proper configuration

    155 GitHub stars~560 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Dotnet MCP Builder

    boshi-xixixi/TraeSkill

    Build Model Context Protocol (MCP) servers in C/.NET against the current ModelContextProtocol 1.x NuGet packages.

    274 GitHub stars~1.7k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed

More from managedcode/Storage

All 41 skills in this repo

  • Mcaf Adr Writing

    managedcode/Storage

    Create or update an ADR under docs/ADR/ for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts.

    138 GitHub stars~951 tokensUpdated today
    Auto-check passed

  • Mcaf Agile Delivery

    managedcode/Storage

    Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback.

    138 GitHub stars~883 tokensUpdated today
    Auto-check passed

  • Mcaf Architecture Overview

    managedcode/Storage

    Create or update docs/Architecture.md as the global architecture map for a solution.

    138 GitHub stars~950 tokensUpdated today
    Auto-check passed

  • Mcaf CI CD

    managedcode/Storage

    Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring.

    138 GitHub stars~981 tokensUpdated today
    Auto-check passed

  • Mcaf Code Review

    managedcode/Storage

    Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene.

    138 GitHub stars~957 tokensUpdated today
    Auto-check passed

  • Mcaf Devex

    managedcode/Storage

    Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.

    138 GitHub stars~911 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mcaf Dotnet Roslynator

What does Mcaf Dotnet Roslynator do?

Use the open-source free Roslynator analyzer packages and optional CLI for .NET. Mcaf Dotnet Roslynator is an agent skill from managedcode/Storage.NET.

When should I use Mcaf Dotnet Roslynator?

Mcaf Dotnet Roslynator fits situations like: A repo wants broad C static analysis; dead-code detection; optional CLI checks; extra rules beyond the SDK analyzers.

How do I install Mcaf Dotnet Roslynator in Claude Code?

Run `npx skills add managedcode/Storage --skill mcaf-dotnet-roslynator -a claude-code`. Or copy the skill folder (.codex/skills/mcaf-dotnet-roslynator in managedcode/Storage) into .claude/skills/mcaf-dotnet-roslynator in your project. Claude Code loads it when a task matches its description.

How do I install Mcaf Dotnet Roslynator in Codex?

Run `npx skills add managedcode/Storage --skill mcaf-dotnet-roslynator -a codex`. Or copy the skill folder (.codex/skills/mcaf-dotnet-roslynator in managedcode/Storage) into .agents/skills/mcaf-dotnet-roslynator in your project. Codex loads it when a task matches its description.

Can I use Mcaf Dotnet Roslynator 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/Storage --skill mcaf-dotnet-roslynator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcaf-dotnet-roslynator, .gemini/skills/mcaf-dotnet-roslynator, .github/skills/mcaf-dotnet-roslynator and .opencode/skills/mcaf-dotnet-roslynator in your project.

What does Mcaf Dotnet Roslynator need to run?

Going by SKILL.md and its folder, Mcaf Dotnet Roslynator needs the command-line tools its instructions call (dotnet and rg). Compatibility (from SKILL.md): Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first..

Does Mcaf Dotnet Roslynator 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 Mcaf Dotnet Roslynator 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 Mcaf Dotnet Roslynator use?

Mcaf Dotnet Roslynator 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 Mcaf Dotnet Roslynator use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 708 tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Dotnet Roslynator?

Skills that share tags, products or a category with Mcaf Dotnet Roslynator: Roslynator (managedcode/dotnet-skills, 486 stars), Find Untested Sources (dotnet/skills, 5.6k stars), Init My Project (MCSLTeam/MCServerLauncher-Future, 121 stars) and MCP Csharp (atherio-danp/cde-dotnetcc, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Dotnet Roslynator?

managedcode (a GitHub organization) maintains it in managedcode/Storage, which has 138 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/Storage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.