smithery.ai

complexity

Analyzes code for complexity issues. Use when code feels hard to understand, reviewing maintainability, or planning refactoring.

First seen Apr 16, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Grep, Glob

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,284 B
  • docs SUMMARY.md 146 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Complexity Analyzer

Complexity is the enemy. Good design reduces the complexity developers face.

Three Symptoms

  1. Change Amplification: Simple change requires modifications in many places

- Duplicated magic values, scattered configuration, tight coupling

  1. Cognitive Load: Too much knowledge needed to complete a task

- Too many parameters, deep nesting, complex conditionals, hidden state, non-obvious side effects

  1. Unknown Unknowns: Not obvious what to modify or what info is needed

- Missing docs on non-obvious behavior, implicit contracts, hidden dependencies, action-at-a-distance

Red Flags

  • Shallow modules (interface nearly as complex as implementation)
  • Information leakage (implementation details in interfaces)
  • Pass-through methods (just call another method)
  • Conjoined methods (must be called together)
  • Temporal decomposition (split by execution order, not information hiding)

Output

Complexity level (Low/Medium/High/Critical), findings with location/symptom/impact/suggestion, prioritized refactoring recommendations.