Agent skill

Mcaf Dotnet Stylecop Analyzers

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

MITAuto-check passedAgent Workflows

Install Mcaf Dotnet Stylecop Analyzers

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a claude-code

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

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers --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-stylecop-analyzers .claude/skills/mcaf-dotnet-stylecop-analyzers && 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/

Paste into Claude Code

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .claude/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-stylecop-analyzers .agents/skills/mcaf-dotnet-stylecop-analyzers && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .agents/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-stylecop-analyzers .cursor/skills/mcaf-dotnet-stylecop-analyzers && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .cursor/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/managedcode/Storage.git --path .codex/skills/mcaf-dotnet-stylecop-analyzers

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-stylecop-analyzers .gemini/skills/mcaf-dotnet-stylecop-analyzers && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .gemini/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-stylecop-analyzers .github/skills/mcaf-dotnet-stylecop-analyzers && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .github/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add managedcode/Storage --skill mcaf-dotnet-stylecop-analyzers -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install managedcode/Storage mcaf-dotnet-stylecop-analyzers --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/managedcode/Storage.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-stylecop-analyzers .opencode/skills/mcaf-dotnet-stylecop-analyzers && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mcaf-dotnet-stylecop-analyzers" agent skill from https://github.com/managedcode/Storage/tree/main/.codex/skills/mcaf-dotnet-stylecop-analyzers into .opencode/skills/mcaf-dotnet-stylecop-analyzers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcaf-dotnet-stylecop-analyzers", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mcaf-dotnet-stylecop-analyzers
GitHub stars: 138
Token cost: ~1k tokens
SKILL.md length: 489 words
Files: 2 (incl. references)
Skills in repo: 41
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

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 stricter style conventions than the SDK analyzers alone provide
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 Stylecop Analyzers is an agent skill from managedcode/Storage. Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.

Its SKILL.md is about 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/stylecop-analyzers.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 repo wants stricter style conventions than the SDK analyzers alone provide
Tasks that involve Plain language and style rules

Example prompts

“/mcaf-dotnet-stylecop-analyzers”

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.

Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
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 Stylecop Analyzers loads about 1k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 489 words of instructions outside code blocks.

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

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). 489 words, ~1,031 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-dotnet-stylecop-analyzers/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: mcaf-dotnet-stylecop-analyzers
description: Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.
compatibility: Requires a .NET SDK-based repository; respects the repo's `AGENTS.md` commands first.

MCAF: .NET StyleCopAnalyzers

Trigger On

the repo wants StyleCop.Analyzers
naming, layout, or documentation style needs stronger enforcement
the team needs stylecop.json 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

repos that intentionally rely only on SDK analyzers
repos where StyleCop overlaps too heavily with an existing style package and no consolidation is planned

Inputs

the nearest AGENTS.md
current .editorconfig
any existing stylecop.json

Quick Start

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

Workflow

Add StyleCop.Analyzers only if the repo wants its opinionated style rules.
Keep severity in the root .editorconfig.
Use stylecop.json only for StyleCop-specific behavioral options.
Prefer one checked-in stylecop.json per repo unless a project genuinely needs its own behavior.
Avoid rule duplication with SDK analyzers or other analyzer packs when possible.

Bootstrap When Missing

If StyleCop.Analyzers is not configured yet:

Detect current state:
- rg -n "StyleCop\\.Analyzers|stylecop\\.json" -g '*.csproj' -g 'stylecop.json' .
Add package to the intended scope:
- dotnet add PROJECT.csproj package StyleCop.Analyzers
Keep severity in root .editorconfig and use stylecop.json only for StyleCop-specific behavior.
Prevent overlap with existing analyzer packs by defining ownership.
Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
If the repo intentionally uses SDK analyzers only, return status: not_applicable.

Deliver

explicit StyleCop package setup
repo-owned StyleCop rule configuration
clear split between root .editorconfig and stylecop.json

Validate

StyleCop severity is versioned in repo config
stylecop.json is used only where it adds value

Show full SKILL.md (191 more words)Show less

Ralph Loop

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

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
Execute one planned step and produce a concrete delta.
Review the result and capture findings with actionable next fixes.
Apply fixes in small batches and rerun the relevant checks or review steps.
Update the plan after each iteration.
Repeat until outcomes are acceptable or only explicit exceptions remain.
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/stylecop-analyzers.md first

Example Requests

"Add StyleCop.Analyzers to this solution."
"Configure StyleCop without losing .editorconfig ownership."

Files

SKILL.md and 1 other file (references) in .codex/skills/mcaf-dotnet-stylecop-analyzers of managedcode/Storage.

SKILL.md
references/stylecop-analyzers.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Dotnet Stylecop Analyzers 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 Stylecop Analyzers compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Mcaf Dotnet Stylecop Analyzers this skillmanagedcode/Storage	138	—	~1k	Automated safety check: Pass	MIT	today
Analyzer Configmanagedcode/dotnet-skills	486	—	~1.3k	Automated safety check: Pass	MIT	today
Meziantou Analyzermanagedcode/dotnet-skills	486	—	~1.1k	Automated safety check: Pass	MIT	today
Stylecop Analyzersmanagedcode/dotnet-skills	486	—	~1.2k	Automated safety check: Pass	MIT	today
Caveman ModeJuliusBrussee/caveman	110k	—	~1k	Automated safety check: Pass	Apache-2.0	today
Revit Extensions AuthoringNice3point/RevitExtensions	168	—	~2.4k	Automated safety check: Pass	MIT	yesterday

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

Questions about Mcaf Dotnet Stylecop Analyzers

What does Mcaf Dotnet Stylecop Analyzers do?

Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Mcaf Dotnet Stylecop Analyzers is an agent skill from managedcode/Storage.NET projects.

When should I use Mcaf Dotnet Stylecop Analyzers?

Mcaf Dotnet Stylecop Analyzers fits situations like: A repo wants stricter style conventions than the SDK analyzers alone provide; tasks that involve Plain language and style rules.

How do I install Mcaf Dotnet Stylecop Analyzers in Claude Code?

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

How do I install Mcaf Dotnet Stylecop Analyzers in Codex?

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

Can I use Mcaf Dotnet Stylecop Analyzers 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-stylecop-analyzers -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-stylecop-analyzers, .gemini/skills/mcaf-dotnet-stylecop-analyzers, .github/skills/mcaf-dotnet-stylecop-analyzers and .opencode/skills/mcaf-dotnet-stylecop-analyzers in your project.

What does Mcaf Dotnet Stylecop Analyzers need to run?

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

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

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

What are the alternatives to Mcaf Dotnet Stylecop Analyzers?

Skills that share tags, products or a category with Mcaf Dotnet Stylecop Analyzers: 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 Stylecop Analyzers?

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.

Install Mcaf Dotnet Stylecop Analyzers

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

MCAF: .NET StyleCopAnalyzers

Trigger On

Value

Do Not Use For

Inputs

Quick Start

Workflow

Bootstrap When Missing

Deliver

Validate

Ralph Loop

Required Result Format

Load References

Example Requests

Files

Compare with similar skills

Similar skills

More from managedcode/Storage

Related

Questions about Mcaf Dotnet Stylecop Analyzers