How do I install the Vibe Audit skill?

Run npx skillmds@latest add majiayu000/vibe-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vibe Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vibe Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vibe Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vibe Audit?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vibe Audit by majiayu000 — Agent Skill

Name: Vibe Audit
Rating: 4.2 (5 reviews)
Author: majiayu000

Vibe Audit

Brutal Vibe Audit for engineering quality. Auto-activates on: "code review", "technical audit", "engineering quality", "is this production ready", "vibe check", "slop check", "AI-generated code", "technical due diligence", "can we ship this", "quality assessment"

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Brutal Vibe Audit

When the user questions code quality, asks for technical reviews, or wants to distinguish real engineering from AI slop, apply the 20-metric engineering audit.

Auto-Trigger Patterns

"Code review" or "technical audit" requests
Questions about "production readiness"
"Vibe check" or "slop check" on code
Concerns about "AI-generated code" quality
Technical due diligence needs
Questions like "can we ship this?"
Architecture reviews
Security or performance concerns
Quality assessment requests

What This Skill Does

Scores engineering reality across 20 metrics (0-5 each, 100 total):

Section A: Architecture & Vibe (1-5)

Architectural Justification
Dependency Bloat
README vs Reality Gap
AI Hallucination Smell
Folder Structure Sanity

Section B: Core Engineering (6-10) 6. Error Handling Strategy 7. Concurrency Model 8. Data Structures & Algorithms 9. Memory Management 10. Type Safety & Contracts

Section C: Performance & Scale (11-14) 11. Critical Path Latency 12. Backpressure & Limits 13. State Management 14. Network Efficiency

Section D: Security & Robustness (15-17) 15. Input Validation & Trust 16. Secrets & Supply Chain 17. Observability

Section E: QA & Operations (18-20) 18. Test Reality 19. CI/CD & Reproducibility 20. Bus Factor & Maintainability

Verdict Bands

0-40: VIBE CODING SCRAP - Rewrite
41-60: AI/JUNIOR PROTOTYPE - 70% rewrite
61-75: TECHNICAL DEBT BOMB - Refactor before scaling
76-85: SOLID ENGINEERING - Ship with monitoring
86-95: PROFESSIONAL GRADE - Minor polish
96-100: UNICORN TIER - NASA level

When to Use

Pre-launch technical reviews
Code quality assessments
Technical due diligence (M&A, investment)
AI-generated code validation
Architecture decisions
Performance concerns
Security audits

Complementary Audits

Jobs Audit: If UX/design also needs review
Carlin Audit: If marketing claims need verification
Multi-Audit: For comprehensive product analysis

Invoke

Use /vibe-audit [codebase path] for explicit invocation.

---name: vibe-auditdescription: Brutal Vibe Audit for engineering quality. Auto-activates on: "code review", "technical audit", "engineering quality", "is this production ready", "vibe check", "slop check", "AI-generated code", "technical due diligence", "can we ship this", "quality assessment"--- # Brutal Vibe Audit When the user questions code quality, asks for technical reviews, or wants to distinguish real engineering from AI slop, apply the 20-metric engineering audit. ## Auto-Trigger Patterns - "Code review" or "technical audit" requests - Questions about "production readiness" - "Vibe check" or "slop check" on code - Concerns about "AI-generated code" quality - Technical due diligence needs - Questions like "can we ship this?" - Architecture reviews - Security or performance concerns - Quality assessment requests ## What This Skill Does Scores engineering reality across 20 metrics (0-5 each, 100 total): **Section A: Architecture & Vibe (1-5)** 1. Architectural Justification 2. Dependency Bloat 3. README vs Reality Gap 4. AI Hallucination Smell 5. Folder Structure Sanity **Section B: Core Engineering (6-10)** 6. Error Handling Strategy 7. Concurrency Model 8. Data Structures & Algorithms 9. Memory Management 10. Type Safety & Contracts **Section C: Performance & Scale (11-14)** 11. Critical Path Latency 12. Backpressure & Limits 13. State Management 14. Network Efficiency **Section D: Security & Robustness (15-17)** 15. Input Validation & Trust 16. Secrets & Supply Chain 17. Observability **Section E: QA & Operations (18-20)** 18. Test Reality 19. CI/CD & Reproducibility 20. Bus Factor & Maintainability ## Verdict Bands - **0-40:** VIBE CODING SCRAP - Rewrite - **41-60:** AI/JUNIOR PROTOTYPE - 70% rewrite - **61-75:** TECHNICAL DEBT BOMB - Refactor before scaling - **76-85:** SOLID ENGINEERING - Ship with monitoring - **86-95:** PROFESSIONAL GRADE - Minor polish - **96-100:** UNICORN TIER - NASA level ## When to Use - Pre-launch technical reviews - Code quality assessments - Technical due diligence (M&A, investment) - AI-generated code validation - Architecture decisions - Performance concerns - Security audits ## Complementary Audits - **Jobs Audit**: If UX/design also needs review - **Carlin Audit**: If marketing claims need verification - **Multi-Audit**: For comprehensive product analysis ## Invoke Use `/vibe-audit [codebase path]` for explicit invocation.

Frequently asked questions