Cc Skill Security Review
ListedHelps with security, code review as part of implementing security and authentication workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add sickn33/agentic-awesome-skills --skill cc-skill-security-review -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
sickn33
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
Declares what it does: failed
No SKILL.md was found in the skill's directory.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 5a4cdd9df8
- Scanned
- 0 files
- Copies in repo
- 3 — all of them scanned
About this skill
What it does
This skill helps ensure code adheres to security best practices and identifies potential vulnerabilities during development. It focuses on common security pitfalls, providing guidance and examples for secure coding techniques related to secrets management, input validation, and SQL injection prevention. The skill aims to improve the overall security posture of applications by proactively addressing these concerns.
When to use it
This skill is particularly useful in the following scenarios:
- Implementing authentication or authorization features.
- Handling user input or file uploads.
- Creating new API endpoints.
- Working with secrets and credentials.
- Implementing payment processing functionality.
- Storing or transmitting sensitive data.
- Integrating third-party APIs.
Key capabilities
- Secrets Management: Provides guidance on storing secrets in environment variables instead of hardcoding them, along with verification steps to ensure proper implementation.
- Input Validation: Demonstrates how to validate user input using schemas (e.g., Zod) and provides examples for file upload validation including size, type, and extension checks.
- SQL Injection Prevention: Illustrates the dangers of concatenating SQL queries and promotes the use of parameterized queries for safer database interactions.
Example prompts
Here are some example prompts you could give an AI agent with this skill:
- "Review this code snippet for potential secrets management vulnerabilities."
- "How can I validate user input to prevent injection attacks?"
- "Show me how to use parameterized queries in [programming language/framework]."
Tips & gotchas
- The skill provides specific examples using Zod and assumes a familiarity with similar schema validation libraries.
- It focuses on common vulnerabilities; more specialized security reviews may require additional tools or expertise.
- Always prioritize whitelisting allowed inputs rather than blacklisting potentially dangerous ones for input validation.