Skip to content
Back to skills

Analyze Cooper538 Eshop Demo 2

ASecurity

Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsgobashsecurity

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill analyze-cooper538-eshop-demo-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze Cooper538 Eshop Demo 2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Analyze Cooper538 Eshop Demo 2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-analyze-cooper538-eshop-demo-2/badge)](https://www.skillsdirectory.com/skills/majiayu000-analyze-cooper538-eshop-demo-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: analyze
description: Run code analyzers (unused packages, code quality, security). Use when user wants to analyze the codebase or runs /analyze.
allowed-tools: Bash, Read
---

# 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`:

| Argument | Script |
|----------|--------|
| (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
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.