verification Skill
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals. Published by openai in plugins.
What is verification Skill?
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Data analysis
- Writing
- Browser automation use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use verification Skill
- Use it for browser automation.
- Use it for data analysis.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/verification/SKILL.md
What it does
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
Skill instructions
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. This skill coordinates with agent-browser-verify (browser-side visual checks), investigation-mode (reactive debugging), and observability (logging/monitoring) — but 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
Explore related resources
Frequently asked questions
What is verification?
verification is a open-source AI agent skill with Copy skill directory. Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
Who is verification best for?
verification is best for reusing agent instructions, scripts, and references, browser automation workflows, data analysis workflows, writing workflows.
How do I install verification?
Install or run verification using Copy skill directory. Check verification for the latest setup command.
Is verification actively maintained?
verification may need a closer maintenance check before production use.
Auto-fetched from GitHub.
