analyze — community analyze, eshop-demo, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Code Review Agents needing advanced .NET microservices analysis capabilities. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

cooper538 cooper538
[0]
[0]
Updated: 2/13/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
54
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing advanced .NET microservices analysis capabilities. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

Core Value

Empowers agents to detect unused NuGet packages, code quality issues, and security vulnerabilities using dotnet-unused and Roslyn warnings, enhancing overall codebase security and maintainability.

Ideal Agent Persona

Perfect for Code Review Agents needing advanced .NET microservices analysis capabilities.

↓ Capabilities Granted for analyze

Detecting unused NuGet packages to optimize dependencies
Scanning for security vulnerabilities to ensure codebase integrity
Analyzing code quality to improve adherence to coding standards

! Prerequisites & Limits

  • .NET microservices architecture codebases only
  • Requires specific analyzer tools like dotnet-unused

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is analyze?

Perfect for Code Review Agents needing advanced .NET microservices analysis capabilities. Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

How do I install analyze?

Run the command: npx killer-skills add cooper538/eshop-demo/analyze. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for analyze?

Key use cases include: Detecting unused NuGet packages to optimize dependencies, Scanning for security vulnerabilities to ensure codebase integrity, Analyzing code quality to improve adherence to coding standards.

Which IDEs are compatible with analyze?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for analyze?

.NET microservices architecture codebases only. Requires specific analyzer tools like dotnet-unused.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add cooper538/eshop-demo/analyze. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use analyze immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

analyze

Install analyze, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Code Analyzer

Run analysis tools on the codebase.

Usage

/analyze              # Run all analyzers
/analyze packages     # Unused NuGet packages only
/analyze quality      # Code quality only
/analyze security     # Security vulnerabilities only

Arguments

  • $ARGUMENTS - Analyzer type to run
    • Empty or all - Run all analyzers
    • packages - Detect unused NuGet packages (dotnet-unused)
    • quality - Check code style and Roslyn warnings
    • security - Scan for known CVEs and deprecated packages

Process

Step 1: Ensure Tools Are Installed

Run dotnet tool restore if tools are not available.

Step 2: Execute Analyzer(s)

Based on $ARGUMENTS:

ArgumentScript
(empty) / all./tools/analyzers/run-all.sh
packages./tools/analyzers/unused-packages/analyze.sh
quality./tools/analyzers/code-quality/analyze.sh
security./tools/analyzers/security/analyze.sh

Step 3: Report Results

Summarize findings:

  • Number of issues found per category
  • Actionable recommendations

Output Format

=== Analysis Results ===

Unused Packages: X issues
  - ProjectName: PackageName

Code Quality: X warnings
  - File:Line - Warning description

Security: X vulnerabilities
  - PackageName - CVE-XXXX-XXXXX (severity)

Recommendations:
  1. Remove unused package X from project Y
  2. Fix warning Z in file W

Related Skills

Looking for an alternative to analyze or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer