Agent skill

Complexity

by managedcode in managedcode/dotnet-skills

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code.

MITAuto-check passedAgent Workflows

Install Complexity

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

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

GitHub CLI
$ gh skill install managedcode/dotnet-skills complexity --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/Complexity/skills/complexity .claude/skills/complexity && 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
complexity
GitHub stars
486
Token cost
~1.2k tokens
SKILL.md length
530 words
Files
5 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • : the team wants to find overly complex methods
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls rg and dotnet

What it does

Complexity is an agent skill from managedcode/dotnet-skills. Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. USE FOR: the team wants to find overly complex methods; cyclomatic complexity thresholds are needed in CI; maintainability metrics or coupling thresholds need to be configured. DO NOT USE FOR: formatting-only work; generic analyzer setup with no complexity policy change. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation…

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/complexity.md` and `references/config.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. 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

  • : the team wants to find overly complex methods
  • Cyclomatic complexity thresholds are needed in CI
  • Maintainability metrics
  • Coupling thresholds need to be configured

Example prompts

  • “/complexity”

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

Complexity loads about 1.2k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 139 tokens; SKILL.md has 530 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
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
~4.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). 530 words, ~1,213 tokens.

Download SKILL.mdSave it as .claude/skills/complexity/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
complexity
description
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. USE FOR: the team wants to find overly complex methods; cyclomatic complexity thresholds are needed in CI; maintainability metrics or coupling thresholds need to be configured. DO NOT USE FOR: formatting-only work; generic analyzer setup with no complexity policy change. 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 Complexity Review

Trigger On

  • the team wants to find overly complex methods
  • cyclomatic complexity thresholds are needed in CI
  • maintainability metrics or coupling thresholds need to be configured

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

  • formatting-only work
  • generic analyzer setup with no complexity policy change

Inputs

  • the nearest AGENTS.md
  • current analyzer settings
  • current maintainability limits

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 the built-in maintainability analyzers before reaching for non-standard tooling.
  2. Use these rules deliberately:
    • CA1502 for excessive cyclomatic complexity in methods
    • CA1505 for low maintainability index
    • CA1506 for excessive class coupling
    • CA1501 when inheritance depth is also part of the design problem
  3. Keep rule severity in the root .editorconfig.
  4. Keep metric thresholds in a checked-in CodeMetricsConfig.txt added as AdditionalFiles.
  5. Pair analyzer findings with MCAF maintainability limits in AGENTS.md.

Bootstrap When Missing

If complexity thresholds are not configured yet:

  1. Detect current state:
    • rg -n "CA1501|CA1502|CA1505|CA1506|CodeMetricsConfig" -g '.editorconfig' -g '*.csproj' -g 'Directory.Build.*' .
    • rg --files -g 'CodeMetricsConfig.txt'
  2. Add severity entries for CA1502, CA1505, CA1506, and CA1501 in root .editorconfig.
  3. Add checked-in CodeMetricsConfig.txt and include it as AdditionalFiles in project props.
  4. Keep maintainability limits aligned with AGENTS.md.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. If policy relies only on AGENTS.md limits with no analyzer gate by design, return status: not_applicable.

Deliver

  • explicit complexity and maintainability policy
  • checked-in metric thresholds
  • CI commands that surface complex methods early

Validate

  • method-complexity checks are enabled where the repo wants them
  • thresholds are versioned in repo, not held in IDE memory
  • complexity findings map to real refactoring decisions
Show full SKILL.md (199 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

  • "Which analyzer finds complex methods in .NET?"
  • "Add a complexity gate for our C# code."
  • "Configure cyclomatic complexity thresholds."

© 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/Complexity/skills/complexity of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/complexity.md
  • references/config.md
  • references/metrics.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Complexity 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.

Complexity compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Complexity this skillmanagedcode/dotnet-skills486—~1.2kAutomated 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
ccc Semantic Code Searchcocoindex-io/cocoindex-code2.7k—~938Automated safety check: PassApache-2.0
Context Engineeringabashev/vfs-s31069 repos~2.6kAutomated safety check: NotesApache-2.0
Repomix Codebase Packeryamadashy/repomix29k—~1.3kAutomated safety check: NotesMIT

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
  • 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
  • Context Engineering

    abashev/vfs-s3

    Optimizes agent context setup. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 9 repos~2.6k tokens
    Agent WorkflowsAuto-check: notes
  • Repomix Codebase Packer

    yamadashy/repomix

    Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.

    29k GitHub stars~1.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check: notes
  • 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

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 Complexity

What does Complexity do?

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Complexity is an agent skill from managedcode/dotnet-skills.NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code.

When should I use Complexity?

Complexity fits situations like: : the team wants to find overly complex methods; cyclomatic complexity thresholds are needed in CI; maintainability metrics; coupling thresholds need to be configured.

How do I install Complexity in Claude Code?

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

How do I install Complexity in Codex?

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

Can I use Complexity 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 complexity -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/complexity, .gemini/skills/complexity, .github/skills/complexity and .opencode/skills/complexity in your project.

What does Complexity need to run?

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

Complexity 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 Complexity use?

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

What are the alternatives to Complexity?

Skills that share tags, products or a category with Complexity: Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars), Copilot Session Failure Analysis (dotnet/maui, 23k stars), ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars) and Context Engineering (abashev/vfs-s3, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Complexity?

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.