Verification
Run end-to-end verification of the user story—browser, API, data, and env—when dev starts or something feels almost working.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill verificationWhat is this skill?
- Infers what you are building, then verifies browser → API → data → response as one story
- Triggers on common dev commands: next dev, npm/pnpm/bun/yarn dev, vite, vercel dev, astro dev
- Prompt signals for “why isn’t this working”, “almost works but”, and “works locally but”
- Designed for full verification when something feels off without a narrow unit-test scope
- Summary goal: verify full user story across server and client
Adoption & trust: 246 installs on skills.sh; 187 GitHub stars; 2/3 security scanners passed (skills.sh audits).
Recommended Skills
Agent Browservercel-labs/open-agents
Tddmattpocock/skills
Use My Browserxixu-me/skills
Test Driven Developmentobra/superpowers
Verification Before Completionobra/superpowers
Webapp Testinganthropics/skills
Journey fit
Primary fit
Full-story verification is shelved under Ship/testing as the canonical gate before you trust a feature or deploy. The skill infers intent from dev-server commands and “verify the flow” language, matching local E2E confidence checks rather than production monitoring alone.
Common Questions / FAQ
Is Verification safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Verification
# Full-Story Verification You are a verification orchestrator. Your job is not to run a single check — it is to **infer the complete user story** being built and verify every boundary in the flow with evidence. Your focus is the **end-to-end story**, not any single layer. ## When This Triggers - A dev server just started and the user wants to know if things work - The user says something "isn't quite right" or "almost works" - The user asks you to verify a feature or check the full flow ## Step 1 — Infer the User Story Before checking anything, determine **what is being built**: 1. Read recently edited files (check git diff or recent Write/Edit tool calls) 2. Identify the feature boundary: which routes, components, API endpoints, and data sources are involved 3. Scan `package.json` scripts, route structure (`app/` or `pages/`), and environment files (`.env*`) 4. State the story in one sentence: _"The user is building [X] which flows from [UI entry point] → [API route] → [data source] → [response rendering]"_ **Do not skip this step.** Every subsequent check must be