Talos-class comprehensive code validation. Use for "validate code", "run vibe", "check quality", "security review", "architecture review", "accessibility audit", "complexity check", or any validation need. One skill to validate them all.
View on GitHubFebruary 1, 2026
Select agents to install to:
npx add-skill https://github.com/boshu2/agentops/blob/main/skills/vibe/SKILL.md -a claude-code --skill vibeInstallation paths:
.claude/skills/vibe/# Vibe Skill **YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.** Comprehensive code validation across 8 quality aspects. --- ## ⚠️ Claude Validation Limitation Warning **Claude is weak at systematic verification.** This was proven when Claude scored docs 9/10 "Ready for Implementation" while Codex found critical bugs at 6/10 on the same prompt. **For SPEC/DOCUMENT validation:** - Claude skims instead of traces - Claude pattern-matches instead of reasons - Claude is biased toward "looks good" **Mitigation required:** See "Spec/Document Validation Mode" section below. --- ## Execution Steps Given `/vibe [target]`: ### Step 1: Load Vibe-Coding Science **Read the vibe-coding reference:** ``` Tool: Read Parameters: file_path: skills/vibe/references/vibe-coding.md ``` This gives you: - Vibe Levels (L0-L5 trust calibration) - 5 Core Metrics and thresholds - 12 Failure Patterns to detect - Grade mapping ### Step 1a: Pre-flight Checks **Before proceeding, verify we have work to validate:** ```bash # Check if in git repo git rev-parse --git-dir 2>/dev/null || echo "NOT_GIT" ``` If NOT_GIT and no explicit path provided, STOP with error: > "Not in a git repository. Provide explicit file path: `/vibe path/to/files`" ### Step 2: Determine Target and Vibe Level **If target provided:** Use it directly. **Classify the vibe level based on task type:** | Task Type | Vibe Level | Depth | |-----------|:----------:|-------| | Format, lint | L5 | Skip | | Boilerplate | L4 | Quick | | CRUD, tests | L3 | Quick | | Features | L2 | Deep | | Architecture, security | L1 | Deep | **If no target:** Auto-detect from git state: ```bash # Check staged changes git diff --cached --name-only 2>/dev/null | head -10 # Check unstaged changes git diff --name-only 2>/dev/null | head -10 # Check recent commits git log --oneline -5 --since="24 hours ago" 2>/dev/null ``` Use the first non-empty result. If nothing found, ask user. ### Step 2a: Pre-flight Check - Files Exist