VernHole / K-Hole Vern - Be careful what you wish for. Random Vern personas do discovery on your idea. The more the merrier.

Historian Vern - Index a directory of input files into a structured concept map with source references.

Delivers high-quality, production-grade code using Opus-level reasoning — clean architecture, thorough error handling, tests, and documentation. Use when the user asks for elegant solutions, quality-first code, architectural excellence, or best-practice implementations.

Generate a new Vern persona using AI

Enterprise Vern - Needs 6 meetings and a committee first. Process, governance, compliance.

Runs a multi-LLM discovery pipeline (Default 5-step or Expanded 7-step) that chains analysis, refinement, chaos-checking, and consolidation across LLMs, then breaks results into actionable VTS tasks. Use when the user wants to explore, validate, or plan an idea through multiple AI perspectives.

Architect Vern - Systems design, scalable architecture, production-grade thinking. The blueprints before the build.

Academic Vern - Needs more research. Cites sources, considers prior art, wants peer review.

Initialize a new project with Ralph methodology by creating prd.json backlog, progress.md log, and tech-stack configuration. Use when starting a new project or setting up Ralph for the first time.

Build a comprehensive project backlog through multi-stage architectural analysis. Creates 6 functional groups and generates detailed tasks for each. Use when you need a large, well-organized backlog for complex projects.

Execute a single Ralph development cycle by selecting a failing task, implementing it, verifying with tests, and committing. Use when ready to implement the next feature from the backlog.

Write handler code in the zigts TypeScript subset for zigttp's serverless runtime. Covers the language spec, virtual modules, compile-time verification, sound mode type safety, and idiomatic FaaS patterns. Use for any .ts/.tsx/.js/.jsx files targeting zigttp.

Write idiomatic Zig code following the Zen of Zig philosophy. Use for systems programming with Zig (.zig files), covering manual memory management with allocators, error unions and explicit error handling, compile-time programming (comptime), data-oriented design, and the new async/Io model. Applies functional programming parallels (Result types, ADTs, explicit effects) for C-free systems development.

This skill should be used when the user asks to "detect workspaces", "find packages", "list monorepo packages", "workspace structure", "monorepo analysis", or needs to identify workspace/package boundaries in a codebase for focused security analysis.

This skill should be used when the user asks about "vulnerability chains", "chained exploits", "multi-step attacks", "SSRF to RCE", "pivot attacks", or needs to identify how vulnerabilities in different components can be combined during whitebox security review.

This skill should be used when the user asks about "vulnerability patterns", "how to find SQL injection", "XSS patterns", "command injection techniques", "OWASP vulnerabilities", "common web vulnerabilities", "exploitation patterns", or needs to understand how specific vulnerability classes work during whitebox security review.

This skill should be used when the user asks about "threat model", "STRIDE", "data flow diagram", "attack surface", "threat analysis", "security architecture", "component threats", "trust boundaries", "technology decomposition", or needs systematic threat identification during whitebox security review.

Drive a single finding through CPG verification and false-positive triage.

Guided first-run security audit: doctor, scope, threats, scan, verify, report.

Decide audit boundaries for large or monorepo targets and write audit-plan.md.

Diff-aware PR security review with verified findings and PR comment payload.

Bundle findings, reports, audit plan, and ledger into one evidence zip.

Detect ANY credential/secret flowing to ANY output sink. Use when asked about "credential leakage", "secret logging", "sensitive data exposure", "CWE-532", "password in logs", "token exposure", or security logging issues.

This skill should be used when the user asks about "security misconfiguration", "default credentials", "debug mode", "security headers", "exposed endpoints", "TLS configuration", or needs to find configuration-related vulnerabilities during whitebox security review.