Back to catalog
Human reviewedDevelopment

Skill dossier

security-reviewer

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A read-only security review skill that scans code with SAST and secrets tools, reviews manually and writes severity-rated findings.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Maps attack surface and confirms written authorization before proceeding.
  • Suggests running semgrep, bandit, gitleaks, npm audit and trivy.
  • Requires manual review of auth, input handling and crypto because tools miss context.
  • Reports findings with location, CVSS severity, impact and remediation.

Limitations & scope

  • Frontmatter restricts tools to Read, Grep and Glob, so the scan commands may not run without more permissions.
  • Active testing requires authorization the skill cannot verify.
  • This review did not run any scanners.

Relevant for

  • Security engineers and reviewers
  • Teams adding SAST to pipelines
  • Developers auditing inherited code

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
7
Markdown files
7
scripts
0
references
6
Size
29.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/security-reviewer/references/infrastructure-security.mdReference5.8 KB
skills/security-reviewer/references/penetration-testing.mdReference5.8 KB
skills/security-reviewer/references/report-template.mdReference3.7 KB
skills/security-reviewer/references/sast-tools.mdReference2.4 KB
skills/security-reviewer/references/secret-scanning.mdReference2.9 KB
skills/security-reviewer/references/vulnerability-patterns.mdReference3.8 KB
skills/security-reviewer/SKILL.mdInstruction4.9 KB

SKILL.md frontmatter

{
  "name": "security-reviewer",
  "description": "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": "MIT",
  "allowed-tools": "Read Grep Glob",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "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"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Scope and authorize

    Map attack surface and critical paths and confirm written authorization and rules of engagement.

  2. 02
    Action

    Scan and review

    Run SAST, dependency and secrets tools, then do mandatory manual review.

  3. 03
    Decision

    Classify and limit testing

    Verify scope authorization, rate severity with CVSS and confirm with proof-of-concept only.

  4. 04
    Output

    Deliver report

    Provide executive summary, findings table, detailed findings and prioritized recommendations.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

40 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

22 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 22 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

2 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Inspect all security findings (40 findings)
High

Dynamic command execution is referenced

3 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Verify you have written authorization for the target scope before any active testing, and review scanner commands before running them.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/security-reviewer # .claude/skills/security-reviewer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/security-reviewer/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md for security-reviewer is discoverable at the destination, then ask Claude Code to use it on a small test task.

Prerequisites

  • Frontmatter restricts tools to Read, Grep and Glob, so the scan commands may not run without more permissions.
  • Active testing requires authorization the skill cannot verify.
  • This review did not run any scanners.

Example prompts

Representative task

Use the security-reviewer skill to audit the src/api directory of this repo. Scope to read-only static analysis, check authentication first, scan for hardcoded secrets, and produce a findings table with severity and remediation.

Inspect before use

Read the security-reviewer skill files at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/security-reviewer/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Strong scope and authorization guardrails, including no exploitation beyond proof of concept.
  • Structured report format with severity and remediation.

Considerations

  • Penetration-testing topics need real authorization.
  • Tool coverage depends on what is installed locally.
Research conclusion

A guardrail-conscious review workflow that is safe to try on code you own.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/security-reviewer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.