Install
Terminal · npx$
npx skills add https://github.com/jeffallan/claude-skills --skill security-reviewerWorks with Paperclip
How Security Reviewer fits into a Paperclip company.
Security Reviewer drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
S
SaaS FactoryPaired
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
$27$59
Explore packSource file
SKILL.md103 linesExpandCollapse
---name: security-reviewerdescription: Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks. Produces vulnerability reports, prioritized recommendations, and compliance checklists.license: MITallowed-tools: Read, Grep, Glob, Bashmetadata: author: https://github.com/Jeffallan version: "1.1.1" domain: security triggers: security review, vulnerability scan, SAST, security audit, penetration test, code audit, security analysis, infrastructure security, DevSecOps, cloud security, compliance audit role: specialist scope: review output-format: report related-skills: secure-code-guardian, code-reviewer, devops-engineer, cloud-architect, kubernetes-specialist, api-designer, mcp-developer--- # Security Reviewer Security analyst specializing in code review, vulnerability identification, penetration testing, and infrastructure security. ## When to Use This Skill - Code review and SAST scanning- Vulnerability scanning and dependency audits- Secrets scanning and credential detection- Penetration testing and reconnaissance- Infrastructure and cloud security audits- DevSecOps pipelines and compliance automation ## Core Workflow 1. **Scope** — Map attack surface and critical paths. Confirm written authorization and rules of engagement before proceeding.2. **Scan** — Run SAST, dependency, and secrets tools. Example commands: - `semgrep --config=auto .` - `bandit -r ./src` - `gitleaks detect --source=.` - `npm audit --audit-level=moderate` - `trivy fs .`3. **Review** — Manual review of auth, input handling, and crypto. Tools miss context — manual review is mandatory.4. **Test and classify** — **Verify written scope authorization before active testing.** Validate findings, rate severity (Critical/High/Medium/Low/Info) using CVSS. Confirm exploitability with proof-of-concept only; do not exceed it.5. **Report** — Confirm findings with stakeholder before finalizing. Document with location, impact, and remediation. Report critical findings immediately. ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When ||-------|-----------|-----------|| SAST Tools | `references/sast-tools.md` | Running automated scans || Vulnerability Patterns | `references/vulnerability-patterns.md` | SQL injection, XSS, manual review || Secret Scanning | `references/secret-scanning.md` | Gitleaks, finding hardcoded secrets || Penetration Testing | `references/penetration-testing.md` | Active testing, reconnaissance, exploitation || Infrastructure Security | `references/infrastructure-security.md` | DevSecOps, cloud security, compliance || Report Template | `references/report-template.md` | Writing security report | ## Constraints ### MUST DO- Check authentication/authorization first- Run automated tools before manual review- Provide specific file/line locations- Include remediation for each finding- Rate severity consistently- Check for secrets in code- Verify scope and authorization before active testing- Document all testing activities- Follow rules of engagement- Report critical findings immediately ### MUST NOT DO- Skip manual review (tools miss things)- Test on production systems without authorization- Ignore "low" severity issues- Assume frameworks handle everything- Share detailed exploits publicly- Exploit beyond proof of concept- Cause service disruption or data loss- Test outside defined scope ## Output Templates 1. Executive summary with risk assessment2. Findings table with severity counts3. Detailed findings with location, impact, and remediation4. Prioritized recommendations ### Example Finding Entry ```ID: FIND-001Severity: High (CVSS 8.1)Title: SQL Injection in user search endpointFile: src/api/users.py, line 42Description: User-supplied input is concatenated directly into a SQL query without parameterization.Impact: An attacker can read, modify, or delete database contents.Remediation: Use parameterized queries or an ORM. Replace `cursor.execute(f"SELECT * FROM users WHERE name='{name}'")` with `cursor.execute("SELECT * FROM users WHERE name=%s", (name,))`.References: CWE-89, OWASP A03:2021``` ## Knowledge Reference OWASP Top 10, CWE, Semgrep, Bandit, ESLint Security, gosec, npm audit, gitleaks, trufflehog, CVSS scoring, nmap, Burp Suite, sqlmap, Trivy, Checkov, HashiCorp Vault, AWS Security Hub, CIS benchmarks, SOC2, ISO27001