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

Analyzer Config

by managedcode in managedcode/dotnet-skills

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

MITAuto-check passedAgent Workflows

Install Analyzer Config

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

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills 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/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/Analyzer-Config/skills/analyzer-config .claude/skills/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
analyzer-config
GitHub stars
486
Token cost
~1.3k tokens
SKILL.md length
569 words
Files
5 (incl. references)
Skills in repo
81
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

Analyzer Config is an agent skill from managedcode/dotnet-skills. 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. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit…

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

It sits in Agent Workflows, covering Codebase knowledge for agents and Plain language and style rules. It works with .NET. 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

  • A .NET repo needs rule severity
  • Code-style options
  • Analyzer ownership made explicit
  • : the repo needs a root .editorconfig

Example prompts

  • “/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 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:

    • 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

Analyzer Config loads about 1.3k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 158 tokens; SKILL.md has 569 words of instructions outside code blocks.

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

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). 569 words, ~1,279 tokens.

Download SKILL.mdSave it as .claude/skills/analyzer-config/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
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. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

.NET Analyzer Configuration

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

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 4 other files (references) in catalog/Tools/Analyzer-Config/skills/analyzer-config of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/analyzer-config.md
  • references/rules.md
  • references/template.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

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.

Analyzer Config compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyzer Config this skillmanagedcode/dotnet-skills486—~1.3kAutomated safety check: PassMIT
Mcaf Dotnet Analyzer Configmanagedcode/Storage138—~1.2kAutomated safety check: PassMIT
Mcaf Dotnet Meziantou Analyzermanagedcode/Storage138—~955Automated safety check: PassMIT
Mcaf Dotnet Stylecop Analyzersmanagedcode/Storage138—~1kAutomated safety check: PassMIT
Microsoft Skill CreatorMicrosoftDocs/mcp1.9k3 repos~2.1kAutomated safety check: PassCC-BY-4.0
Copilot Session Failure Analysisdotnet/maui23k—~3.4kAutomated safety check: PassMIT

Similar skills

  • Mcaf Dotnet Analyzer Config

    managedcode/Storage

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

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

  • Mcaf Dotnet Meziantou Analyzer

    managedcode/Storage

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

    138 GitHub stars~955 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Mcaf Dotnet Stylecop Analyzers

    managedcode/Storage

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

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

  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed

  • Copilot Session Failure Analysis

    dotnet/maui

    Official

    Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • ccc Semantic Code Search

    cocoindex-io/cocoindex-code

    Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.

    2.7k GitHub stars~938 tokensUpdated today
    Agent WorkflowsAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo

  • 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

  • Blazor

    managedcode/dotnet-skills

    Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Analyzer Config

What does Analyzer Config do?

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

When should I use Analyzer Config?

Analyzer Config fits situations like: A .NET repo needs rule severity; code-style options; analyzer ownership made explicit; : the repo needs a root .editorconfig.

How do I install Analyzer Config in Claude Code?

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

How do I install Analyzer Config in Codex?

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

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

What does Analyzer Config need to run?

Going by SKILL.md and its folder, 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 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 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 Analyzer Config use?

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

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

What are the alternatives to Analyzer Config?

Skills that share tags, products or a category with Analyzer Config: Mcaf Dotnet Analyzer Config (managedcode/Storage, 138 stars), Mcaf Dotnet Meziantou Analyzer (managedcode/Storage, 138 stars), Mcaf Dotnet Stylecop Analyzers (managedcode/Storage, 138 stars) and Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyzer Config?

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.