Skills complexity-analyzer
📦

complexity-analyzer

Content revision r1 Safe ⚙️ External commands

Analyze Code Complexity

Complex code is hard to review, test, and maintain. This skill helps Claude, Codex, and Claude Code measure complexity metrics and produce focused refactoring guidance.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "complexity-analyzer" from https://skillstore.io/skills/curiouslearner-complexity-analyzer.md and its manifest at https://skillstore.io/api/skills/curiouslearner-complexity-analyzer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/curiouslearner-complexity-analyzer.md Signed manifest GET /api/skills/curiouslearner-complexity-analyzer/manifest Signed lockfile GET /api/skills/curiouslearner-complexity-analyzer/lockfile

Test it

Using "complexity-analyzer". Analyze a payment module with several long functions.

Expected outcome:

The report highlights processPayment as high complexity, explains the main branch and nesting issues, and recommends extracting validation, fee calculation, and error handling.

Using "complexity-analyzer". Review a pull request that changes service logic.

Expected outcome:

The review notes that average complexity stayed stable, but one new function exceeds the target threshold and needs more focused tests.

Using "complexity-analyzer". Assess a full source directory before planning maintenance work.

Expected outcome:

The summary ranks the most complex modules, separates urgent refactoring from monitoring items, and suggests practical next steps for each hotspot.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

The static findings are false positives caused by Markdown code fences and prose in SKILL.md. I found no evidence of command execution, system reconnaissance, prompt injection, or malicious intent in the reviewed skill instructions.

1
Files scanned
187
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (3)
SKILL.md:70-77 SKILL.md:77-81 SKILL.md:81-126
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/curiouslearner-complexity-analyzer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/curiouslearner-complexity-analyzer/security.svg)](https://skillstore.io/skills/curiouslearner-complexity-analyzer?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/curiouslearner-complexity-analyzer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/curiouslearner-complexity-analyzer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/curiouslearner-complexity-analyzer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

CuriousLearner. (2026). complexity-analyzer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/curiouslearner-complexity-analyzer/audits/8

BibTeX citation

@techreport{curiouslearner-curiouslearner-complexity-analyzer-2026, author = {CuriousLearner}, title = {complexity-analyzer security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/curiouslearner-complexity-analyzer/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "complexity-analyzer security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "CuriousLearner" date-released: "2026-07-06" url: "https://skillstore.io/skills/curiouslearner-complexity-analyzer/audits/8" identifiers: - type: other value: "skillstore:curiouslearner-complexity-analyzer:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance

What You Can Build

Prioritize Refactoring Work

Identify the highest complexity functions before a cleanup sprint.

Review Pull Request Risk

Check whether changed files add complex control flow or long functions.

Track Maintainability Trends

Compare complexity scores across modules to guide maintenance planning.

Try These Prompts

Analyze One File 
Use complexity-analyzer on this file. Report the main complexity scores, the most complex functions, and the top refactoring recommendation.
Scan A Source Directory 
Use complexity-analyzer on src/. Summarize average complexity, list the ten highest-risk functions, and group recommendations by priority.
Compare Before And After 
Use complexity-analyzer to compare this branch with the previous version. Show which functions improved, worsened, or still exceed the target threshold.
Plan A Refactoring Roadmap 
Use complexity-analyzer across the project. Create a refactoring roadmap based on cyclomatic complexity, nesting depth, function length, and maintainability impact.

Best Practices

  • Run the skill on focused directories so findings stay actionable.
  • Review high complexity results with recent change history and defect data.
  • Use the recommendations to split large refactors into small reviewable changes.

Avoid

  • Do not treat a single complexity score as proof that code is incorrect.
  • Do not refactor stable business logic without tests or product context.
  • Do not ignore moderate complexity that changes often or lacks coverage.

Frequently Asked Questions

Which complexity metrics does this skill discuss?
It covers cyclomatic complexity, cognitive complexity, Halstead metrics, maintainability index, nesting depth, and lines of code.
Can it analyze an entire project?
Yes, it can summarize project-level complexity when the relevant files are available in the workspace.
Does it make code changes automatically?
No. It provides analysis and recommendations, while the user decides which refactors to apply.
Can it compare complexity across versions?
Yes, it can compare available before-and-after code and explain where complexity changed.
Does it require a specific programming language?
No. The guidance covers several common languages, but exact metrics may depend on available language tools.
How should teams use the results?
Use the results to prioritize risky hotspots, plan tests, and choose smaller refactoring steps.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/CuriousLearner/devkit/tree/main/skills/complexity-analyzer

Ref

d11af420e07cd866fe39cfa937efef3223896c06

Maintenance freshness

7/18/2026

Usage

4 downloads · 185 views

File structure

📄 SKILL.md