What problem does it solve? Testing whether a Claude Code plugin correctly injects skills, fires hooks, and produces valid generated code requires real interactive sessions — claude --print and scripted runners do not trigger plugin hooks. This Skill provides the exact, proven procedure for launching, monitoring, and verifying plugin eval sessions end to end. ## Core Features & Use Cases - Interactive eval launch: Spawns WezTerm panes running real Claude Code sessions with the Vercel plugin installed, using exact copy-paste Bash commands and timestamped directory naming. - Injection monitoring: Checks skill claim directories and debug logs to count injected skills, hook firings, and PostToolUse validation catches. - Code verification: Greps generated projects for correct patterns — gateway vs direct provider usage, image model selection, withWorkflow config, and AI Elements installation. - Use Case: Run 12 benchmark scenarios (doc-qa-agent, multi-agent-research, compliance-auditor, etc.) across three complexity tiers, then write a coverage report and feed findings back into skill fixes before release. ## Quick Start Launch three benchmark eval sessions for the Vercel plugin using the tarot-deck, interior-designer, and superhero-origin prompts, then report which skills were injected in each session.