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

Stylecop Analyzers

by managedcode in managedcode/dotnet-skills

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

MITAuto-check passedAgent Workflows

Install Stylecop Analyzers

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

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills 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/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Tools/StyleCop-Analyzers/skills/stylecop-analyzers .claude/skills/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/

Facts

Skill name
stylecop-analyzers
GitHub stars
486
Token cost
~1.2k tokens
SKILL.md length
488 words
Files
5 (incl. references)
Skills in repo
81
Repo updated
First seen
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

Stylecop Analyzers is an agent skill from managedcode/dotnet-skills. 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. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. 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. INVOKES…

Its SKILL.md is about 1.2k 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/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 Plain language and style rules and Codebase knowledge for agents. 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 repo wants stricter style conventions than the SDK analyzers alone provide
  • : the repo wants StyleCop.Analyzers
  • Documentation style needs stronger enforcement
  • The team needs stylecop.json guidance

Example prompts

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

  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:

    • 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

Stylecop Analyzers loads about 1.2k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 168 tokens; SKILL.md has 488 words of instructions outside code blocks.

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

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). 488 words, ~1,165 tokens.

Download SKILL.mdSave it as .claude/skills/stylecop-analyzers/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
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. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. 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. 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.

StyleCop Analyzers

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

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

Bootstrap When Missing

If StyleCop.Analyzers is not configured yet:

  1. Detect current state:
    • rg -n "StyleCop\\.Analyzers|stylecop\\.json" -g '*.csproj' -g 'stylecop.json' .
  2. Add package to the intended scope:
    • dotnet add PROJECT.csproj package StyleCop.Analyzers
  3. Keep severity in root .editorconfig and use stylecop.json only for StyleCop-specific behavior.
  4. Prevent overlap with existing analyzer packs by defining ownership.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. 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.

  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

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

© 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/StyleCop-Analyzers/skills/stylecop-analyzers of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/config.md
  • references/rules.md
  • references/stylecop-analyzers.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

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.

Stylecop Analyzers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stylecop Analyzers this skillmanagedcode/dotnet-skills486—~1.2kAutomated 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

  • 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
    Auto-check passed

  • 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

Works with

Categories

Questions about Stylecop Analyzers

What does Stylecop Analyzers do?

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

When should I use Stylecop Analyzers?

Stylecop Analyzers fits situations like: A repo wants stricter style conventions than the SDK analyzers alone provide; : the repo wants StyleCop.Analyzers; documentation style needs stronger enforcement; the team needs stylecop.json guidance.

How do I install Stylecop Analyzers in Claude Code?

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

How do I install Stylecop Analyzers in Codex?

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

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

What does Stylecop Analyzers need to run?

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

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 Stylecop Analyzers 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 5.1k tokens, read only when the agent opens those files.

What are the alternatives to Stylecop Analyzers?

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

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.