Security Audit
Review .NET services for safe defaults in input handling, authentication, authorization, secret management, logging exposure, and configuration hygiene. Use before release, during reviews, or when hardening an API or integration.
Install
npx skills add DIL8654/claude-code-dotnet-template --skill security-auditgit clone --depth 1 https://github.com/DIL8654/claude-code-dotnet-template.git /tmp/claude-code-dotnet-template
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-dotnet-template/.claude/skills/security-audit ~/.claude/skills/security-auditPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Audit Skill
Review a .NET service for practical security weaknesses and unsafe defaults.
## When to Use
- Before releasing an API or background service
- When adding authentication or authorization
- When reviewing secrets, configuration, or Azure integrations
- During dependency and logging review
---
## Quick Reference: Common Issues
| Issue | Symptom | Impact |
|-------|---------|--------|
| Missing validation | Raw external input trusted too early | Injection, malformed state, bad data |
| Weak authorization | Endpoint protected by auth but not policy | Over-broad access |
| Secret leakage | Keys or tokens in config files or logs | Credential exposure |
| Verbose production errors | Stack traces or internal messages returned | Attack surface disclosure |
| Unsafe defaults | Debug settings or permissive CORS in production | Avoidable exposure |
---
## Input Handling
- Validate request models
- Bound sizes, counts, and pagination
- Treat all external input as untrusted
- Normalize input only when the business meaning is clear
```csharp
// GOOD: Explicit constraints
public sealed record CreateUserRequest(
[property: Required, MaxLength(200)] string Name,
[property: EmailAddress] string Email);
```
---
## Authentication and Authorization
### Review Questions
- Is authentication configured correctly?
- Are endpoints protected by the correct policies?
- Is authorization checked at the right boundary?Details
- Skill name
security-audit- Repository
- DIL8654/claude-code-dotnet-template
- Path
.claude/skills/security-audit/SKILL.md- License
- GPL-3.0
- Repo updated
- 24 March 2026
FAQ
What does the Security Audit skill do?
Review .NET services for safe defaults in input handling, authentication, authorization, secret management, logging exposure, and configuration hygiene. Use before release, during reviews, or when hardening an API or integration.
How do I install the Security Audit skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add DIL8654/claude-code-dotnet-template --skill security-audit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Audit popular?
It lives in DIL8654/claude-code-dotnet-template, which has 9 GitHub stars and 5 forks.
Related skills
API Contract Review
9DIL8654/claude-code-dotnet-template
Review ASP.NET Core Web API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when the user asks to review an API, check endpoints, validate REST behavior, or before releasing contract changes.
Architecture Review
9DIL8654/claude-code-dotnet-template
Review Clean Architecture boundaries, dependency direction, layering decisions, and abstraction quality in .NET solutions. Use when evaluating project structure, new dependencies, service boundaries, or architectural drift.
Azure Integration
9DIL8654/claude-code-dotnet-template
Add Azure services to .NET applications with Managed Identity, typed options, infrastructure isolation, and production-safe configuration. Use when wiring Key Vault, App Configuration, Storage, Service Bus, or Azure Identity patterns.
Re Electron Skill
10iceman1001/awesome_rfid_claude_skills
Electron application reverse engineering — ASAR unpacking, webpack bundle analysis, auth/payment logic discovery, IPC channel mapping, and client-side authorization bypass analysis. Use when the user needs to: reverse engineer an Electron app (.deb/.dmg/.exe), analyze auth/subscription/license logic in Electron apps, map IPC channels between main and renderer processes, identify client-side enforcement vulnerabilities (CWE-602), or perform security audit of Electron-based desktop applications for CTF or research.
Security
9prangishviliAbe/agent-skills
Security engineering for web applications, APIs, and the AI agents and tools around them. Use to audit code or architecture, check whether a suspected flaw is exploitable, threat-model a feature, or harden sign-in, sessions, OAuth, access control and tenant isolation, injection, XSS, CSRF, SSRF, file uploads, cryptography and secrets, webhooks, race conditions, dependencies and CI/CD, WordPress, and prompt injection or tool permissions in LLM agents; also for "is this secure", leaked keys, dependency alerts, and incident triage. Traces real attack paths from attacker input to impact, reports e
API Exploit Prover
101ikeadragon/awesome-offsec-claude
Convert API vulnerability leads into confirmed impact or cleanly disproven outcomes with reproducible evidence.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.