plugins/proof-driven-verification/skills/verification-setup/SKILL.md
Prepare or diagnose the proof-driven verification environment. Use when asked to set up, install, upgrade, doctor, validate prerequisites, or troubleshoot Agent Browser, ffmpeg, Deepgram CLI, Remotion, Next.js DevTools MCP, or GTM Hub dev-server readiness for proof-driven verification.
npx skillsauth add ansarullahanasz360/cc-guide verification-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill before a verification run when the environment is unknown or when a tool fails.
Run:
node plugins/proof-driven-verification/scripts/doctor.mjs
Use JSON when another script or agent needs structured output:
node plugins/proof-driven-verification/scripts/doctor.mjs --json
If the user asks to install or upgrade prerequisites, run:
node plugins/proof-driven-verification/scripts/setup.mjs
Use dry-run first when changing a new machine:
node plugins/proof-driven-verification/scripts/setup.mjs --dry-run
agent-browser latest practical versionagent-browser installffmpeg and ffprobedgDEEPGRAM_API_KEY in files. Require it from the environment.DEEPGRAM_API_KEY is a warning, not a setup failure. The run can still produce raw evidence and silent proof.agent-browser, browser payloads, or ffmpeg blocks browser video evidence.node plugins/proof-driven-verification/scripts/deepgram-key.mjs set or use DEEPGRAM_API_KEY.development
Decide HOW to run a coding task — interactive, goal mode, or a workflow — then author the launch-ready prompt or goal package for Claude Code, Codex, or Antigravity. Use when the user says "launchpad", "start a goal", "set up a goal/sprint", "should this be a goal or interactive", "plan an autonomous run", "I want to brain-dump a task", "help me write a goal prompt", or is about to kick off a long autonomous run and wants it scoped, delegated, and verifiable first.
development
Use when turning founder requirements, research packets, plans, specs, and system designs into one or more independently executable Claude Code, Cloud Code, or Codex implementation sprints with story writing, review, execution, optional verification, and sprint-level commits.
tools
Interactive Claude Code repository setup and optimization. Configures the complete ecosystem - skills, commands, subagents, hooks, rules, MCPs, and plugins. Invoke with /setup-claude init or /setup-claude audit.
testing
Pre-flight check for Ralph TUI loops. Validates config, templates, prd.json, and environment before starting a loop. Run after /prd to verify everything is ready. Detects global CLAUDE.md conflicts, validates template variables, and provides launch commands.