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 Code Analysis

by managedcode in managedcode/Storage

Use the free built-in .NET SDK analyzers and analysis levels.

MITAuto-check passedAgent Workflows

Install Mcaf Dotnet Code Analysis

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

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

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

At a glance

Use the free built-in .NET SDK analyzers and analysis levels.

  • 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 first-party code 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 Code Analysis is an agent skill from managedcode/Storage. Use the free built-in .NET SDK analyzers and analysis levels. Use when a .NET repo needs first-party code analysis, EnableNETAnalyzers, AnalysisLevel, or warning policy wired into build and CI.

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

It sits in Agent Workflows. 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 first-party code analysis
  • EnableNETAnalyzers
  • Warning policy wired into build and CI

Example prompts

  • “/mcaf-dotnet-code-analysis”

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 Code Analysis loads about 1.1k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 512 words of instructions outside code blocks.

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

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). 512 words, ~1,076 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-dotnet-code-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
mcaf-dotnet-code-analysis
description
Use the free built-in .NET SDK analyzers and analysis levels. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning policy wired into build and CI.
compatibility
Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

MCAF: .NET Code Analysis

Trigger On

  • the repo wants first-party .NET analyzers
  • CI should fail on analyzer warnings
  • the team needs AnalysisLevel or AnalysisMode guidance

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

  • third-party analyzer selection by itself
  • formatting-only work

Inputs

  • the nearest AGENTS.md
  • project files or Directory.Build.props
  • current analyzer severity policy

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. Start with SDK analyzers before adding third-party packages.
  2. Enable or document:
    • EnableNETAnalyzers
    • AnalysisLevel
    • AnalysisMode
    • warning policy such as TreatWarningsAsErrors
  3. Keep per-rule severity in the repo-root .editorconfig.
  4. Use dotnet build as the analyzer execution gate in CI.
  5. Add third-party analyzers only for real gaps that first-party rules do not cover.

Bootstrap When Missing

If first-party .NET code analysis is requested but not configured yet:

  1. Detect current state:
    • dotnet --info
    • rg -n "EnableNETAnalyzers|AnalysisLevel|AnalysisMode|TreatWarningsAsErrors" -g '*.csproj' -g 'Directory.Build.*' .
  2. Treat SDK analyzers as built-in functionality, not as a separate third-party install path.
  3. Enable the needed properties in the solution's MSBuild config, typically in Directory.Build.props or the target project file:
    • EnableNETAnalyzers
    • AnalysisLevel
    • AnalysisMode when needed
    • warning policy such as TreatWarningsAsErrors
  4. Keep rule-level severity in the repo-root .editorconfig.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. If the repo intentionally defers analyzer policy to another documented build layer, return status: not_applicable.

Deliver

  • first-party analyzer policy that is explicit and reviewable
  • build-time analyzer execution for CI

Validate

  • analyzer behavior is driven by repo config, not IDE defaults
  • CI can reproduce the same warnings and errors locally
Show full SKILL.md (198 more words)Show less

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/code-analysis.md first

Example Requests

  • "Turn on built-in .NET analyzers."
  • "Make analyzer warnings fail the build."
  • "Set the right AnalysisLevel for this 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-code-analysis of managedcode/Storage.

  • SKILL.md
  • references/code-analysis.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Dotnet Code Analysis 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 Code Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Dotnet Code Analysis this skillmanagedcode/Storage138—~1.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
Microsoft DocsMicrosoftDocs/mcp1.9k1 repos~723Automated safety check: PassCC-BY-4.0
Init My ProjectMCSLTeam/MCServerLauncher-Future121—~2.1kAutomated safety check: PassGPL-3.0
Grill Me DocsTheAngryByrd/IcedTasks150—~915Automated safety check: PassMIT

Similar skills

  • 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

  • Microsoft Docs

    MicrosoftDocs/mcp

    Official

    Understand Microsoft technologies by querying official documentation.

    1.9k GitHub starsUsed in 1 repo~723 tokens
    Agent WorkflowsAuto-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

  • Grill Me Docs

    TheAngryByrd/IcedTasks

    A skill your agent uses when creating, auditing, or updating project documentation.

    150 GitHub stars~915 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

  • 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

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 Code Analysis

What does Mcaf Dotnet Code Analysis do?

Use the free built-in .NET SDK analyzers and analysis levels. Mcaf Dotnet Code Analysis is an agent skill from managedcode/Storage.NET SDK analyzers and analysis levels.

When should I use Mcaf Dotnet Code Analysis?

Mcaf Dotnet Code Analysis fits situations like: A .NET repo needs first-party code analysis; enableNETAnalyzers; warning policy wired into build and CI.

How do I install Mcaf Dotnet Code Analysis in Claude Code?

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

How do I install Mcaf Dotnet Code Analysis in Codex?

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

Can I use Mcaf Dotnet Code Analysis 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-code-analysis -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-code-analysis, .gemini/skills/mcaf-dotnet-code-analysis, .github/skills/mcaf-dotnet-code-analysis and .opencode/skills/mcaf-dotnet-code-analysis in your project.

What does Mcaf Dotnet Code Analysis need to run?

Going by SKILL.md and its folder, Mcaf Dotnet Code Analysis 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 Code Analysis 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 Code Analysis 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 Code Analysis use?

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

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

What are the alternatives to Mcaf Dotnet Code Analysis?

Skills that share tags, products or a category with Mcaf Dotnet Code Analysis: Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars), Copilot Session Failure Analysis (dotnet/maui, 23k stars), Microsoft Docs (MicrosoftDocs/mcp, 1.9k stars) and Init My Project (MCSLTeam/MCServerLauncher-Future, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Dotnet Code Analysis?

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.