Agent skills for Claude Code

Verify Single Step Instrumentation (SSI) is working end-to-end on Linux hosts — SSI automatically instruments applications for APM without…

Implement, test, audit, debug, and harden Verify Checkout hosted-deposit flows in merchant backends, websites, and apps.

Prove a change actually works before it counts as done.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session…

Generate a project-local verification skill that drives the app the way a user does — any language, framework, or platform.

Log past Spiderly's email-code auth wall to visually verify the running Angular admin panel — screenshot a page, click through a flow, or…

Verify a test-program change or conclusion through fresh deterministic evidence and iterative repair.

How to check that a Minecraft plugin actually works on a running Paper/Purpur server using VitaminMCP - connecting a session, reading…

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop.

Guide for optimizing SQL queries with EXPLAIN ANALYZE, index tuning, N+1 detection, covering indexes, and query plan analysis.

Decide which competitor to take on, and whether naming them helps or hurts, using battle rap matchup logic - the ladder, the crowd, the…

Execute automatic activation for all google vertex ai multimodal operations

Pre-Production validation — build a production-quality end-to-end build to confirm the full game loop is achievable before committing to…

Vertical Slice Architecture (VSA) for .NET applications — one of several supported architectures in dotnet-claude-kit.

Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or…

Author and inspect Pixar Universal Scene Description (USD) files: usdcat (print/convert between .usda ASCII / .usdc crate binary / .usdz…

Use after a brand direction and source of truth are confirmed to produce or maintain VI manuals, logo packages, brand assets, landscape…

Use when making CTO decisions — tech debt, team scaling, architecture, and DORA metrics.

Use when building or auditing frontend UI — components, design systems, or avoiding generic AI aesthetics.

Use when making any code change — trunk-based development, atomic commits, change sizing (~100 lines), and the commit-as-save-point pattern.

Use when you have a rough concept that needs divergent and convergent exploration.