The setup · Claude Code half

Vlad's actual Claude Code, snapshotted.

Chapter 5 explains skills as a concept. Chapter 11 walks through building one. This page is the receipts — the 62 skills, 32 custom agents, and 12 plugins running live in Vlad's ~/.claude/ right now. Auto-generated from the actual filesystem; updates as the stack evolves.

The point isn't that you should install all of these. The point is that this is what an operator's library looks like at hour two thousand. Steal anything. Skip anything. Build your own.

62 skills · 32 custom agents · 12 plugins

Daily ops

Standups, vault hygiene, the morning + Friday loops.

10
dailyops

Morning standup across all projects — reviews yesterday's git activity, surfaces priorities and blockers.

health-pulseops

Check CI, deploy, and cron health across all active projects. Updates ~/.claude/health/heartbeat-state.json. Alerts via Telegram on state transitions.

learnops

Save a lesson or insight to persistent memory for future sessions. Use when something non-obvious should be remembered.

memory-hygieneops

Check MEMORY.md health — detect bloat, find stale memories, suggest consolidation. Run biweekly or after sprint bursts.

retroops

End-of-session retrospective — reviews what happened, extracts lessons, saves insights to memory for future sessions.

sprint-kickoffops

Break down a sprint goal into tasks with estimates

telegram-reportops

Send a formatted report or message to a Telegram chat using the Telegram MCP plugin.

vault-auditops

Audit the Obsidian vault — find orphan notes, broken links, empty notes, duplicate titles, and tag inventory.

vault-noteops

Create a structured Obsidian note from current work context — proper frontmatter, tags, and wikilinks to existing notes.

weeklyops

Weekly review across all projects — git activity summary, metrics, memory cleanup, and next-week planning.

Code review + QA

Audits, security passes, bug hunts, debugging.

14
auditreview

No description in frontmatter.

bughunterreview

Inspect a scope (file, module, or full repo) and identify likely bugs — returns concrete findings with file paths, severity, and fix suggestions

debug-swarmreview

Investigate a bug with multiple competing hypotheses

debugging-guidereview

Systematic debugging methodology — reproduce, isolate, hypothesize, fix, verify. Reference guide for bug investigation.

gstack-carefulreview

Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode". (gs…

gstack-qareview

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does t…

gstack-reviewreview

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)

hardenreview

Audit and harden Supabase edge functions — CORS lockdown, JWT auth, secret cleanup, rate limiting

perf-checkreview

Performance audit — finds N+1 queries, missing indexes, blocking operations, memory issues, and pagination gaps.

review-and-fixreview

Implement a change with parallel code review and testing

security-auditreview

Run a 4-agent security audit on any codebase — client exposure, auth, secrets, injection

security-reviewreview

Security audit of a file, module, or full codebase — OWASP Top 10, auth issues, injection, secret exposure, and access control gaps

tdd-workflowreview

Test-driven development methodology — red-green-refactor cycle, test patterns, and TDD best practices for any project.

ultrareviewreview

Deep code review of a PR, file, or module — architecture, correctness, performance, security, and test coverage in one pass

Build + ship

Scaffolding, deploys, env flips, framework-specific muscle.

19
api-designbuild

Design REST API endpoints from requirements — generates route table, DTOs, response schemas, and auth requirements.

apps-script-clasp-pushbuild

Push a local .gs source file to a Google Apps Script project and bump an existing deployment to the new version — no Apps Script editor UI needed. Handles one-time clasp install, OAuth login, Apps Script API enablement, cloning, push, and deployment-by-ID update. Use when you need a local Apps Script code change live on a deployed webhook URL, or when som…

build-featurebuild

Build a feature with parallel agents for backend, tests, and API layer

deploy-checkbuild

Run pre-deployment validation checks

device-logsbuild

No description in frontmatter.

diagnose-iapbuild

No description in frontmatter.

git-shipbuild

Commit all changes with a smart message, push to remote, and optionally create a PR — all in one command.

google-apps-script-debugbuild

Diagnose Google Apps Script web app webhooks that look broken from outside — covers the non-obvious 302 redirect, Deploy-vs-Manage-Deployments distinction, doPost-in-editor failure, getActiveSheet footgun, and status-field drift. Use when a Next.js/React frontend posts to a `script.google.com/macros/s/.../exec` URL and data isn't arriving, or when an Apps…

pitch-htmlbuild

Generate a single-file interactive HTML pitch artifact from a project's strategic docs (BRIEF + MONETIZATION + REVENUE-MODEL + BRAND-IDENTITY). Use when Vlad says "create me a beautiful artifact to send to friends" / "make me an HTML pitch" / "build interactive [slide deck / 1-pager]". Output: a self-contained .html file, email-attachable, no build step,…

preflight-iosbuild

No description in frontmatter.

quick-fixbuild

Rapid bug fix — finds root cause, implements minimal fix, and verifies with tests. From bug report to verified fix.

refactorbuild

Safe refactoring with test baseline before and after — ensures no regressions while improving code quality.

scaffoldbuild

Scaffold a new module or component for any framework — detects project type and generates all boilerplate following existing patterns.

ship-iosbuild

No description in frontmatter.

supabase-state-checkbuild

Report drift between your local Supabase migration files and the actual production DB state via Management API. Surfaces tables that exist but aren't in the tracker, migrations in the repo that aren't applied, and RLS gaps on user-data tables. Use before running `supabase db push` on a project where migrations are sometimes applied via dashboard.

vercel-env-flipbuild

Flip an existing Vercel production env var to a new value and redeploy so the change takes effect. Wraps the CLI 50.x dance of rm + add + redeploy that trips up non-interactive flows. Use when changing a feature flag, rotating a secret, or correcting a misconfigured env var in prod.

verify-file-durabilitybuild

Detect silent file reversion (bindfs mirrors, overlay mounts, sync agents, watchdog skills) by capturing a snapshot, waiting, then re-checking. Use after writing to any path where an upstream process might re-sync and overwrite the edit — Claude.ai Cowork /mnt/skills/, Codex worktrees, Dropbox/iCloud folders, network mounts.

verify-next-public-envbuild

Verify a NEXT_PUBLIC_* env var actually made it into the live production bundle. NEXT_PUBLIC_* vars bake at build time, so changing them on Vercel has zero effect until a redeploy rebuilds the client JS. This skill pulls Vercel env, checks for formatting issues (trailing whitespace, dupes), and greps the currently-deployed bundle to confirm the new value…

webhook-guidebuild

Webhook integration patterns — signature validation, queue processing, idempotency, and retry strategies for external service webhooks.

Strategy + research

Office hours, competitor intel, ultra-plans, monetization.

12
ahrefs-budget-checkstrategy

Preflight check on Ahrefs subscription-info-limits-and-usage before running bulk keyword queries. Prevents 'API units limit reached' errors mid-batch. Estimates cost per operation (keywords-explorer-overview ~50 units minimum, serp-overview variable, site-explorer-organic-keywords 25+). Warns when <100 units remain before a bulk call that needs 500+.

competitor-intelstrategy

Compare a domain against competitors using Ahrefs — keyword gaps, traffic comparison, backlink analysis, and content opportunities.

content-draftstrategy

Draft LinkedIn post, newsletter section, or blog article from recent work — turns technical insights into engaging content.

growth-scanstrategy

Pull Ahrefs metrics for any domain — traffic, keywords, backlinks, domain rating — and analyze growth trends.

gstack-office-hoursstrategy

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help…

mirror-patternstrategy

Prompt template for "mirror the structure of <existing file>" when spawning agents to create files matching an established pattern. Reliably produces consistent output across parallel agents where a free-form prompt would drift. Used for: scraper replication, test-file creation, schema migration, deploy-pattern replication.

monetize-ideastrategy

Generate monetization strategy for a product — revenue models, pricing tiers, financial projections, and go-to-market plan.

plan-onlystrategy

Enter plan-only mode — analyze and design without creating, editing, or modifying any files.

researchstrategy

Launch a research swarm to explore code from multiple angles

seo-checkstrategy

Quick SEO health check for a URL or domain — technical issues, keyword performance, and quick-win opportunities from Ahrefs.

swarm-strategic-planstrategy

Generate a complete 25-document strategic plan for a greenfield venture using a 5-wave × 4-agent swarm. Use when Vlad says "draft me plans for [new venture]" or "build me a complete strategy for X" and the project does not yet exist. Outputs: scaffolded folder + master BRIEF + 20 specialist docs + 8 brainstorming personas + cross-cutting synthesis.

ultraplanstrategy

Deep multi-step execution planning with goals, risks, implementation sequence, verification steps, and rollback — ported from claw-code

Portfolio-specific

Belkins/Folderly/Partner Connector/LinguaLive — Vlad's actual book of business.

4
lingualiveportfolio

LinguaLive project quick-reference — loads non-obvious architecture patterns, state model, payment flow, and gotchas at session start to save investigation time.

pcportfolio

Partner Connector dispatcher — routes to pc-api (NestJS backend) or pc-client (Nuxt 4 frontend) based on task context. Use /pc <describe your task>.

pc-apiportfolio

Partner Connector API quick-reference — NestJS backend patterns, module map, auth flow, HubSpot CRM loop, and gotchas.

pc-clientportfolio

Partner Connector Client quick-reference — Nuxt 4 SPA patterns, gateway layer, explicit imports requirement, auth flow, and gotchas.

Meta

Skills that build other skills, verify other agents, etc.

3
agent-wave-verifymeta

Between-wave audit for parallel agent orchestration. After 3-4 agents finish a wave, run file-count/LOC/commit-hash verification to confirm each agent delivered. Catches silent failures (agent returned OK but left no commit), race conditions (two agents wrote to same file), and scope drift (agent added files outside its assigned directory). Use after any…

preflight-external-depsmeta

Audit external data sources and API integrations for 2026 viability BEFORE writing code. Spawn parallel research agents to verify each dependency still works as documented, catch deprecations, rate-limit changes, and policy shifts. Use when starting a project with listed data feeds, external APIs, or third-party integrations. Saves 2-3 weeks of wasted sca…

teleportmeta

Jump to a file or symbol by name — searches filenames and content, returns up to 10 file matches and content matches with line numbers

How to read this list

Most operators discover skills by need. They explain a workflow to Claude three times, write a SKILL.md, drop it in ~/.claude/skills/, and never explain it again. That's how the list above grew. Every line in it started as a paragraph Vlad got tired of retyping.

The custom agents in ~/.claude/agents/ serve a different job — they're specialized subagents you spawn from a main session. code-reviewer reviews code. tdd-guide enforces test-first. pc-api-lead owns the Partner Connector backend. Pick read-only tools for the agents that should never edit; broader tool surfaces for the ones that ship.

Plugins are bundles — skills + agents + slash commands + MCP servers, distributed as one. Browse the marketplace inside Claude Code with /plugins.

Stay close

Edition 3 lands when this list says it does.

No course. No paywall. Operator playbooks weekly. 10K+ subscribers.