Back to search
my-claude-skills
SkillWorks with Claude CodeGitHub
the Claude skills I can't build without anymore
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/mar-antaya--my-claude-skills)HTML
<a href="/listings/mar-antaya--my-claude-skills"><img src="/api/listings/mar-antaya--my-claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
git clone https://github.com/YOUR_USERNAME/my-claude-skills.git
Then copy any skill folder into your Claude Code skills directory:
cp -r my-claude-skills/pr-review-expert ~/.claude/skills/
---
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 76 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # the Claude skills I can't build without anymore
- > 6 production-ready Claude Code skills I use daily as girl in AI/ML
- > Every single one of these has saved me hours on real projects.
- ---
- ## how to install
- ```bash
- git clone https://github.com/YOUR_USERNAME/my-claude-skills.git
- ```
- Then copy any skill folder into your Claude Code skills directory:
- ```bash
- cp -r my-claude-skills/pr-review-expert ~/.claude/skills/
- ```
- ---
- ## the 6 skills
- ### 1. pr-review-expert
- Paste your pull request diff and Claude does a full blast radius
- analysis, security scan, and coverage check before you ship anything.
- **why I use it**: stops me shipping broken code at midnight
- ---
- ### 2. skill-security-auditor
- Scans your code for command injection, data exfiltration, and prompt
- injection vulnerabilities. Zero dependencies — runs anywhere Python runs.
- **why I use it**: I run this before every deploy
- ---
- ### 3. dependency-auditor
- Scans every library in your project for license compliance, security
- risks, and tells you exactly what to upgrade and why.
- **why I use it**: catches the stuff you forget to check
- ---
- ### 4. tech-debt-tracker
- Scans your entire codebase, scores the debt, prioritizes what to fix
- first, and generates a trend dashboard so you can see your code
- getting cleaner over time.
- **why I use it**: makes tech debt visible instead of invisible
- ---
- ### 5. performance-profiler
- Profiles your Node, Python, or Go code, analyzes bundle size, and
- runs load testing so you find bottlenecks before your users do.
- **why I use it**: essential before any production release
- ---
- ### 6. ci-cd-pipeline-builder
- Detects your stack automatically and generates a complete GitHub
- Actions or GitLab CI config. No more copying YAML from Stack Overflow.
- **why I use it**: sets up my entire pipeline in minutes not hours
- ## let's build together
- If you build something with these drop it in my comments —
- I want to see what you're making.
- Follow along for more AI engineering tutorials →
- @mar_antaya
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.