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 Analyzer Config

by managedcode in managedcode/Storage

Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

MITAuto-check passedAgent Workflows

Install Mcaf Dotnet Analyzer Config

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

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

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

At a glance

Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

  • 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 .NET repo needs rule severity
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls rg and dotnet

What it does

Mcaf Dotnet Analyzer Config is an agent skill from managedcode/Storage. Use a repo-root .editorconfig to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested .editorconfig files are allowed when they serve a clear subtree-specific purpose.

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/analyzer-config.md`). Compatibility notes: Requires a .NET SDK-based repository; respects the repo's AGENTS.md commands first.

It sits in Agent Workflows, covering Plain language and style rules. It works with .NET. 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 .NET repo needs rule severity
  • Code-style options
  • Analyzer ownership made explicit

Example prompts

  • “/mcaf-dotnet-analyzer-config”

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:

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

    From compatibility in the SKILL.md frontmatter.

Context cost

Mcaf Dotnet Analyzer Config loads about 1.2k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 570 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~79
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
~2.3k

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). 570 words, ~1,171 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-dotnet-analyzer-config/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
mcaf-dotnet-analyzer-config
description
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.
compatibility
Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

MCAF: .NET Analyzer Config

Trigger On

  • the repo needs a root .editorconfig
  • analyzer severity and style ownership are unclear
  • the team wants one source of truth for rule configuration

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

  • choosing analyzers with no config change
  • formatting-only execution with no config ownership question

Inputs

  • the nearest AGENTS.md
  • current .editorconfig
  • any Directory.Build.props overrides

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 one repo-root .editorconfig with root = true.
  2. Add nested .editorconfig files when a subtree has a clear scoped purpose, such as stricter rules, different generated-code handling, or a different policy for tests or legacy code.
  3. Keep severity in .editorconfig, not scattered through IDE settings.
  4. Write the file as real EditorConfig, not as a made-up .NET variant:
    • lowercase filename .editorconfig
    • root = true in the preamble
    • no inline comments
    • forward slashes in globs
  5. Keep bulk switches such as EnableNETAnalyzers in MSBuild files, not in .editorconfig.
  6. Treat .globalconfig as an exceptional case, not the normal repo setup.

Bootstrap When Missing

If analyzer configuration is requested but not structured yet:

  1. Detect current state:
    • rg --files -g '.editorconfig' -g '.globalconfig'
    • rg -n "EnableNETAnalyzers|AnalysisLevel|AnalysisMode" -g '*.csproj' -g 'Directory.Build.*' .
  2. Create or normalize one repo-root .editorconfig with root = true.
  3. Move rule severity into .editorconfig and keep bulk analyzer switches in project or MSBuild config.
  4. Add nested .editorconfig files only when a subtree really needs different scoped policy.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. If the repo intentionally uses another documented analyzer-config ownership model, return status: not_applicable.

Deliver

  • one explicit analyzer configuration ownership model
  • a root .editorconfig layout that agents can extend safely
Show full SKILL.md (231 more words)Show less

Validate

  • rule severity is reproducible in local and CI builds
  • IDE-only settings do not silently override repo policy
  • the default path is a root .editorconfig, not a surprise alternative

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/analyzer-config.md first

Example Requests

  • "Make .editorconfig the source of truth."
  • "Write a proper root .editorconfig for this repo."
  • "Fix conflicting analyzer severities in this .NET repo."

© 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-analyzer-config of managedcode/Storage.

  • SKILL.md
  • references/analyzer-config.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Dotnet Analyzer Config 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 Analyzer Config compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Dotnet Analyzer Config this skillmanagedcode/Storage138—~1.2kAutomated safety check: PassMIT
Analyzer Configmanagedcode/dotnet-skills486—~1.3kAutomated safety check: PassMIT
Meziantou Analyzermanagedcode/dotnet-skills486—~1.1kAutomated safety check: PassMIT
Stylecop Analyzersmanagedcode/dotnet-skills486—~1.2kAutomated safety check: PassMIT
Caveman ModeJuliusBrussee/caveman110k—~1kAutomated safety check: PassApache-2.0
Revit Extensions AuthoringNice3point/RevitExtensions168—~2.4kAutomated safety check: PassMIT

Similar skills

  • 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
    Agent WorkflowsAuto-check passed

  • Meziantou Analyzer

    managedcode/dotnet-skills

    Use the open-source free Meziantou.Analyzer package for design, usage, security, performance, and style rules in .NET.

    486 GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Stylecop Analyzers

    managedcode/dotnet-skills

    Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects.

    486 GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Caveman Mode

    JuliusBrussee/caveman

    Switches the agent to a terse reply style that gives the answer first, drops filler, and keeps every technical fact, command and number exact.

    110k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Revit Extensions Authoring

    Nice3point/RevitExtensions

    Add a fluent extension to Nice3point.Revit.Extensions with C 14 extension(Type){} blocks that wrap the raw Revit API for readability and chaining.

    168 GitHub stars~2.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Ad Level Up

    CorridorTech/PoseCap

    Curate the project's rule-set — add, refine, merge, or retire a convention.

    220 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check: notes

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 Analyzer Config

What does Mcaf Dotnet Analyzer Config do?

Use a repo-root .editorconfig to configure free .NET analyzer and style rules. Mcaf Dotnet Analyzer Config is an agent skill from managedcode/Storage.NET analyzer and style rules.

When should I use Mcaf Dotnet Analyzer Config?

Mcaf Dotnet Analyzer Config fits situations like: A .NET repo needs rule severity; code-style options; analyzer ownership made explicit.

How do I install Mcaf Dotnet Analyzer Config in Claude Code?

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

How do I install Mcaf Dotnet Analyzer Config in Codex?

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

Can I use Mcaf Dotnet Analyzer Config 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-analyzer-config -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-analyzer-config, .gemini/skills/mcaf-dotnet-analyzer-config, .github/skills/mcaf-dotnet-analyzer-config and .opencode/skills/mcaf-dotnet-analyzer-config in your project.

What does Mcaf Dotnet Analyzer Config need to run?

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

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

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

About 1.2k tokens (SKILL.md is roughly 4.7k 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 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Dotnet Analyzer Config?

Skills that share tags, products or a category with Mcaf Dotnet Analyzer Config: Analyzer Config (managedcode/dotnet-skills, 486 stars), Meziantou Analyzer (managedcode/dotnet-skills, 486 stars), Stylecop Analyzers (managedcode/dotnet-skills, 486 stars) and Caveman Mode (JuliusBrussee/caveman, 110k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Dotnet Analyzer Config?

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.