About security-audit
A skill for checking a specified file or folder for common security vulnerabilities. It returns task-specific findings with concrete action notes for executable audit requests.
Key features
- 01Checks code for common vulnerabilities
- 02Accepts a file or folder path
- 03Returns concrete action notes
Use cases
- 01Auditing a code file for security issues
- 02Reviewing a folder for common vulnerabilities
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/security-auditin Claude Code to confirm it loaded.
Details
From the project READMESecurity Audit
Purpose
Check code for common security vulnerabilities
Routing
- Use when: Use when the user asks to check code for common security vulnerabilities.
- Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Outputs: Outcome from Security Audit: task-specific result plus concrete action notes.
- Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
- Use the security-audit skill for this request.
- Help me with security audit.
- Use when the user asks to check code for common security vulnerabilities.
- Security Audit: provide an actionable result.
Negative
- Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
- Do not use security-audit for unrelated requests.
- This request is outside security audit scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| path | string | Yes | Path to file or folder to audit |
Runtime Prompt
- Current runtime prompt length: 497 characters.
- Runtime prompt is defined directly in
../security-audit.json.
Comments
Markdown supported