Run ten ordered checks and emit an overall environment health status.
npx skills add https://github.com/razorpay/ai-playbook --skill setup-verify
Please help me install this Agent Skill. Skill: setup-verify Source: https://github.com/razorpay/ai-playbook/tree/main/skills/setup-verify Command: npx skills add https://github.com/razorpay/ai-playbook --skill setup-verify
setup-verify diagnoses environment drift by checking whether all required tools, auth, network routes, and config are healthy for the playbook curriculum, so you know exactly why your setup isn’t quest-ready.
Ask Claude Code to run setup-verify and paste the resulting report to see which checks are blocking or warning before you try to claim Quest W-0.
High-intent search queries and answers about installing and using this skill.
You can verify dev environment readiness by running ten ordered diagnostics covering tool versions, network routes, and auth configurations. The check produces a GREEN, WARNING, or BLOCKER assessment with one-line fixes for any failing items.
Environment drift happens when local tool versions, auth tokens, or network routes fall out of sync with required configurations. Diagnose it by running an environment health report that flags specific signals and provides exact one-line fixes to resolve them.
Verify Claude Code and gcloud Vertex auth by running an environment diagnostic that includes dedicated auth verification checks. The diagnostic evaluates your authentication state and returns a status indicating whether your auth is healthy or needs reconfiguration.
Yes, you can re-run a single environment check using focused rerun mode. If you know which area failed, such as internal registry access or Git corp SSO config, you can target and re-verify that specific check without running all ten diagnostics again.
No, the setup verification does not modify your local environment configuration. It performs read-only diagnostics across all checks and only emits an overall status with suggested one-line fixes for you to execute manually if needed.
A LiteLLM connectivity check returns a warning status when the diagnostic detects an issue reaching the LiteLLM endpoint, which could indicate network route problems or proxy interference. The health report provides a specific signal and a one-line fix to resolve the connectivity block.
xotongDiagnose and configure a Compound Engineering environment with guided health checks and setup.
razorpayGuide learners through belt-based curriculum modules with stateful progression and quest gating.
openaiRun installation, build, linting, type checks, and tests for code changes.
riandeoliveiraManage NuGet packages across .NET solutions using dotnet CLI and CPM.
