Software Audit Skill
Security and privacy audit for web and mobile apps built fast with AI assistance ("vibe coded"). Checks for OWASP Top 10 issues, leaked secrets, broken access control, sensitive data in logs, APIs that expose too much data, misconfigured Supabase/Firebase rules, insecure mobile storage, and risky dependencies. Use this skill whenever the user asks to audit, review, harden, pen-test, sanity-check, or "make safe" an app or repo, asks "is my app secure?", "is this safe to launch/ship?", "am I leaking anything?", or mentions OWASP, MASVS, RLS, exposed API keys, or logging sensitive data, rate limi
Install
npx skills add luigimorel/software-audit-skill --skill software-audit-skillgit clone --depth 1 https://github.com/luigimorel/software-audit-skill.git /tmp/software-audit-skill
mkdir -p ~/.claude/skills
cp -r /tmp/software-audit-skill/software-audit-skill ~/.claude/skills/software-audit-skillPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Vibe App Audit Audit web and mobile apps for the security and privacy mistakes that fast, AI-assisted development produces most often. The reader is probably a solo builder or small team who shipped quickly and cannot afford a 40-page pentest report. Be accurate, prioritized, and practical. ## Core rule: never trust the client Every price, user ID, role, subscription status, feature flag, and rate-limit counter must be validated or enforced on the server. Anything that exists only in the browser, the mobile bundle, or the request body is attacker-controlled. Most findings below are this one rule broken in a different place. ## Principles 1. **Find what actually gets people hurt first.** Leaked secrets, missing authorization, and over-exposed data matter far more than a missing header. Order findings by real-world impact, not by checklist order. 2. **Plain language.** Explain each issue as "what could happen to your users or your bill", then show the fix. Define jargon (IDOR, RLS, CORS) in one short phrase the first time it appears. 3. **Every finding gets a fix.** Include a copy-pasteable code or config change in the user's stack, not generic advice. 4. **Evidence over vibes.** Cite file paths and line numbers. Never report an issue you did not see in code, config, or a response. If you could not verify something, label it "Unverified" and say what to check.
Details
- Skill name
software-audit-skill- Repository
- luigimorel/software-audit-skill
- Path
software-audit-skill/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
FAQ
What does the Software Audit Skill skill do?
Security and privacy audit for web and mobile apps built fast with AI assistance ("vibe coded"). Checks for OWASP Top 10 issues, leaked secrets, broken access control, sensitive data in logs, APIs that expose too much data, misconfigured Supabase/Firebase rules, insecure mobile storage, and risky dependencies. Use this skill whenever the user asks to audit, review, harden, pen-test, sanity-check, or "make safe" an app or repo, asks "is my app secure?", "is this safe to launch/ship?", "am I leaking anything?", or mentions OWASP, MASVS, RLS, exposed API keys, or logging sensitive data, rate limi
How do I install the Software Audit Skill skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add luigimorel/software-audit-skill --skill software-audit-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Software Audit Skill popular?
It lives in luigimorel/software-audit-skill, which has 9 GitHub stars and 1 forks.
Related skills
Data Privacy
10RiskResponse/ciso-security-skills
Data Protection Officer (DPO) and Chief Privacy Officer (CPO) skill for privacy program governance, regulatory compliance, and privacy engineering. Use this skill whenever the user asks about privacy policy, data processing agreement, DPA, GDPR, CCPA, CPRA, LGPD, data protection, privacy program, DPO, chief privacy officer, DPIA, data subject rights, data mapping, ROPA, records of processing, international data transfer, SCCs, breach notification, privacy by design, consent management, cookie policy, privacy notice, data classification, ISO 27701, NIST Privacy Framework, privacy impact assessm
Isms P Audit
9basejb/isms-p-audit-skill
ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and
Docuseal CLI
9docusealco/docuseal-agent-skills
Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI - create templates from PDF/DOCX/HTML, send documents for signing, track submissions, and update submitters. Use when the user wants to run DocuSeal commands in the shell, scripts, or CI/CD pipelines. Always load this skill before running `docuseal` commands.
Eng Blast Radius
23jpoehnelt/skills
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
Docuseal Code
9docusealco/docuseal-agent-skills
DocuSeal development reference. Embed signing forms and template builder into web and mobile apps (JS/React/Vue/Angular, WebView, JWT, CSS theming). REST API with all endpoints, request/response schemas, code examples (cURL, CLI, Node.js, TypeScript, Python, Ruby, PHP, Go, C#, Java), and webhooks. Use when the user wants to integrate DocuSeal document signing or template management into their application.
Effect
23jpoehnelt/skills
Apply Effect v4 conventions for services, layers, tagged errors, boundary runners, resources, retries, deadlines, HTTP, and tests. Use when writing or reviewing TypeScript that imports effect, adds a service or error class, chooses where to run a program, bounds external I/O, or tests Effect code.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.