Automated summary
Reviews a given code scope for security flaws (authentication, input validation, injection, IDOR, data exposure) and proposes fixes ranked by severity.
Strengths
- Follows a concrete checklist: @PreAuthorize, @Valid, JPQL, IDOR, Redis TTL, Kafka access
- Each finding gets a severity, file/line location, exploit scenario and recommended fix
- Takes a free-form scope through $ARGUMENTS, so you can target a module or a diff
Limitations
- Heavily Spring/Java-oriented (annotations, JPQL, Kafka, Redis); less relevant for other stacks
- Static reading only: it does not run penetration tests or dynamic checks
- Output quality depends on the scope given and how deeply the files are read
Use it before a production release or during code review of a Spring module that exposes REST endpoints and handles user data.
Do not treat it as a replacement for a professional security audit, or run it on a non-Java codebase without adapting the checklist.
Security analysis
SafeThis is a purely analytical, read-only review skill: it instructs the agent to read files in a given scope, check them against a curated vulnerability checklist (authz, input validation, SQL injection, data exposure, mass assignment, IDOR, Kafka/Redis), and report severity/location/exploit/fix. There are no shell commands, no network calls, no file writes or deletions, no secret exfiltration, and no attempts to disable safety controls. The $ARGUMENTS placeholder only supplies the review scope. The only minor observation is that no allowed-tools are declared, so the agent's available toolset is implementation-dependent, but the instructions themselves create no execution risk.
No concerns found
How this analysis is madeExamples
Run a security review of src/main/java/com/acme/orders/ — check auth annotations, input validation and IDOR on every endpoint.취약점 검토: src/main/java/com/acme/repository 의 JPQL/native 쿼리에서 SQL injection 가능성을 확인해줘security review of the payment service before release: look for tokens or PII in logs and responses, and missing @PreAuthorize on controllers.name: security description: "보안 취약점을 검토하고 개선안을 제시합니다. '보안 검토', '취약점', '인증 확인', '권한 체크', 'IDOR', 'XSS', '보안 이슈', '@PreAuthorize', 'security review', 'vulnerability', 'auth check', 'permission', 'IDOR', 'injection' 등의 요청에 반응합니다."
Review the specified scope for security risks.
Scope: $ARGUMENTS
Instructions
- Read the specified files.
- Check for:
- Authentication/Authorization: endpoints missing
@PreAuthorizeor JWT validation; improper role checks - Input validation: missing
@Valid, unvalidated user input reaching the database or Kafka - SQL injection: JPQL/native queries with string concatenation
- Sensitive data exposure: tokens, passwords, or PII logged or returned in responses
- Mass assignment: DTOs mapped directly to entities without filtering
- IDOR: resource access not scoped to the authenticated user
- Kafka/Redis: unauthenticated topic access or sensitive data in cache without TTL
- Authentication/Authorization: endpoints missing
- For each finding, provide:
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- Location (file, line)
- Description and exploit scenario
- Recommended fix
Checklist
- [ ] All REST endpoints have appropriate
@PreAuthorize - [ ] All user inputs validated with
@Validor manual checks - [ ] No string concatenation in JPQL/native queries
- [ ] No tokens/passwords in logs or API responses
- [ ] Resource ownership verified before access (IDOR check)
- [ ] Redis cached sensitive data has TTL set
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/security-vulnerability-review-mrwakesi' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/security-vulnerability-review-mrwakesi/download' --output '.skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md.part' && mv '.skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md.part' '.skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md' && test -s '.skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/security' && cp -R '.skill-downloads/security-vulnerability-review-mrwakesi' '.claude/skills/security'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/security-vulnerability-review-mrwakesi'openskills read 'security-vulnerability-review-mrwakesi'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/security-vulnerability-review-mrwakesi/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
DeFi AMM Security
Security
Security checklist for Solidity AMM contracts, liquidity pools, and swap flows. Covers reentrancy, donation attacks, oracle manipulation, slippage, and integer math.
Semgrep Rule Creator
Security
Creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. Includes test-first methodology, taint mode support, and validation steps. Helps when building targeted static analysis detections.
Dev Toolbar Review Guide
Security
Safety rules for the dev toolbar, PostHog client, and feature flags. Use when reviewing changes to dev-tools and related files, covering environment guards, override cookies, and SSE stream safety.