Verification

When you spin up a dev server or mutter "why isn't this working," this skill kicks in to trace the full user story from browser through API to data and back. It's not running unit tests. It's inferring what you're actually building, then checking each boundary with evidence: screenshots, terminal output, network logs, environment state. The reporting format is structured (what was checked, what was found, what's next), and it stops at the first broken boundary instead of piling on noise. Honestly most useful when you've wired up a feature across layers and need to confirm the whole thing actually works, or when something feels off but you're not sure which layer is lying to you.

skills.sh installs: 226
GitHub stars: 183
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add vercel-labs/vercel-plugin --skill verification --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

Read recently edited files (check git diff or recent Write/Edit tool calls)
Identify the feature boundary: which routes, components, API endpoints, and data sources are involved
Scan package.json scripts, route structure (app/ or pages/), and environment files (.env*)
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 anchored to the inferred story.